Proxmox VMs are not starting

jyotib

New Member
Apr 9, 2025
2
0
1
When I try to start my VM using qm start 110 command it is giving this error "
qm start 110
start failed: command '/usr/bin/kvm -id 110 -name 'interface3-1,debug-threads=on' -no-shutdown -chardev 'socket,id=qmp,path=/var/run/qemu-server/110.qmp,server=on,wait=off' -mon 'chardev=qmp,mode=control' -chardev 'socket,id=qmp-event,path=/var/run/qmeventd.sock,reconnect=5' -mon 'chardev=qmp-event,mode=control' -pidfile /var/run/qemu-server/110.pid -daemonize -smbios 'type=1,uuid=db81e01b-4340-4186-a7e1-e9e8d12f0c57' -smp '16,sockets=2,cores=8,maxcpus=16' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-server/bootsplash.jpg' -vnc 'unix:/var/run/qemu-server/110.vnc,password=on' -cpu host,+kvm_pv_eoi,+kvm_pv_unhalt -m 60000 -object 'iothread,id=iothread-virtioscsi0' -object 'iothread,id=iothread-virtioscsi1' -device 'pci-bridge,id=pci.1,chassis_nr=1,bus=pci.0,addr=0x1e' -device 'pci-bridge,id=pci.2,chassis_nr=2,bus=pci.0,addr=0x1f' -device 'pci-bridge,id=pci.3,chassis_nr=3,bus=pci.0,addr=0x5' -device 'vmgenid,guid=112e4ef8-bc9a-4350-9abe-be0a48a36d0f' -device 'piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2' -device 'usb-tablet,id=tablet,bus=uhci.0,port=1' -device 'VGA,id=vga,bus=pci.0,addr=0x2' -device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3,free-page-reporting=on' -iscsi 'initiator-name=iqn.1993-08.org.debian:01:a456782c447' -drive 'if=none,id=drive-ide2,media=cdrom,aio=io_uring' -device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=101' -device 'virtio-scsi-pci,id=virtioscsi0,bus=pci.3,addr=0x1,iothread=iothread-virtioscsi0' -drive 'file=/dev/pve/vm-110-disk-0,if=none,id=drive-scsi0,format=raw,cache=none,aio=io_uring,detect-zeroes=on' -device 'scsi-hd,bus=virtioscsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0,id=scsi0,bootindex=100' -device 'virtio-scsi-pci,id=virtioscsi1,bus=pci.3,addr=0x2,iothread=iothread-virtioscsi1' -drive 'file=/dev/vol-data/vm-110-disk-1,if=none,id=drive-scsi1,discard=on,format=raw,cache=none,aio=io_uring,detect-zeroes=unmap' -device 'scsi-hd,bus=virtioscsi1.0,channel=0,scsi-id=0,lun=1,drive=drive-scsi1,id=scsi1' -netdev 'type=tap,id=net0,ifname=tap110i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' -device 'virtio-net-pci,mac=DA:4D:92:DE:81:64,netdev=net0,bus=pci.0,addr=0x12,id=net0,rx_queue_size=1024,tx_queue_size=1024,bootindex=102' -netdev 'type=tap,id=net1,ifname=tap110i1,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' -device 'virtio-net-pci,mac=D2:53:9E:C1:8C:B2,netdev=net1,bus=pci.0,addr=0x13,id=net1,rx_queue_size=1024,tx_queue_size=1024' -machine 'type=pc+pve0'' failed: got timeout"
 
Hi,
please share your pveversion -v and the output of qm config 110 as well as cat /etc/pve/storage.cfg
 
