Bug 758160 - Connection closed when guest shut down
Summary: Connection closed when guest shut down
Keywords:
Status: CLOSED DUPLICATE of bug 752718
Alias: None
Product: Fedora
Classification: Fedora
Component: virt-manager
Version: 16
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Cole Robinson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-29 12:51 UTC by Tim Waugh
Modified: 2011-12-01 16:38 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-01 16:38:13 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Tim Waugh 2011-11-29 12:51:19 UTC
Description of problem:
Very often when I shut down a guest, the libvirt connection closes and I get an error message:

Error polling connection 'qemu:///system': Unable to read from monitor: Connection reset by peer

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


The main virt-manager window now says:

localhost (QEMU) - Not Connected


Closing the error message window and double-clicking on the localhost line prompts me for the admin password again, and re-establishes the connection.

Version-Release number of selected component (if applicable):
virt-manager-0.9.0-7.fc16.noarch
libvirt-0.9.6-2.fc16.x86_64
qemu-kvm-0.15.1-3.fc16.x86_64

How reproducible:
Often.

Comment 1 Jerry James 2011-12-01 16:19:00 UTC
Is this a duplicate of bug 752718?

Comment 2 Tim Waugh 2011-12-01 16:38:13 UTC
Yes, thanks for spotting that.

*** This bug has been marked as a duplicate of bug 752718 ***


Note You need to log in before you can comment on or make changes to this bug.