VMs won't start - QEMU Binary issue

[Walkmilton]

I've been having trouble since I tried to enable a thunderbolt drive connected to my server. Now whenever I go to start a VM or create a new one, I get the following error

/usr/bin/kvm: symbol lookup error: /lib/x86_64-linux-gnu/libgfrpc.so.0: undefined symbol: dict_getn
command '/usr/bin/kvm --version' failed: exit code 127
TASK ERROR: Detected old QEMU binary ('unknown', at least 3.0 is required)

I've tried searching the forums but not had much luck. I'd be happy to do a reinstall but I really want to recover my home assistant config - I stupidly have lost my backup file despite using it not too long ago to set up. Does anyone know how I could either fix this issue or recover the home assistant VM? I tried creating a backup of it but I get the same error

 

[cheiss]

Hi,

can you please post the output of pveversion -v?
What did you last use to upgrade your host? Using apt upgrade instead of apt full-upgrade can cause issues, for example.

You may also try running apt reinstall pve-qemu-kvm, which reinstalls QEMU and might solve it.

 

[Walkmilton]

Yes I think I used apt upgrade. Here's the output:

proxmox-ve: 8.2.0 (running kernel: 6.8.12-1-pve)
pve-manager: 8.2.4 (running version: 8.2.4/faa83925c9641325)
proxmox-kernel-helper: 8.1.0
proxmox-kernel-6.8: 6.8.12-1
proxmox-kernel-6.8.12-1-pve-signed: 6.8.12-1
proxmox-kernel-6.8.4-2-pve-signed: 6.8.4-2
ceph-fuse: 17.2.7-pve3
corosync: 3.1.7-pve3
criu: 3.17.1-3
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx9
intel-microcode: 3.20240531.1
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-4
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.1
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.3
libpve-access-control: 8.1.4
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.0.7
libpve-cluster-perl: 8.0.7
libpve-common-perl: 8.2.2
libpve-guest-common-perl: 5.1.4
libpve-http-server-perl: 5.1.0
libpve-network-perl: 0.9.8
libpve-rs-perl: 0.8.9
libpve-storage-perl: 8.2.3
libspice-server1: 0.15.1-1
lvm2: 2.03.22-1+b1
lxc-pve: 6.0.0-1
lxcfs: 6.0.1-1
novnc-pve: 1.4.0-3
proxmox-backup-client: 3.2.7-1
proxmox-backup-file-restore: 3.2.7-1
proxmox-firewall: 0.5.0
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.2.3
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.6
proxmox-widget-toolkit: 4.2.3
pve-cluster: 8.0.7
pve-container: 5.1.12
pve-docs: 8.2.3
pve-edk2-firmware: 4.2023.08-4
pve-esxi-import-tools: 0.7.1
pve-firewall: 5.0.7
pve-firmware: 3.13-1
pve-ha-manager: 4.0.5
pve-i18n: 3.2.2
pve-qemu-kvm: 9.0.2-2
pve-xtermjs: 5.3.0-3
qemu-server: 8.2.4
smartmontools: 7.4-2
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.4-pve1

 

[DoubleD]

I recently had issue with MVs not starting (or migrating) b/c of QEMU binary old.

What worked for me:

power down all VMs
Run "apt update;apt full-upgrade;reboot", one PVE host at a time.
I think one of them need one more reboot