Issues installing proxmox 8 version on Dell R630

R

redium

Member
Dec 16, 2019
24
0
21
37
Help,

I'm already figting 4 days with proxmox on a Dell R630.
I have installed a vps with pfsense and when i'm trying to startup the VPS it crash and wont will start.

I have already upgraded bios and firmware and downgrade nothing helps.
I have installed on uefi thats not working so now tried on bios with 8 version its not working 7 version is not working.

6.4 version works then upgrade from 6.4 to 7 everything works when i upgarde from 7 to 8 its not working anymore vps wont start.

TASK ERROR: start failed: command '/usr/bin/kvm -id 120 -name 'pfsense,debug-threads=on' -no-shutdown -chardev 'socket,id=qmp,path=/var/run/qemu-server/120.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/120.pid -daemonize -smbios 'type=1,uuid=39807920-ca2f-4574-a11a-2cb33a89de4b' -smp '4,sockets=1,cores=4,maxcpus=4' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-server/bootsplash.jpg' -vnc 'unix:/var/run/qemu-server/120.vnc,password=on' -cpu kvm64,enforce,+kvm_pv_eoi,+kvm_pv_unhalt,+lahf_lm,+sep -m 4096 -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 'vmgenid,guid=6f0ca2f7-b0a4-4c1a-960d-d4573c037292' -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' -iscsi 'initiator-name=iqn.1993-08.org.debian:01:525c75774f9a' -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=scsihw0,bus=pci.0,addr=0x5' -drive 'file=/dev/pve/vm-120-disk-0,if=none,id=drive-scsi0,format=raw,cache=none,aio=io_uring,detect-zeroes=on' -device 'scsi-hd,bus=scsihw0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0,id=scsi0,bootindex=100' -netdev 'type=tap,id=net0,ifname=tap120i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' -device 'virtio-net-pci,mac=12:D4:76:59:07:0E,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=102' -netdev 'type=tap,id=net1,ifname=tap120i1,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' -device 'virtio-net-pci,mac=F2:05:D8:7A:B3:16,netdev=net1,bus=pci.0,addr=0x13,id=net1' -machine 'type=pc-i440fx-6.1+pve0'' failed: got timeout

I have tried to many things to get it worked have changed pve kernels but nothing helps can someone from the proxmox team help me to get finaly this proxmox system worked on dell R630 with Intel(R) Xeon(R) CPU E5-2620 v3

root@pmx70:~# pveversion -v
proxmox-ve: 8.2.0 (running kernel: 5.15.158-2-pve)
pve-manager: 8.2.7 (running version: 8.2.7/3e0176e6bb2ade3b)
proxmox-kernel-helper: 8.1.0
pve-kernel-5.15: 7.4-15
proxmox-kernel-6.8: 6.8.12-2
proxmox-kernel-6.8.12-2-pve-signed: 6.8.12-2
pve-kernel-5.4: 6.4-20
pve-kernel-5.15.158-2-pve: 5.15.158-2
pve-kernel-5.4.203-1-pve: 5.4.203-1
pve-kernel-5.4.106-1-pve: 5.4.106-1
ceph-fuse: 16.2.11+ds-2
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown: residual config
ifupdown2: 3.2.0-1+pmx9
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.4
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.3
libpve-guest-common-perl: 5.1.4
libpve-http-server-perl: 5.1.1
libpve-network-perl: 0.9.8
libpve-rs-perl: 0.8.10
libpve-storage-perl: 8.2.5
libqb0: 1.0.5-1
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 6.0.0-1
lxcfs: 6.0.0-pve2
novnc-pve: 1.4.0-4
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.7
proxmox-widget-toolkit: 4.2.3
pve-cluster: 8.0.7
pve-container: 5.2.0
pve-docs: 8.2.3
pve-edk2-firmware: 4.2023.08-4
pve-esxi-import-tools: 0.7.2
pve-firewall: 5.0.7
pve-firmware: 3.13-2
pve-ha-manager: 4.0.5
pve-i18n: 3.2.3
pve-qemu-kvm: 9.0.2-3
pve-xtermjs: 5.3.0-3
qemu-server: 8.2.4
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.6-pve1
 
