save fails after writing out memory image
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
virt-manager |
Fix Released
|
Low
|
|||
virt-manager (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: virt-manager
After writing out all 512M of memory, "Save" failed:
Traceback (most recent call last):
File "/usr/share/
vm.
File "/usr/share/
self.
File "/usr/lib/
if ret == -1: raise libvirtError ('virDomainSave() failed', dom=self)
libvirtError: virDomainSave() failed unknown procedure (received 34, expected 37)
Additionally, I think bug 194644 is not gone -- my keyboard (and all virt-man windows) hung while the save happened. (I was able to switch VTs to vt1, so I think the keyboard focus needs to be "ejected" from the VM before save starts -- I think keystrokes are blocked while the save happens?)
Changed in virt-manager: | |
status: | Unknown → In Progress |
Changed in virt-manager: | |
status: | In Progress → Unknown |
Changed in virt-manager: | |
status: | Unknown → Fix Committed |
Changed in virt-manager: | |
status: | Fix Committed → Fix Released |
Changed in virt-manager: | |
importance: | Unknown → Low |
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: virt-manager/ virtManager/ engine. py", line 403, in _save_callback save(file_ to_save) virt-manager/ virtManager/ domain. py", line 394, in save vm.save( file) python2. 5/site- packages/ libvirt. py", line 354, in save
Traceback (most recent call last):
File "/usr/share/
vm.
File "/usr/share/
self.
File "/usr/lib/
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: /bugs.edge. launchpad. net/ubuntu/ +source/ virt-manager/ +bug/201221
https:/