uyuni wrongly label machine as physical instead of VM
fritz0011 opened this issue · 0 comments
Problem description
Some machines are identified as physical instead of VM (mostly on Microsoft HYPER-V)
Steps to reproduce
See additional info:
BTW, even if machine is un-register from uyuni and re-added it is still identified as nonVM
P.S. Please, consider it as P3 as it affects also reports of machines we extract from uyuni....
Uyuni version
Information for package Uyuni-Server-release:
---------------------------------------------
Repository : uyuni-server-stable
Name : Uyuni-Server-release
Version : 2024.05-230900.217.1.uyuni3
Arch : x86_64
Vendor : obs://build.opensuse.org/systemsmanagement:Uyuni
Support Level : Level 3
Installed Size : 1.4 KiB
Installed : Yes (automatically)
Status : up-to-date
Source package : Uyuni-Server-release-2024.05-230900.217.1.uyuni3.src
Summary : Uyuni Server
Uyuni proxy version (if used)
No response
Useful logs
No response
Additional information
machine identified correctly as VM
CPU
Count: 2
Arch: x86_64
MHz: 2399.996
Cache: 35840 KB
Vendor: GenuineIntel
Model: Intel(R) Xeon(R) CPU E5-2680 v4
Memory
RAM: 7616
Swap: 8191
DMI
Vendor: Microsoft Corporation
System: Virtual Machine Hyper-V UEFI Release v4.0
Product: Virtual Machine
Board:
Asset
chassis: 9343-1097-3624-0602-9114-1687-88
chassis: 9343-1097-3624-0602-9114-1687-88
board: 9343-1097-3624-0602-9114-1687-88
system: 9343-1097-3624-0602-9114-1687-88
BIOS Release: 12/17/2019
BIOS Vendor: Microsoft Corporation
BIOS Version: Hyper-V UEFI Release v4.0
machine identified as physical server
CPU
Count: 2
Arch: x86_64
MHz: 2399.996
Cache: 35840 KB
Vendor: GenuineIntel
Model: Intel(R) Xeon(R) CPU E5-2680 v4
Memory
RAM: 7616
Swap: 8191
DMI
Vendor: Microsoft Corporation
System: Virtual Machine Hyper-V UEFI Release v4.0
Product: Virtual Machine
Board:
Asset
chassis: 9343-1097-3624-0602-9114-1687-88
chassis: 9343-1097-3624-0602-9114-1687-88
board: 9343-1097-3624-0602-9114-1687-88
system: 9343-1097-3624-0602-9114-1687-88
BIOS Release: 12/17/2019
BIOS Vendor: Microsoft Corporation
BIOS Version: Hyper-V UEFI Release v4.0
Just to mention, this erratic behavior seems to affect only VMs deployed in HYPER-V