What logs do you want to see proxmox provides only the following errors when I'm trying to start the VMid 120 in the WebGUI or in the console

-------------------

()
VM 120 qmp command 'set_password' failed - unable to connect to VM 120 qmp socket - timeout after 51 retries
TASK ERROR: Failed to run vncproxy.
()
trying to acquire lock...
TASK ERROR: can't lock file '/var/lock/qemu-server/lock-120.conf' - got timeout

Header
Proxmox
Virtual Environment 8.2.7
Virtual Machine 120 (pfsense) on node 'pmx70'
No Tags
Logs
()
TASK ERROR: start failed: command '/usr/bin/kvm -id 120 -name 'pfsense,debug-threads=on' -no-shutdown -chardev 'socket,id=qmp,path=/var/run/qemu-server/120.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/120.pid -daemonize -smbios 'type=1,uuid=39807920-ca2f-4574-a11a-2cb33a89de4b' -smp '4,sockets=1,cores=4,maxcpus=4' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-server/bootsplash.jpg' -vnc 'unix:/var/run/qemu-server/120.vnc,password=on' -cpu kvm64,enforce,+kvm_pv_eoi,+kvm_pv_unhalt,+lahf_lm,+sep -m 4096 -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 'vmgenid,guid=6f0ca2f7-b0a4-4c1a-960d-d4573c037292' -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:525c75774f9a' -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=scsihw0,bus=pci.0,addr=0x5' -drive 'file=/dev/pve/vm-120-disk-0,if=none,id=drive-scsi0,format=raw,cache=none,aio=io_uring,detect-zeroes=on' -device 'scsi-hd,bus=scsihw0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0,id=scsi0,bootindex=100' -netdev 'type=tap,id=net0,ifname=tap120i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' -device 'virtio-net-pci,mac=12:D4:76:59:07:0E,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=102' -netdev 'type=tap,id=net1,ifname=tap120i1,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' -device 'virtio-net-pci,mac=F2:05:D8:7A:B3:16,netdev=net1,bus=pci.0,addr=0x13,id=net1' -netdev 'type=tap,id=net2,ifname=tap120i2,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' -device 'virtio-net-pci,mac=BC:24:11:3A:23:BD,netdev=net2,bus=pci.0,addr=0x14,id=net2' -device virtio-iommu-pci -machine 'type=pc-i440fx-6.2+pve0'' failed: got timeout

TASK ERROR: connection timed out
 
Why the timeout occured for example. What about dmesg? Anything in /var/log/syslog at the time?

Maybe run the command that got a timeout interactively in a terminal and see if it returns or not.
 
