virt-manager. restore windows vm-> Unknown savevm section type 5
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
qemu (Ubuntu) |
Expired
|
Medium
|
Unassigned |
Bug Description
When running a windows vm under kvm, save-ing, and then restore-ing, the restore fails with
Error restoring domain: internal error: process exited while connecting to monitor: Unknown savevm section type 5
2015-07-
Sw versions:
i ipxe-qemu 1.0.0+git-
ii qemu-kvm 1:2.2+dfsg-
ii qemu-system-common 1:2.2+dfsg-
ii qemu-system-x86 1:2.2+dfsg-
ii qemu-utils 1:2.2+dfsg-
jonesn@
jonesn@
ii gir1.2-
ii libvirt-bin 1.2.12-0ubuntu13 amd64 programs for the libvirt library
ii libvirt-glib-1.0-0 0.1.9-4 amd64 libvirt glib mainloop integration
ii libvirt0 1.2.12-0ubuntu13 amd64 library for interfacing with different virtualization systems
ii python-libvirt 1.2.12-0ubuntu1 amd64 libvirt Python bindings
jonesn@
onesn@jonesn-
ii virt-manager 1:1.0.1-5ubuntu1 all desktop application for managing virtual machines
It may be this bug in qemu 2.2
http://
I've not seen a later package in the ubuntu repos, though happy to test if one exists. I may build qemu seperately as a test
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: virt-manager 1:1.0.1-5ubuntu1
ProcVersionSign
Uname: Linux 3.19.0-22-generic x86_64
NonfreeKernelMo
ApportVersion: 2.17.2-0ubuntu1.1
Architecture: amd64
CurrentDesktop: KDE
Date: Wed Jul 8 08:19:03 2015
ExecutablePath: /usr/share/
InstallationDate: Installed on 2015-06-12 (25 days ago)
InstallationMedia: It
InterpreterPath: /usr/bin/python2.7
PackageArchitec
ProcEnviron:
LANGUAGE=en_GB:en
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_GB.UTF-8
SHELL=/bin/bash
SourcePackage: virt-manager
UpgradeStatus: No upgrade log present (probably fresh install)
Changed in qemu (Ubuntu): | |
status: | Triaged → Incomplete |
Changed in qemu (Ubuntu): | |
assignee: | Stefan Bader (smb) → nobody |
Updated package to qemu after testing against the packages in https:/ /launchpad. net/ubuntu/ +source/ qemu (2.3 debs). With these installed this bug does not occur. Note that I did remove USB controller/ redirector and changed spice->vnc in order to get the vm to start since these 2.3 packages as of 8 July 2015 appear not to support spice or usb