Description of problem: xenner and libvirt have a different idea of guest domain id and vm uuid Version-Release number of selected component (if applicable): libvirt-0.4.4 Additional info: xenner has -domid and -uuid command line switches (also listed in help) which can be used.
Triaging this bug ... kraxel: can you clarify what the proposed changes should be? Should xenner change to match libvirt's use of vm uuid, or the other way around? Or perhaps another approach. Does the mismatch between domain id and vm uuid result in a failure of some sort? Thanks!
xenner is started by the libvirt daemon (pretty much like qemu). libvirt has a uuid and a domain id for every guest started. libvirt daemon should pass these to xenner, using the command line switches mentioned in the first comment, when starting xenner. presense of these switches can be detected from help text. libvirt already does that to detect other features such as -drive support in qemu / xenner. The uuid mismatch isn't that a big problem. The domid mismatch is IMHO a serve usability issue. The domid printed by "virsh list" doesn't match the one used in xenstore for example. Which can be very confusing when trouble-shooting things, or when trying to use xenconsole (which checks xenstore too).
Patches for passing -domid & -uuid args posted upstream http://www.redhat.com/archives/libvir-list/2008-November/msg00013.html
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle. Changing version to '10'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This was in libvirt-0.5.0