I have found this in journalctl
Oct 13 18:18:38 pmx70 pvedaemon[1442]: VM 120 qmp command failed - VM 120 qmp command 'query-proxmox-support' failed - unable to connect to VM 120 qmp socket - t>
Oct 13 18:18:38 pmx70 pvestatd[1384]: VM 120 qmp command failed - VM 120 qmp command 'query-proxmox-support' failed - unable to connect to VM 120 qmp socket - ti>
Oct 13 18:18:43 pmx70 kernel: vmbr205: port 2(fwpr120p0) entered blocking state
Oct 13 18:18:43 pmx70 kernel: vmbr205: port 2(fwpr120p0) entered forwarding state
Oct 13 18:18:44 pmx70 kernel: fwbr120i0: port 1(fwln120i0) entered blocking state
Oct 13 18:18:44 pmx70 kernel: fwbr120i0: port 1(fwln120i0) entered disabled state
Oct 13 18:18:44 pmx70 kernel: device fwln120i0 entered promiscuous mode
Oct 13 18:18:44 pmx70 kernel: fwbr120i0: port 1(fwln120i0) entered blocking state
Oct 13 18:18:44 pmx70 kernel: fwbr120i0: port 1(fwln120i0) entered forwarding state
Oct 13 18:18:44 pmx70 kernel: fwbr120i0: port 2(tap120i0) entered blocking state
Oct 13 18:18:44 pmx70 kernel: fwbr120i0: port 2(tap120i0) entered disabled state
Oct 13 18:18:44 pmx70 kernel: fwbr120i0: port 2(tap120i0) entered blocking state
Oct 13 18:18:44 pmx70 kernel: fwbr120i0: port 2(tap120i0) entered forwarding state
Oct 13 18:18:44 pmx70 pvestatd[1384]: status update time (13.870 seconds)
Oct 13 18:18:45 pmx70 kernel: device tap120i1 entered promiscuous mode
Oct 13 18:18:45 pmx70 kernel: vmbr90: port 2(tap120i1) entered blocking state
Oct 13 18:18:45 pmx70 kernel: vmbr90: port 2(tap120i1) entered disabled state
Oct 13 18:18:45 pmx70 kernel: device bond0.90 entered promiscuous mode
Oct 13 18:18:46 pmx70 pvedaemon[1442]: VM 120 qmp command failed - VM 120 qmp command 'query-proxmox-support' failed - unable to connect to VM 120 qmp socket - t>
Oct 13 18:18:46 pmx70 pvedaemon[240143]: starting vnc proxy UPID:pmx70:0003AA0F:005EF5A2:670BF2E6:vncproxy:120:root@pam:
Oct 13 18:18:46 pmx70 pvedaemon[1442]: <root@pam> starting task UPID:pmx70:0003AA0F:005EF5A2:670BF2E6:vncproxy:120:root@pam:
Oct 13 18:18:52 pmx70 pvestatd[1384]: VM 120 qmp command failed - VM 120 qmp command 'query-proxmox-support' failed - unable to connect to VM 120 qmp socket - ti>
Oct 13 18:18:57 pmx70 pvedaemon[1441]: VM 120 qmp command failed - VM 120 qmp command 'query-proxmox-support' failed - unable to connect to VM 120 qmp socket - t>
Oct 13 18:18:59 pmx70 pveproxy[227221]: proxy detected vanished client connection
Oct 13 18:18:59 pmx70 kernel: vmbr90: port 2(tap120i1) entered blocking state
Oct 13 18:18:59 pmx70 kernel: vmbr90: port 2(tap120i1) entered forwarding state
Oct 13 18:18:59 pmx70 pve-firewall[1381]: firewall update time (9.593 seconds)
Oct 13 18:18:59 pmx70 pvestatd[1384]: status update time (15.576 seconds)
Oct 13 18:19:00 pmx70 pvedaemon[239962]: start failed: command '/usr/bin/kvm -id 120 -name 'pfsense,debug-threads=on' -no-shutdown -chardev 'socket,id=qmp,path=/>
Oct 13 18:19:01 pmx70 kernel: device tap120i2 entered promiscuous mode
Oct 13 18:19:01 pmx70 kernel: vmbr76: port 2(tap120i2) entered blocking state
Oct 13 18:19:01 pmx70 kernel: vmbr76: port 2(tap120i2) entered disabled state
Oct 13 18:19:01 pmx70 kernel: device bond0.76 entered promiscuous mode
Oct 13 18:19:03 pmx70 pvedaemon[1440]: VM 120 qmp command failed - VM 120 qmp command 'query-proxmox-support' failed - unable to connect to VM 120 qmp socket - t>
Oct 13 18:19:03 pmx70 pvedaemon[1440]: <root@pam> end task UPID:pmx70:0003A95A:005EEF09:670BF2D5:qmstart:120:root@pam: start failed: command '/usr/bin/kvm -id 12>
Oct 13 18:19:07 pmx70 pvestatd[1384]: VM 120 qmp command failed - VM 120 qmp command 'query-proxmox-support' failed - unable to connect to VM 120 qmp socket - ti>
Oct 13 18:19:09 pmx70 pvedaemon[240143]: connection timed out
Oct 13 18:19:09 pmx70 pvedaemon[1442]: <root@pam> end task UPID:pmx70:0003AA0F:005EF5A2:670BF2E6:vncproxy:120:root@pam: connection timed out
Oct 13 18:19:13 pmx70 kernel: vmbr76: port 2(tap120i2) entered blocking state
Oct 13 18:19:13 pmx70 kernel: vmbr76: port 2(tap120i2) entered forwarding state
Oct 13 18:19:13 pmx70 pvestatd[1384]: status update time (13.478 seconds)
Oct 13 18:19:14 pmx70 kernel: vmbr76: port 2(tap120i2) entered disabled state

