I'm having a problem with multiple VMs and virt-manager on a Fedora 16 x86_64 machine. When I have multiple VMs running and shut one down, frequently virt-manager loses its connection. All of my VM windows disappear, and I'm left looking at a dialog box that says (after expanding the "Details" tab):
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
Simply reconnecting in virt-manager usually works, and then I can reopen windows for the VMs that are still running. HOWEVER, yesterday I had this happen and one of my running VMs was NOT listed. I just about panicked, thinking it had been deleted somehow. However, restarting libvirtd made it show up again.
Is this a known problem? If not, what component should I file a bug against? Thanks,
On 11/30/2011 06:07 PM, Jerry James wrote:
I'm having a problem with multiple VMs and virt-manager on a Fedora 16 x86_64 machine. When I have multiple VMs running and shut one down, frequently virt-manager loses its connection. All of my VM windows disappear, and I'm left looking at a dialog box that says (after expanding the "Details" tab):
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
Simply reconnecting in virt-manager usually works, and then I can reopen windows for the VMs that are still running. HOWEVER, yesterday I had this happen and one of my running VMs was NOT listed. I just about panicked, thinking it had been deleted somehow. However, restarting libvirtd made it show up again.
Is this a known problem? If not, what component should I file a bug against? Thanks,
I'm seeing this too occasionally. I shut down a VM and virt-manager looses the connection. After reconnecting everything seems to be ok.
Regards, Dennis
It's known issue. View bug :-
https://bugzilla.redhat.com/show_bug.cgi?id=752718
Boris.
--- On Thu, 12/1/11, Dennis Jacobfeuerborn dennisml@conversis.de wrote:
From: Dennis Jacobfeuerborn dennisml@conversis.de Subject: Re: [fedora-virt] Close a VM, virt-manager loses connection To: virt@lists.fedoraproject.org Date: Thursday, December 1, 2011, 7:43 AM
On 11/30/2011 06:07 PM, Jerry James wrote:
I'm having a problem with multiple VMs and virt-manager on a Fedora 16 x86_64 machine. When I have multiple VMs running and shut one down, frequently virt-manager loses its connection. All of my VM windows disappear, and I'm left looking at a dialog box that says (after expanding the "Details" tab):
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
Simply reconnecting in virt-manager usually works, and then I can reopen windows for the VMs that are still running. HOWEVER, yesterday I had this happen and one of my running VMs was NOT listed. I just about panicked, thinking it had been deleted somehow. However, restarting libvirtd made it show up again.
Is this a known problem? If not, what component should I file a bug against? Thanks,
I'm seeing this too occasionally. I shut down a VM and virt-manager looses the connection. After reconnecting everything seems to be ok.
Regards, Dennis
_______________________________________________ virt mailing list virt@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/virt
It's known issue. View bug :-
https://bugzilla.redhat.com/show_bug.cgi?id=752718
Boris.
--- On Thu, 12/1/11, Dennis Jacobfeuerborn dennisml@conversis.de wrote:
From: Dennis Jacobfeuerborn dennisml@conversis.de Subject: Re: [fedora-virt] Close a VM, virt-manager loses connection To: virt@lists.fedoraproject.org Date: Thursday, December 1, 2011, 7:43 AM
On 11/30/2011 06:07 PM, Jerry James wrote:
I'm having a problem with multiple VMs and virt-manager on a Fedora 16 x86_64 machine. When I have multiple VMs running and shut one down, frequently virt-manager loses its connection. All of my VM windows disappear, and I'm left looking at a dialog box that says (after expanding the "Details" tab):
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
Simply reconnecting in virt-manager usually works, and then I can reopen windows for the VMs that are still running. HOWEVER, yesterday I had this happen and one of my running VMs was NOT listed. I just about panicked, thinking it had been deleted somehow. However, restarting libvirtd made it show up again.
Is this a known problem? If not, what component should I file a bug against? Thanks,
I'm seeing this too occasionally. I shut down a VM and virt-manager looses the connection. After reconnecting everything seems to be ok.
Regards, Dennis
_______________________________________________ virt mailing list virt@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/virt
On 11/30/2011 12:07 PM, Jerry James wrote:
I'm having a problem with multiple VMs and virt-manager on a Fedora 16 x86_64 machine. When I have multiple VMs running and shut one down, frequently virt-manager loses its connection. All of my VM windows disappear, and I'm left looking at a dialog box that says (after expanding the "Details" tab):
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
Simply reconnecting in virt-manager usually works, and then I can reopen windows for the VMs that are still running. HOWEVER, yesterday I had this happen and one of my running VMs was NOT listed. I just about panicked, thinking it had been deleted somehow. However, restarting libvirtd made it show up again.
Is this a known problem? If not, what component should I file a bug against? Thanks,
I realize this is thread is pretty old, but here's a the bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=752718
Fix is now in upstream virt-manager, backport to f16 coming soon.
Thanks, Cole
-
Boris Derzhavets -
Cole Robinson -
Dennis Jacobfeuerborn -
Jerry James