On 10/19/2011 05:03 AM, Frank Murphy wrote: > Hi, > > If I use "halt -p" on the Fedora Guests. > I get disconnected from Virt-Manager. > > click connect, and the running vms are there again.
Were you running multiple guests at the time? Was the guest where you did 'halt' running in full-screen mode? If so, this sounds similar to: https://bugzilla.redhat.com/show_bug.cgi?id=742055 > > Here what vmm says: > > Error polling connection 'qemu:///system': Unable to read from > monitor: Connection reset by peer > > Traceback (most recent call last): > File "/usr/share/virt-manager/virtManager/engine.py", line 440, in _tick > conn.tick() > File "/usr/share/virt-manager/virtManager/connection.py", line 1507, in > tick > vm.tick(now) > File "/usr/share/virt-manager/virtManager/domain.py", line 1531, in tick > info = self._backend.info() > File "/usr/lib64/python2.7/site-packages/libvirt.py", line 1411, in info > if ret is None: raise libvirtError ('virDomainGetInfo() failed', > dom=self) > libvirtError: Unable to read from monitor: Connection reset by peer > > > What would I bz against. Right now, my guess is that virt-manager is not handling guest-initiated shutdown cleanly, although we might reassign the problem to libvirt if it turns out to be a data race where libvirt isn't properly handling events during a guest-initiated shutdown, such that it leaks an unexpected error to the client instead. -- Eric Blake [email protected] +1-801-349-2682 Libvirt virtualization library http://libvirt.org _______________________________________________ virt mailing list [email protected] https://admin.fedoraproject.org/mailman/listinfo/virt