Oct 13 18:19:14 pmx70 kernel: vmbr76: port 2(tap120i2) entered disabled state
Oct 13 18:19:21 pmx70 pvestatd[1384]: VM 120 qmp command failed - VM 120 qmp command 'query-proxmox-support' failed - unable to connect to VM 120 qmp socket - ti>
Oct 13 18:19:24 pmx70 pvedaemon[1440]: VM 120 qmp command failed - VM 120 qmp command 'query-proxmox-support' failed - unable to connect to VM 120 qmp socket - t>
Oct 13 18:19:24 pmx70 pvedaemon[240315]: starting vnc proxy UPID:pmx70:0003AABB:005F0466:670BF30C:vncproxy:120:root@pam:
Oct 13 18:19:24 pmx70 pvedaemon[1440]: <root@pam> starting task UPID:pmx70:0003AABB:005F0466:670BF30C:vncproxy:120:root@pam:
Oct 13 18:19:26 pmx70 kernel: device bond0.76 left promiscuous mode
Oct 13 18:19:26 pmx70 pve-firewall[1381]: firewall update time (6.014 seconds)
Oct 13 18:19:26 pmx70 pvestatd[1384]: status update time (13.035 seconds)
Oct 13 18:19:26 pmx70 pvedaemon[240358]: stop VM 120: UPID:pmx70:0003AAE6:005F0548:670BF30E:qmstop:120:root@pam:
Oct 13 18:19:26 pmx70 pvedaemon[1441]: <root@pam> starting task UPID:pmx70:0003AAE6:005F0548:670BF30E:qmstop:120:root@pam:
Oct 13 18:19:27 pmx70 kernel: vmbr90: port 2(tap120i1) entered disabled state
Oct 13 18:19:28 pmx70 pvedaemon[1442]: VM 120 qmp command failed - VM 120 qmp command 'query-proxmox-support' failed - unable to connect to VM 120 qmp socket - t>
Oct 13 18:19:31 pmx70 pvedaemon[240358]: VM 120 qmp command failed - VM 120 qmp command 'quit' failed - unable to connect to VM 120 qmp socket - timeout after 51>
Oct 13 18:19:31 pmx70 pvedaemon[240358]: VM quit/powerdown failed - terminating now with SIGTERM
Oct 13 18:19:33 pmx70 qm[240359]: VM 120 qmp command failed - VM 120 qmp command 'set_password' failed - unable to connect to VM 120 qmp socket - timeout after 5>
Oct 13 18:19:33 pmx70 pvedaemon[240315]: Failed to run vncproxy.
Oct 13 18:19:33 pmx70 pvedaemon[1440]: <root@pam> end task UPID:pmx70:0003AABB:005F0466:670BF30C:vncproxy:120:root@pam: Failed to run vncproxy.
Oct 13 18:19:34 pmx70 pvestatd[1384]: VM 120 qmp command failed - VM 120 qmp command 'query-proxmox-support' failed - unable to connect to VM 120 qmp socket - ti>
Oct 13 18:19:41 pmx70 pvedaemon[240358]: VM still running - terminating now with SIGKILL
Oct 13 18:19:41 pmx70 kernel: device bond0.90 left promiscuous mode
Oct 13 18:19:41 pmx70 kernel: fwbr120i0: port 2(tap120i0) entered disabled state
Oct 13 18:19:41 pmx70 kernel: fwbr120i0: port 2(tap120i0) entered disabled state
Oct 13 18:19:41 pmx70 pvestatd[1384]: status update time (15.643 seconds)
Oct 13 18:19:42 pmx70 systemd[1]: 120.scope: Deactivated successfully.
Oct 13 18:19:42 pmx70 systemd[1]: 120.scope: Consumed 1min 11.637s CPU time.
Oct 13 18:19:42 pmx70 pvedaemon[1441]: <root@pam> end task UPID:pmx70:0003AAE6:005F0548:670BF30E:qmstop:120:root@pam: OK
Oct 13 18:20:02 pmx70 pvedaemon[240521]: start VM 120: UPID:pmx70:0003AB89:005F135C:670BF332:qmstart:120:root@pam:
Oct 13 18:20:02 pmx70 pvedaemon[1440]: <root@pam> starting task UPID:pmx70:0003AB89:005F135C:670BF332:qmstart:120:root@pam:
Oct 13 18:20:03 pmx70 systemd[1]: Started 120.scope.
Oct 13 18:20:04 pmx70 kernel: device tap120i0 entered promiscuous mode
Oct 13 18:20:04 pmx70 kernel: fwbr120i0: port 1(fwln120i0) entered disabled state
Oct 13 18:20:04 pmx70 kernel: vmbr205: port 2(fwpr120p0) entered disabled state
Oct 13 18:20:04 pmx70 kernel: device fwln120i0 left promiscuous mode
Oct 13 18:20:04 pmx70 kernel: fwbr120i0: port 1(fwln120i0) entered disabled state
Oct 13 18:20:04 pmx70 kernel: device fwpr120p0 left promiscuous mode
Oct 13 18:20:04 pmx70 kernel: vmbr205: port 2(fwpr120p0) entered disabled state
Oct 13 18:20:08 pmx70 pvedaemon[240550]: start VM 120: UPID:pmx70:0003ABA6:005F158D:670BF338:qmstart:120:root@pam:
Oct 13 18:20:08 pmx70 pvedaemon[1442]: <root@pam> starting task UPID:pmx70:0003ABA6:005F158D:670BF338:qmstart:120:root@pam:
Oct 13 18:20:11 pmx70 pvedaemon[1441]: VM 120 qmp command failed - VM 120 qmp command 'query-proxmox-support' failed - got timeout
 
