+++ This bug was initially created as a clone of Bug #495611 +++ Created an attachment (id=339411) RHEL 5.3 FV Xen DMIDECODE In order to allow identifying a host from the guest - mainly for RHN use cases - a UUID needs to be exported through SMBIOS to the guests the same way, that happens for RHEL5 / Xen. Attached is an example demidecode from a RHEL 5.3 Xen system.
This request makes no sense. KVM already has the ability to expose the *guest* UUID via SMBIOS data. This is sufficient for RHN needs (as proved by fact that Xen works this way already). There is no need to expose the host OS UUID too.
I changed the subject to reflect the guest UUID. I will file another request for the host UUID as it is a slightly different use case. It seem to be a QE-only thing. Also, this is more improtant for RHEL than for RHEV-H, as the "free" virt guests rules depend on the UUID being there. This means, if the *GUEST* UUID is not available in the guest's smbios, that guest will not follow the expected RHN business rules and possibly not be able to register in RHN.
Based on Dan's comments there is nothing to do here other than make sure that QE is testing this. Assigned and added key QE folks. Feel free to close.
QE: You can use WMI to query the UUID on Windows.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2009-1243.html