Comment 4 for bug 201221

Revision history for this message
In , Soren (soren-redhat-bugs) wrote :

Description of problem:

Version-Release number of selected component (if applicable):
0.5.3

How reproducible:
Always

Steps to Reproduce:
1. Start a domain
2. In its menu, click save and enter a filename
3. Wait a little bit

Actual results:
Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/engine.py", line 403, in _save_callback
    vm.save(file_to_save)
  File "/usr/share/virt-manager/virtManager/domain.py", line 394, in save
    self.vm.save(file)
  File "/usr/lib/python2.5/site-packages/libvirt.py", line 354, in save
    if ret == -1: raise libvirtError ('virDomainSave() failed', dom=self)
libvirtError: virDomainSave() failed unknown procedure (received 34, expected 37)

Expected results:
Saving the image and not much else.

Additional info:
The problem seems to stem from virt-manager using the existing "control"
connection to invoke the saving. According to rjones, virt-manager should use
another connection for that.

First reported at:
https://bugs.edge.launchpad.net/ubuntu/+source/virt-manager/+bug/201221