LnxBil said:
Why the timeout occured for example. What about dmesg? Anything in /var/log/syslog at the time?

Maybe run the command that got a timeout interactively in a terminal and see if it returns or not.
Click to expand...


Here is the output from console when trying to start the VM 120

Code: 
root@pmx70:~# qm start 120
start failed: command '/usr/bin/kvm -id 120 -name 'pfsense,debug-threads=on' -no-shutdown -chardev 'socket,id=qmp,path=/var/run/qemu-server/120.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/120.pid -daemonize -smbios 'type=1,uuid=39807920-ca2f-4574-a11a-2cb33a89de4b' -smp '4,sockets=1,cores=4,maxcpus=4' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-server/bootsplash.jpg' -vnc 'unix:/var/run/qemu-server/120.vnc,password=on' -cpu kvm64,enforce,+kvm_pv_eoi,+kvm_pv_unhalt,+lahf_lm,+sep -m 4096 -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 'vmgenid,guid=6f0ca2f7-b0a4-4c1a-960d-d4573c037292' -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:525c75774f9a' -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=scsihw0,bus=pci.0,addr=0x5' -drive 'file=/dev/pve/vm-120-disk-0,if=none,id=drive-scsi0,format=raw,cache=none,aio=io_uring,detect-zeroes=on' -device 'scsi-hd,bus=scsihw0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0,id=scsi0,bootindex=100' -netdev 'type=tap,id=net0,ifname=tap120i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' -device 'virtio-net-pci,mac=12:D4:76:59:07:0E,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=102' -netdev 'type=tap,id=net1,ifname=tap120i1,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' -device 'virtio-net-pci,mac=F2:05:D8:7A:B3:16,netdev=net1,bus=pci.0,addr=0x13,id=net1' -netdev 'type=tap,id=net2,ifname=tap120i2,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' -device 'virtio-net-pci,mac=BC:24:11:3A:23:BD,netdev=net2,bus=pci.0,addr=0x14,id=net2' -device virtio-iommu-pci -machine 'type=pc-i440fx-6.2+pve0'' failed: got timeout
 
redium said:
Here is the output from console when trying to start the VM 120

