On 02/05/2012 08:42 AM, Ansis Atteka wrote:
My bad, it actually seems that your patch fixed my issue after I manually removed the domain XML file that was stuck in /var/run.
I've gone ahead and pushed the patch, since it helped.
Nevertheless, it seems that the issue when virt-manager exited preamturely could be caused by something else:
2012-02-05 15:39:28.395+0000: 29540: error : virNetSocketReadWire:999 : End
of file while reading data: Input/output error
virt-manager can't connect if libvirtd is in a weird state; and perhaps the parse error was causing things to get in a weird state to begin with. At any rate, for the XML you attached, the config XML had no <seclabel>, and the live XML had: <seclabel type='dynamic' relabel='yes'/> with no mode='selinux' or any <label> sub-element to say what had actually been labeled. I think that all stems back to the parsing error in the first place, and that with the patch in place, things should be working better. -- Eric Blake eblake@redhat.com +1-919-301-3266 Libvirt virtualization library http://libvirt.org