https://bugzilla.novell.com/show_bug.cgi?id=820873 https://bugzilla.novell.com/show_bug.cgi?id=820873#c9 --- Comment #9 from James Fehlig <jfehlig@suse.com> 2013-06-13 09:33:21 UTC --- (In reply to comment #5)
Actually I use virsh for starting my VMs and the long list option doesn't work with any of them.
There are no guarantees libvirt and xl will play nicely together. These are two different libxl applications, neither of which is aware that the other exits. libxl supports the notion of "user data", where applications can store private data related to a domain. xl stores its data with userid "xl". libvirt stores its data with userid "libvirt-xml". The bug you are seeing is xl unable to find its user data. (In reply to comment #7)
Ok, it looks like the problem is in the libvirtd libxl driver. "xl list -l" only works if the VM is started by xl.
No problem in the libvirt libxl driver. IMO, the bug here is that xl could report a better error message, e.g. "No xl user data found. Is this domain managed by another libxl application?". (In reply to comment #8)
Of course, if I start them with xl then libvirt doesn't see them.
That's correct. libvirt will only know about domains started by libvirt, similar to the qemu driver where domains started with e.g. 'qemu-kvm ...' are unknown to libvirt. Again, I think the bug here is an unclear error message from xl. Do you agree? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.