Code: 
root@pmx70:~# qm start 120
start failed: command '/usr/bin/kvm -id 120 -name 'pfsense,debug-threads=on' -no-shutdown -chardev 'socket,id=qmp,path=/var/run/qemu-server/120.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/120.pid -daemonize -smbios 'type=1,uuid=39807920-ca2f-4574-a11a-2cb33a89de4b' -smp '4,sockets=1,cores=4,maxcpus=4' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-server/bootsplash.jpg' -vnc 'unix:/var/run/qemu-server/120.vnc,password=on' -cpu kvm64,enforce,+kvm_pv_eoi,+kvm_pv_unhalt,+lahf_lm,+sep -m 4096 -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 'vmgenid,guid=6f0ca2f7-b0a4-4c1a-960d-d4573c037292' -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:525c75774f9a' -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=scsihw0,bus=pci.0,addr=0x5' -drive 'file=/dev/pve/vm-120-disk-0,if=none,id=drive-scsi0,format=raw,cache=none,aio=io_uring,detect-zeroes=on' -device 'scsi-hd,bus=scsihw0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0,id=scsi0,bootindex=100' -netdev 'type=tap,id=net0,ifname=tap120i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' -device 'virtio-net-pci,mac=12:D4:76:59:07:0E,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=102' -netdev 'type=tap,id=net1,ifname=tap120i1,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' -device 'virtio-net-pci,mac=F2:05:D8:7A:B3:16,netdev=net1,bus=pci.0,addr=0x13,id=net1' -netdev 'type=tap,id=net2,ifname=tap120i2,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' -device 'virtio-net-pci,mac=BC:24:11:3A:23:BD,netdev=net2,bus=pci.0,addr=0x14,id=net2' -device virtio-iommu-pci -machine 'type=pc-i440fx-6.2+pve0'' failed: got timeout
Click to expand...
Yes, take now the command (starting with kvm) and execute it. Its error message may lead to a solution
 
The first time I did the command manual it gives this error:

kvm: cannot create PID file: Cannot lock pid file: Resource temporarily unavailable

Then I tried again with the same KVM /usr/bin/kvm command, and it worked. The VPS is working again, but I don't see a solution that works directly from Webgui.
 
redium said:
kvm: cannot create PID file: Cannot lock pid file: Resource temporarily unavailable
Click to expand...
We need to find out where the pidfile is created and why the resource was temporarily unavailable. This sound like some memory problem. How much memory is reported? Please provide the output of free and df -aT in code tags.
 
Memory output.

Code: 
free
               total        used        free      shared  buff/cache   available
Mem:       131903164     6957804   125221632       56320      667920   124945360
Swap:        8388604           0     8388604


Code: 
df -aT
Filesystem           Type        1K-blocks    Used Available Use% Mounted on
sysfs                sysfs               0       0         0    - /sys
proc                 proc                0       0         0    - /proc
udev                 devtmpfs     65916792       0  65916792   0% /dev
devpts               devpts              0       0         0    - /dev/pts
tmpfs                tmpfs        13190320    3288  13187032   1% /run
/dev/mapper/pve-root ext4         98497780 5472052  87976180   6% /
securityfs           securityfs          0       0         0    - /sys/kernel/security
tmpfs                tmpfs        65951580   49920  65901660   1% /dev/shm
tmpfs                tmpfs            5120       0      5120   0% /run/lock
cgroup2              cgroup2             0       0         0    - /sys/fs/cgroup
pstore               pstore              0       0         0    - /sys/fs/pstore
bpf                  bpf                 0       0         0    - /sys/fs/bpf
systemd-1            -                   -       -         -    - /proc/sys/fs/binfmt_misc
tracefs              tracefs             0       0         0    - /sys/kernel/tracing
hugetlbfs            hugetlbfs           0       0         0    - /dev/hugepages
debugfs              debugfs             0       0         0    - /sys/kernel/debug
mqueue               mqueue              0       0         0    - /dev/mqueue
fusectl              fusectl             0       0         0    - /sys/fs/fuse/connections
configfs             configfs            0       0         0    - /sys/kernel/config
none                 ramfs               0       0         0    - /run/credentials/systemd-sysusers.service
none                 ramfs               0       0         0    - /run/credentials/systemd-tmpfiles-setup-dev.service
none                 ramfs               0       0         0    - /run/credentials/systemd-sysctl.service
none                 ramfs               0       0         0    - /run/credentials/systemd-tmpfiles-setup.service
binfmt_misc          binfmt_misc         0       0         0    - /proc/sys/fs/binfmt_misc
sunrpc               rpc_pipefs          0       0         0    - /run/rpc_pipefs
lxcfs                fuse.lxcfs          0       0         0    - /var/lib/lxcfs
/dev/fuse            fuse           131072      16    131056   1% /etc/pve
tmpfs                tmpfs        13190316       0  13190316   0% /run/user/0
 
