What were you trying to do that didn't work?

UUID reported by virt-who different from dmidecode of VM running on VMware

we found that the UUID reported in system's dmidecode is not completely matching with UUID reported by virt-who. The UUID is getting reversed.  In order to virt-who work properly, we do a process which is called host-guest-mapping, which means, the Content Host will push one specific UUID, and virt-who will connect to the hypervisor, and will also generate a list of VM's UUID. In general, they should match.

Please provide the package NVR for which bug is seen:

virt-who-1.31.26-1.el9.noarch

How reproducible:

Always

Steps to reproduce

1. Create a RHEL VM
2. proceeds with the hardware upgrade via webUI/vCenter
3. Check the virt-who mapping

Expected results

UUID reported by virt-who should match with the VM dmidecode UUID no matter if the hardware version is upgraded from Vcenter. 

As virt-who already collects properties from the VMs, it should be possible to add 'config.extraConfig" to "self.createPropertySpec("VirtualMachine", ["config.uuid", "config.version", "runtime.powerState"])" in virtwho.virt.Esx.CreateFilter(), then check for the presence of 'acpi.smbiosVersion2.7' in config.extraConfig and act accordingly in Esx.getVmUuid()

Actual results

The VMs are now reported to the subscription watch but as a standalone VM as the UUID reported by virt-who does not match with the VM dmidecode UUID. The hypervisors are also not getting reported to the Subscription watch due to missing host-guests mapping. 

Refer JIRA https://issues.redhat.com/browse/SWATCH-2548