pveversion -v
proxmox-ve: 8.0.1 (running kernel: 6.2.16-3-pve)
pve-manager: 8.0.3 (running version: 8.0.3/bbf3993334bfa916)
pve-kernel-6.2: 8.0.2
pve-kernel-5.15: 7.4-4
pve-kernel-6.2.16-3-pve: 6.2.16-3
pve-kernel-5.15.108-1-pve: 5.15.108-1
pve-kernel-5.15.102-1-pve: 5.15.102-1
ceph-fuse: 16.2.11+ds-2
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx2
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-3
libknet1: 1.25-pve1
libproxmox-acme-perl: 1.4.6
libproxmox-backup-qemu0: 1.4.0
libproxmox-rs-perl: 0.3.0
libpve-access-control: 8.0.3
libpve-apiclient-perl: 3.3.1
libpve-common-perl: 8.0.5
libpve-guest-common-perl: 5.0.3
libpve-http-server-perl: 5.0.3
libpve-rs-perl: 0.8.3
libpve-storage-perl: 8.0.1
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 5.0.2-4
lxcfs: 5.0.3-pve3
novnc-pve: 1.4.0-2
proxmox-backup-client: 2.99.0-1
proxmox-backup-file-restore: 2.99.0-1
proxmox-kernel-helper: 8.0.2
proxmox-mail-forward: 0.1.1-1
proxmox-mini-journalreader: 1.4.0
proxmox-widget-toolkit: 4.0.5
pve-cluster: 8.0.1
pve-container: 5.0.3
pve-docs: 8.0.3
pve-edk2-firmware: 3.20230228-4
pve-firewall: 5.0.2
pve-firmware: 3.7-1
pve-ha-manager: 4.0.2
pve-i18n: 3.0.4
pve-qemu-kvm: 8.0.2-3
pve-xtermjs: 4.16.0-3
qemu-server: 8.0.6
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.1.12-pve1

cat /etc/pve/storage.cfg
dir: local
path /var/lib/vz
content iso,backup,vztmpl

lvmthin: local-lvm
thinpool data
vgname pve
content rootdir,images

lvmthin: vmstrg
thinpool vmstrg
vgname vol-data
content rootdir,images

lvmthin: vmstrg1
thinpool vmstrg1
vgname vmstrg1
content images,rootdir
nodes r1srv9,r1srv10

pbs: proxmoxbak
datastore DC1
server 192.168.11.200
content backup
fingerprint 0f:77:c2:22:19:4e:54:f5:85:3b:6b:5a:8e:5f:b3:37:af:fd:03:cd:93:d0:7b:74:4d:e7:d4:92:26:49:85:df
prune-backups keep-all=1
username root@pam

pbs: proxmoxbakDC2
datastore DC2
server 192.168.11.200
content backup
fingerprint 0f:77:c2:22:19:4e:54:f5:85:3b:6b:5a:8e:5f:b3:37:af:fd:03:cd:93:d0:7b:74:4d:e7:d4:92:26:49:85:df
prune-backups keep-all=1
username root@pam

qm config 110
boot: order=scsi0;ide2;net0
cores: 8
cpu: host
ide2: none,media=cdrom
memory: 60000
meta: creation-qemu=7.1.0,ctime=1679759417
name: interface3-1
net0: virtio=DA:4D:92:DE:81:64,bridge=vmbr1
net1: virtio=D2:53:9E:C1:8C:B2,bridge=vmbr0,firewall=1
numa: 0
ostype: l26
scsi0: local-lvm:vm-110-disk-0,iothread=1,size=100G
scsi1: vmstrg:vm-110-disk-1,discard=on,iothread=1,size=9000G
scsihw: virtio-scsi-single
smbios1: uuid=db81e01b-4340-4186-a7e1-e9e8d12f0c57
sockets: 2
tags: interface3-1-rack1;interface3-1-rack1-192.168.80.5-192.168.11.72
vmgenid: 112e4ef8-bc9a-4350-9abe-be0a48a36d0f
 
Hi,
proxmox-ve: 8.0.1 (running kernel: 6.2.16-3-pve)
this means nearly 2 years without (security) updates. The current version is 8.4.x:
https://pve.proxmox.com/wiki/Package_Repositories
https://pve.proxmox.com/pve-docs/chapter-sysadmin.html#system_software_updates

qm config 110
...
memory: 60000
How much (free) memory does your host have? It can take a while to prepare. You can try starting the VM with a custom timeout, e.g. qm start 110 --timeout 300 to see if that helps.

If that doesn't help, please share the system logs/journal from around the time of the issue.
 
  • Like
Reactions: UdoB