Yes i have shutdown again the vps and tried to get it worked again on the normal way by start vps but its not working

Screenshot 2024-10-13 at 21.13.43.png

Code: 
ls -lha /run/qemu-server/
total 0
drwxr-xr-x  2 root root  120 Oct 13 21:14 .
drwxr-xr-x 28 root root 1.4K Oct 13 20:56 ..
srwxr-x---  1 root root    0 Oct 13 21:12 120.qmp
srwxr-x---  1 root root    0 Oct 13 21:13 120.vnc
-rw-r--r--  1 root root    0 Oct 13 21:13 pci-id-reservations
-rw-r--r--  1 root root    0 Oct 13 01:02 pci-id-reservations.lock

Then I tried the kvm command.

Code: 
/usr/bin/kvm -id 120 -name 'pfsense,debug-threads=on' -no-shutdown -chardev 'socket,id=qmp,path=/var/run/qemu-server/120.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/120.pid -daemonize -smbios 'type=1,uuid=39807920-ca2f-4574-a11a-2cb33a89de4b' -smp '4,sockets=1,cores=4,maxcpus=4' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-server/bootsplash.jpg' -vnc 'unix:/var/run/qemu-server/120.vnc,password=on' -cpu kvm64,enforce,+kvm_pv_eoi,+kvm_pv_unhalt,+lahf_lm,+sep -m 4096 -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 'vmgenid,guid=6f0ca2f7-b0a4-4c1a-960d-d4573c037292' -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:525c75774f9a' -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=scsihw0,bus=pci.0,addr=0x5' -drive 'file=/dev/pve/vm-120-disk-0,if=none,id=drive-scsi0,format=raw,cache=none,aio=io_uring,detect-zeroes=on' -device 'scsi-hd,bus=scsihw0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0,id=scsi0,bootindex=100' -netdev 'type=tap,id=net0,ifname=tap120i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' -device 'virtio-net-pci,mac=12:D4:76:59:07:0E,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=102' -netdev 'type=tap,id=net1,ifname=tap120i1,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' -device 'virtio-net-pci,mac=F2:05:D8:7A:B3:16,netdev=net1,bus=pci.0,addr=0x13,id=net1' -netdev 'type=tap,id=net2,ifname=tap120i2,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' -device 'virtio-net-pci,mac=BC:24:11:3A:23:BD,netdev=net2,bus=pci.0,addr=0x14,id=net2' -netdev 'type=tap,id=net3,ifname=tap120i3,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' -device 'virtio-net-pci,mac=BC:24:11:C6:44:D7,netdev=net3,bus=pci.0,addr=0x15,id=net3' -device virtio-iommu-pci -machine 'type=pc-i440fx-6.2+pve0'

Then the vps starts and I see now this in /run/qemu-server

Code: 
ls -lha /run/qemu-server/
total 4.0K
drwxr-xr-x  2 root root  140 Oct 13 21:16 .
drwxr-xr-x 28 root root 1.4K Oct 13 20:56 ..
-rw-------  1 root root    7 Oct 13 21:16 120.pid
srwxr-x---  1 root root    0 Oct 13 21:16 120.qmp
srwxr-x---  1 root root    0 Oct 13 21:16 120.vnc
-rw-r--r--  1 root root    0 Oct 13 21:13 pci-id-reservations
-rw-r--r--  1 root root    0 Oct 13 01:02 pci-id-reservations.lock
 
The only thing that comes to mind is to start the process with strace and log everything including threads in a file and try to inspect what takes so long to startup the process that will yield to the timeout in PVE.
 
You must log in or register to reply here.

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!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

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!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back