On 11/18/2011 07:25 AM, Robin van Leeuwen wrote:

Hi

I posted the above mentioned bug to Bugzilla and one reply said to mention it on libvir-list@redhat.com as well. So here it is:

https://bugzilla.redhat.com/show_bug.cgi?id=754974

Is mentioning it in this list too, (when it involves libvirt offcourse) after filing a bug on Bugzilla, the appropiate action to take?

You're doing fine. BZs tend to be a bit more permanent (they exist to remind us that the problem exists, and even after it exists), but they are also a bit harder to access so they tend to not get as rapid a response as an email to the list. Alas, regarding the bug itself, I'm not familiar enough with 'virsh list' on a xen:// connection to know how to suggest debugging things; perhaps someone else can chime in. The fact that a 'shut off' guest is listed both locally and remotely means your remote connection is working, while the 'running' and 'idle' Dom0 and guest 17 showing up only locally might point to a flaw in the remote implementation of listing active xen guests. -- Eric Blake eblake@redhat.com +1-919-301-3266 Libvirt virtualization library http://libvirt.org