Bug 189498

Summary: Xen UUIDs are available from Dom0, but not from DomU (fully virtualized domains)
Product: [Fedora] Fedora Reporter: Robin Norwood <robin.norwood>
Component: xenAssignee: Xen Maintainance List <xen-maint>
Status: CLOSED RAWHIDE QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: bstein
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-01-11 16:35:52 EST Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Robin Norwood 2006-04-20 11:36:13 EDT
Xen provides a UUID for running domains, but this UUID is only available from
dom0, not domU.  Management applications (such as RHN) need a way to associate
the domain attached to a given dom0 with the running instance.

For fully virtualized hosts, we will not be able to expose this data in /proc,
so it will need to be exposed via DMI.

See bug #189497 for UUID exposure in paravirtualized domains.
Comment 1 Daniel Berrange 2006-09-29 17:14:32 EDT
I've tested that xen > 3.0.2-31 RPMs provide SMBIOS data to fullyvirtualized
guests. Please run 'dmidecode' in a HVM guest & confirm that the UUID data
satisfies your requirements. 
Comment 2 Daniel Berrange 2007-01-11 16:35:52 EST
This is long since fixed in both Fedora & RHEL.