Incorrect Hardware info for Xen machines

[SchoolGuy]

2016-03-31 15:43:20 UTC

If the machine is running Xen, it is possible that dom0 cannot see all of the memory (or CPUs) available on the physical hardware. In this case, the hypervisor has to be queried for the correct information.

For example, xen126 is listed off in Orthos as having 946MB of RAM. In reality, xl info on this machine shows that there is 16GB on the physical machine, and dom0 is simply limited to 1G.

In order to get an accurate view of the hardware, we need the hardware gathering script to take these facts into consideration. If the script finds the xen hypervisor is running (by looking for the existence of /proc/xen, for example), xm info (under SLES10/11) or xl info (under SLES12+) should contain all the details you need to report the right data.

Checking for /proc/xen/privcmd, might be a better choice as that file only exists in dom0.

Beginning with SLES12SP2, kernel-xen is being replaced with a pvops enabled kernel-default. With this change, it will no longer be possible to identify a machine running xen by checking the Kernelversion field.

---

Migrated from https://bugzilla.suse.com/show_bug.cgi?id=973428