On 02/13/2012 04:13 PM, lee wrote:
Hi
qemu-kvm-0.12.1.2-2.160.el6_1.2.x86_64
qemu-kvm-tools-0.12.1.2-2.160.el6_1.2.x86_64
libvirt-java-javadoc-0.4.7-1.el6.noarch
libvirt-client-0.8.7-18.el6.x86_64
fence-virtd-libvirt-qpid-0.2.1-8.el6.x86_64
ocaml-libvirt-0.6.1.0-6.2.el6.x86_64
libvirt-devel-0.8.7-18.el6.x86_64
libvirt-python-0.8.7-18.el6.x86_64
libvirt-java-0.4.7-1.el6.noarch
libvirt-cim-0.5.11-3.el6.x86_64
libvirt-java-devel-0.4.7-1.el6.noarch
libvirt-client-0.8.7-18.el6.i686
libvirt-qpid-0.2.22-6.el6.x86_64
fence-virtd-libvirt-0.2.1-8.el6.x86_64
libvirt-0.8.7-18.el6.x86_64
ocaml-libvirt-devel-0.6.1.0-6.2.el6.x86_64
get this error when I try to restore a vm that was 'save'.
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/engine.py", line 909, in
run_domain
vm.startup()
File "/usr/share/virt-manager/virtManager/domain.py", line 1321, in startup
self._backend.create()
File "/usr/lib64/python2.7/site-packages/libvirt.py", line 330, in create
if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirtError: cannot send monitor command
'{"execute":"qmp_capabilities"}': Connection reset by peer
the solution was to delete the /var/lib/libvirt/qemu/save directory.
Anyone any idea of why?
It was a known bug, newer libvirt already fixed that. It's
probly caused by there is a corrupt/incomplete domain state
file with the same domain name in /var/lib/libvirt/qemu/save,
actually using "virsh managesave-remove" will help you fix
the problem.
Another way to update your libvirt to newer version, both
"virsh start" and "virsh undefine" introduced related flags
(e.g. virsh start --force-boot, virsh undefine --managed-save)
to work around the problem.
Osier
