save fails after writing out memory image

Bug #201221 reported by Kees Cook
2
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/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)

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?)

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

Revision history for this message
Soren Hansen (soren) wrote :

About bug 194644: Apparantly there are a few things that can make virt-manager hang. One of them was save() hanging indefinitely due to a kernel bug. That's what I've treated as the root cause of 194644. This bug is another thing that makes virt-manager hang, and does indeed have something to do with save(), but it's an entirely different issue. I think we should leave 194644 alone :)

Changed in virt-manager:
status: New → Triaged
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package virt-manager - 0.5.3-0ubuntu8

---------------
virt-manager (0.5.3-0ubuntu8) hardy; urgency=low

  * Clean up: Use patches instead of editing stuff directly in the tree.
  * Add Vcs-Bzr header to debian/control.
  * Make the error message when failing to connect to the hypervisor more
    helpful. (LP: #198957)
  * Use separate libvirt connection when saving a domain. (LP: #201221)
  * Detect magic string in saved qemu/kvm images.

 -- Soren Hansen <email address hidden> Thu, 13 Mar 2008 10:07:03 +0100

Changed in virt-manager:
status: Triaged → Fix Released
Changed in virt-manager:
status: Unknown → In Progress
Revision history for this message
In , Cole (cole-redhat-bugs) wrote :

Hmm, this confuses me. Is this a bug at the libvirt level? Why should a seperate
connection be needed for saving? What type of connection and guest are you
using? (system or session, plain qemu or kvm, xen?). I can't seem to reproduce
this either.

That being said, I've noticed that you are now carrying a fix for this in the
ubuntu package. Would you mind posting the following patches to et-mgmt-tools:

patches/show_session_or_system_in_console.diff
patches/ssh_tunnel_username.patch
patches/restore_saved_images.patch
patches/save_separate_connection.patch

Thanks

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

ssh_tunnel_username.patch was already submitted and applied (revision
675:49c55daf788d).
I'll send the other ones. Thanks for the nudge :)

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

I sent a patch to fix this bug to the mailing list and it has now been applied.
(Changeset 734: 2ea7f77b0339)

I'm not too familiar with your bug handling policies, so I don't know if it's
appropriate to close this bug (since it's not in a release of any sort yet), so
I'll leave that up to you guys.

Revision history for this message
In , Daniel (daniel-redhat-bugs) wrote :

Patch is upstream, will incorporate into next release. Leaving this bug open
until its released.

http://hg.et.redhat.com/virt/applications/virt-manager--devel?cs=2ea7f77b0339

Changed in virt-manager:
status: In Progress → Unknown
Revision history for this message
In , Bug (bug-redhat-bugs) wrote :

Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Revision history for this message
In , Fedora (fedora-redhat-bugs) wrote :

virt-manager-0.6.0-0.fc9 has been submitted as an update for Fedora 9.
http://admin.fedoraproject.org/updates/virt-manager-0.6.0-0.fc9

Revision history for this message
In , Fedora (fedora-redhat-bugs) wrote :

virt-manager-0.6.0-1.fc9 has been submitted as an update for Fedora 9.
http://admin.fedoraproject.org/updates/virt-manager-0.6.0-1.fc9

Revision history for this message
In , Fedora (fedora-redhat-bugs) wrote :

virt-manager-0.6.0-1.fc9 has been pushed to the Fedora 9 testing repository. If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with
 su -c 'yum --enablerepo=updates-testing-newkey update virt-manager'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F9/FEDORA-2008-10705

Changed in virt-manager:
status: Unknown → Fix Committed
Revision history for this message
In , Fedora (fedora-redhat-bugs) wrote :

virt-manager-0.6.0-1.fc9 has been pushed to the Fedora 9 stable repository. If problems still persist, please make note of it in this bug report.

Changed in virt-manager:
status: Fix Committed → Fix Released
Revision history for this message
Robstarusa (rob-naseca) wrote :

I am having this issue in virt-manager 0.6.0-6ubuntu1 on intrepid.

"Error saving domain: unknown
procedure (received 6, expected 10)

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/engine.py", line 465, in _save_callback
    vm.save(file_to_save)
  File "/usr/share/virt-manager/virtManager/domain.py", line 402, in save
    self._update_status()
  File "/usr/share/virt-manager/virtManager/domain.py", line 144, in _update_status
    info = self.vm.info()
  File "/usr/lib/python2.5/site-packages/libvirt.py", line 507, in info
    if ret is None: raise libvirtError ('virDomainGetInfo() failed', dom=self)
libvirtError: unknown procedure (received 6, expected 10)
"

Changed in virt-manager:
importance: Unknown → Low
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.