Restoring VM from 2.3 to 3.0, on start throws error

tehsu

New Member
May 15, 2013
11
0
1
When I start the VM that I restored onto 3.0 from 2.3 it ends up throwing an error, I can't seem to find any information on this anywhere.

TASK ERROR: detected old qemu-kvm binary (unknown)

 
root@tsunade:/var/lib/vz/template/iso# pveversion -v
proxmox-ve-2.6.32: 3.1-109 (running kernel: 2.6.32-23-pve)
pve-manager: 3.1-4 (running version: 3.1-4/f6816604)
pve-kernel-2.6.32-23-pve: 2.6.32-109
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.5-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.0-2
pve-cluster: 3.0-7
qemu-server: 3.1-1
pve-firmware: 1.0-23
libpve-common-perl: 3.0-6
libpve-access-control: 3.0-6
libpve-storage-perl: 3.0-10
pve-libspice-server1: 0.12.4-1
vncterm: 1.1-4
vzctl: 4.0-1pve3
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-17
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.0-2

Edit: It throws the same error with a fresh VM also.
 
I had virt-manager qemu n all that installed before proxmox so I think thats causing the problem but am unsure why it still sees qemu-kvm after I've removed it

I am also seeing this on my new install and not on my old,
kvm --version
kvm: /usr/lib/x86_64-linux-gnu/libspice-server.so.1: version `SPICE_SERVER_0.10.4' not found (required by kvm)
kvm: /usr/lib/x86_64-linux-gnu/libspice-server.so.1: version `SPICE_SERVER_0.11.2' not found (required by kvm)
 
Last edited:
ii pve-qemu-kvm 1.4-17 amd64 Full virtualization on x86 hardware


abbca35bcaae484c7794af4f4bc28fd1 /usr/bin/kvm.old

I was just testing.
 
Did you install the Debian version of "libspice-server1" alongside the Proxmox version (pve-libspice-server1)? This is likely to be true if, for example, you installed the Xorg qxl video driver, like I did. A simple `apt-get purge libspice-server1` cleared this up on my system...

I suspect the problem was that KVM was failing to start properly, even enough to get the version info from the binary, so it never came up far enough to throw a particularly useful error. I was only able to see this level of detail by commenting out the relevant line in the Perl script behind this part of the `qm` utility, but if you run `$(qm showcmd <vmid>)` it should have the same effect. Resolve the conflict which is preventing KVM from starting, and this error should be resolved.

Hope that helps!