guest vm start problem command '/usr/bin/kvm --version' failed: exit code 127

SeLv

Member
Jul 22, 2018
4
0
6
44
Unable to run virtual guests

on start i get following error:
Pls help!

qm start 102
Inconsistency detected by ld.so: ../sysdeps/x86_64/dl-machine.h: 538: elf_machine_rela_relative: Assertion `ELFW(R_TYPE) (reloc->r_info) == R_X86_64_RELATIVE' failed!
command '/usr/bin/kvm --version' failed: exit code 127
internal error: cannot check version of invalid string 'unknown' at /usr/share/perl5/PVE/QemuServer/Helpers.pm line 113.

pveversion -v
proxmox-ve: 6.1-2 (running kernel: 5.3.13-1-pve)
pve-manager: 6.1-5 (running version: 6.1-5/9bf06119)
pve-kernel-5.3: 6.1-1
pve-kernel-helper: 6.1-1
pve-kernel-5.0: 6.0-11
pve-kernel-4.15: 5.4-9
pve-kernel-5.3.13-1-pve: 5.3.13-1
pve-kernel-5.0.21-5-pve: 5.0.21-10
pve-kernel-4.15.18-21-pve: 4.15.18-48
pve-kernel-4.15.18-9-pve: 4.15.18-30
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.2-pve4
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.13-pve1
libpve-access-control: 6.0-5
libpve-apiclient-perl: 3.0-2
libpve-common-perl: 6.0-9
libpve-guest-common-perl: 3.0-3
libpve-http-server-perl: 3.0-3
libpve-storage-perl: 6.1-3
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve3
lxc-pve: 3.2.1-1
lxcfs: 3.0.3-pve60
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.1-2
pve-cluster: 6.1-2
pve-container: 3.0-16
pve-docs: 6.1-3
pve-edk2-firmware: 2.20191127-1
pve-firewall: 4.0-9
pve-firmware: 3.0-4
pve-ha-manager: 3.0-8
pve-i18n: 2.0-3
pve-qemu-kvm: 4.1.1-2
pve-xtermjs: 3.13.2-1
qemu-server: 6.1-4
smartmontools: 7.0-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.2-pve2
 
What happens when you try to update?

Code:
 apt update && apt full-upgrade
 
Hi,
you could apt install debsums and run debsums -s to see if there's any corrupted files in the installed packages. If there are, reinstall the packages with apt install --reinstall <package1> <package2> ... and check the logs for any IO/filesystem errors and if the drives are still healthy.

If there are no corrupted files, you could run a memtest to check your RAM instead.

If there's also no issue there, please share your CPU model and the output of pveversion -v.
 
  • Like
Reactions: iteelion
Hi,
you could apt install debsums and run debsums -s to see if there's any corrupted files in the installed packages. If there are, reinstall the packages with apt install --reinstall <package1> <package2> ... and check the logs for any IO/filesystem errors and if the drives are still healthy.

If there are no corrupted files, you could run a memtest to check your RAM instead.

If there's also no issue there, please share your CPU model and the output of pveversion -v.
You save me thanks!!! There was some corrupted packages.
 
You save me thanks!!! There was some corrupted packages.
I'd still check the logs/hardware to see if everything is fine. There has to be a cause for the corruption after all ;)
 
  • Like
Reactions: iteelion

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!