TASK ERROR: start failed: command '/usr/bin/kvm -id 100

T

TipokS

New Member
Oct 27, 2022
8
1
3
I will try to start VM but doesn't work
how should i do.

TASK ERROR: start failed: command '/usr/bin/kvm -id 100 -name remote -chardev 'socket,id=qmp,path=/var/run/qemu-server/100.qmp,server,nowait' -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/100.pid -daemonize -smbios 'type=1,uuid=f3881bad-f17d-4e74-99b1-c3eb49defe76' -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/100.vnc,x509,password -no-hpet -cpu 'kvm64,+lahf_lm,+sep,+kvm_pv_unhalt,+kvm_pv_eoi,hv_spinlocks=0x1fff,hv_vapic,hv_time,hv_reset,hv_vpindex,hv_runtime,hv_relaxed,hv_synic,hv_stimer,enforce' -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 '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:e3f85e9879d6' -drive 'file=/var/lib/vz/images/100/vm-100-disk-0.raw,if=none,id=drive-ide0,cache=writeback,format=raw,aio=threads,detect-zeroes=on' -device 'ide-hd,bus=ide.0,unit=0,drive=drive-ide0,id=ide0,bootindex=100' -drive 'if=none,id=drive-ide2,media=cdrom,aio=threads' -device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200' -netdev 'type=tap,id=net0,ifname=tap100i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown' -device 'e1000,mac=EA:84:76:B8:9A:DE,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300' -netdev 'type=tap,id=net1,ifname=tap100i1,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown' -device 'e1000,mac=6E:DF:8C:16:8B:CE,netdev=net1,bus=pci.0,addr=0x13,id=net1,bootindex=301' -rtc 'driftfix=slew,base=localtime' -machine 'type=pc' -global 'kvm-pit.lost_tick_policy=discard'' failed: got timeout
 
Please post the whole VM start task log, as there might be some more messages of significance in there.
  • Do you see any messages in the journalctl syslogs when starting this VM?
  • What is this VM's configuration? cat /etc/pve/qemu-server/100.conf
 
in Journalctl
Oct 28 09:39:00 pvestkc systemd[1]: Starting Proxmox VE replication runner...
Oct 28 09:39:02 pvestkc pvedaemon[1971]: <root@pam> starting task UPID:pvestkc:00005BC4:0011046C:635B40C6:qmstart:100:root@pam:
Oct 28 09:39:02 pvestkc pvedaemon[23492]: start VM 100: UPID:pvestkc:00005BC4:0011046C:635B40C6:qmstart:100:root@pam:
Oct 28 09:39:04 pvestkc pvedaemon[1971]: <root@pam> starting task UPID:pvestkc:00005BCD:0011050B:635B40C8:qmstart:200:root@pam:
Oct 28 09:39:04 pvestkc pvedaemon[23501]: start VM 200: UPID:pvestkc:00005BCD:0011050B:635B40C8:qmstart:200:root@pam:
Oct 28 09:39:07 pvestkc pvestatd[1836]: status update time (8.232 seconds)
Oct 28 09:39:08 pvestkc systemd[1]: Started 100.scope.
Oct 28 09:39:10 pvestkc systemd[1]: Started 200.scope.
Oct 28 09:39:10 pvestkc systemd-udevd[23529]: Could not generate persistent MAC address for tap100i0: No such file or directory
Oct 28 09:39:11 pvestkc rrdcached[1599]: queue_thread_main: rrd_update_r (/var/lib/rrdcached/db/pve2-vm/100) failed with status -1. (/var/lib/rrdcached/db/pve2-vm/100: il
Oct 28 09:39:13 pvestkc systemd-udevd[23561]: Could not generate persistent MAC address for tap200i0: No such file or directory
Oct 28 09:39:17 pvestkc pvestatd[1836]: status update time (8.788 seconds)
Oct 28 09:39:25 pvestkc pvedaemon[23393]: start failed: command '/usr/bin/kvm -id 400 -name Comanche-Redhat -chardev 'socket,id=qmp,path=/var/run/qemu-server/400.qmp,serv
Oct 28 09:39:25 pvestkc pvedaemon[1970]: <root@pam> end task UPID:pvestkc:00005B61:0010FEF3:635B40B8:qmstart:400:root@pam: start failed: command '/usr/bin/kvm -id 400 -na
Oct 28 09:39:26 pvestkc pveproxy[15213]: worker exit
Oct 28 09:39:27 pvestkc pveproxy[2152]: worker 15213 finished
Oct 28 09:39:27 pvestkc pveproxy[2152]: starting 1 worker(s)
Oct 28 09:39:27 pvestkc pveproxy[2152]: worker 23613 started
Oct 28 09:39:28 pvestkc pvedaemon[23410]: start failed: command '/usr/bin/kvm -id 800 -name CentOS72019 -chardev 'socket,id=qmp,path=/var/run/qemu-server/800.qmp,server,n
Oct 28 09:39:28 pvestkc pvedaemon[14234]: <root@pam> end task UPID:pvestkc:00005B72:00110017:635B40BB:qmstart:800:root@pam: start failed: command '/usr/bin/kvm -id 800 -n
Oct 28 09:39:29 pvestkc pvestatd[1836]: status update time (11.344 seconds)
Oct 28 09:39:31 pvestkc kernel: device tap400i0 entered promiscuous mode
Oct 28 09:39:32 pvestkc kernel: vmbr0: port 2(tap400i0) entered blocking state
Oct 28 09:39:32 pvestkc kernel: vmbr0: port 2(tap400i0) entered disabled state
Oct 28 09:39:32 pvestkc kernel: vmbr0: port 2(tap400i0) entered blocking state
Oct 28 09:39:32 pvestkc kernel: vmbr0: port 2(tap400i0) entered forwarding state
Oct 28 09:39:34 pvestkc kernel: device tap800i0 entered promiscuous mode
Oct 28 09:39:35 pvestkc systemd-udevd[23648]: Could not generate persistent MAC address for fwbr800i0: No such file or directory
Oct 28 09:39:35 pvestkc systemd-udevd[23667]: Could not generate persistent MAC address for fwpr800p0: No such file or directory
Oct 28 09:39:35 pvestkc systemd-udevd[23668]: Could not generate persistent MAC address for fwln800i0: No such file or directory
Oct 28 09:39:36 pvestkc kernel: fwbr800i0: port 1(fwln800i0) entered blocking state
Oct 28 09:39:36 pvestkc kernel: fwbr800i0: port 1(fwln800i0) entered blocking state
Oct 28 09:39:36 pvestkc kernel: fwbr800i0: port 1(fwln800i0) entered disabled state
Oct 28 09:39:36 pvestkc kernel: device fwln800i0 entered promiscuous mode
Oct 28 09:39:36 pvestkc kernel: fwbr800i0: port 1(fwln800i0) entered blocking state
Oct 28 09:39:36 pvestkc kernel: fwbr800i0: port 1(fwln800i0) entered forwarding state
Oct 28 09:39:36 pvestkc kernel: vmbr1: port 2(fwpr800p0) entered blocking state
Oct 28 09:39:36 pvestkc kernel: vmbr1: port 2(fwpr800p0) entered disabled state
Oct 28 09:39:36 pvestkc kernel: device fwpr800p0 entered promiscuous mode
Oct 28 09:39:36 pvestkc kernel: vmbr1: port 2(fwpr800p0) entered blocking state
Oct 28 09:39:36 pvestkc kernel: vmbr1: port 2(fwpr800p0) entered forwarding state
Oct 28 09:39:36 pvestkc kernel: fwbr800i0: port 2(tap800i0) entered blocking state
Oct 28 09:39:36 pvestkc kernel: fwbr800i0: port 2(tap800i0) entered disabled state
Oct 28 09:39:36 pvestkc kernel: fwbr800i0: port 2(tap800i0) entered blocking state
Oct 28 09:39:36 pvestkc kernel: fwbr800i0: port 2(tap800i0) entered forwarding state
Oct 28 09:39:37 pvestkc systemd[1]: Started Proxmox VE replication runner.
Oct 28 09:39:38 pvestkc systemd-udevd[23741]: Could not generate persistent MAC address for tap800i1: No such file or directory
Oct 28 09:39:38 pvestkc pvedaemon[23492]: start failed: command '/usr/bin/kvm -id 100 -name remote -chardev 'socket,id=qmp,path=/var/run/qemu-server/100.qmp,server,nowait
Oct 28 09:39:39 pvestkc pvedaemon[1971]: <root@pam> end task UPID:pvestkc:00005BC4:0011046C:635B40C6:qmstart:100:root@pam: start failed: command '/usr/bin/kvm -id 100 -na
Oct 28 09:39:41 pvestkc pvedaemon[23501]: start failed: command '/usr/bin/kvm -id 200 -name Windows-RDP -chardev 'socket,id=qmp,path=/var/run/qemu-server/200.qmp,server,n
Oct 28 09:39:41 pvestkc pvedaemon[1971]: <root@pam> end task UPID:pvestkc:00005BCD:0011050B:635B40C8:qmstart:200:root@pam: start failed: command '/usr/bin/kvm -id 200 -na
Oct 28 09:39:43 pvestkc pvestatd[1836]: status update time (14.220 seconds)
Oct 28 09:39:45 pvestkc kernel: device tap100i0 entered promiscuous mode
Oct 28 09:39:45 pvestkc kernel: vmbr0: port 3(tap100i0) entered blocking state
Oct 28 09:39:45 pvestkc kernel: vmbr0: port 3(tap100i0) entered disabled state
Oct 28 09:39:45 pvestkc kernel: vmbr0: port 3(tap100i0) entered blocking state
Oct 28 09:39:45 pvestkc kernel: vmbr0: port 3(tap100i0) entered forwarding state
Oct 28 09:39:47 pvestkc kernel: device tap200i0 entered promiscuous mode
Oct 28 09:39:47 pvestkc systemd-udevd[23799]: Could not generate persistent MAC address for tap100i1: No such file or directory
Oct 28 09:39:47 pvestkc kernel: vmbr0: port 4(tap200i0) entered blocking state
Oct 28 09:39:47 pvestkc kernel: vmbr0: port 4(tap200i0) entered disabled state
Oct 28 09:39:47 pvestkc kernel: vmbr0: port 4(tap200i0) entered blocking state
Oct 28 09:39:47 pvestkc kernel: vmbr0: port 4(tap200i0) entered forwarding state
Oct 28 09:39:49 pvestkc systemd-udevd[23835]: Could not generate persistent MAC address for tap200i1: No such file or directory
Oct 28 09:39:50 pvestkc kernel: vmbr0: port 2(tap400i0) entered disabled state
Oct 28 09:40:00 pvestkc pvestatd[1836]: status update time (17.150 seconds)
Oct 28 09:40:00 pvestkc systemd[1]: Starting Proxmox VE replication runner...
Oct 28 09:40:11 pvestkc kernel: device tap800i1 entered promiscuous mode
Oct 28 09:40:12 pvestkc systemd-udevd[23913]: Could not generate persistent MAC address for fwbr800i1: No such file or directory
Oct 28 09:40:12 pvestkc systemd-udevd[23933]: Could not generate persistent MAC address for fwpr800p1: No such file or directory
Oct 28 09:40:12 pvestkc systemd-udevd[23934]: Could not generate persistent MAC address for fwln800i1: No such file or directory
Oct 28 09:40:13 pvestkc kernel: fwbr800i1: port 1(fwln800i1) entered blocking state
Oct 28 09:40:13 pvestkc kernel: fwbr800i1: port 1(fwln800i1) entered disabled state
Oct 28 09:40:13 pvestkc kernel: device fwln800i1 entered promiscuous mode
Oct 28 09:40:13 pvestkc kernel: fwbr800i1: port 1(fwln800i1) entered blocking state
Oct 28 09:40:13 pvestkc kernel: fwbr800i1: port 1(fwln800i1) entered forwarding state
Oct 28 09:40:13 pvestkc kernel: vmbr0: port 2(fwpr800p1) entered blocking state
Oct 28 09:40:13 pvestkc kernel: vmbr0: port 2(fwpr800p1) entered disabled state
Oct 28 09:40:13 pvestkc kernel: device fwpr800p1 entered promiscuous mode
Oct 28 09:40:13 pvestkc kernel: vmbr0: port 2(fwpr800p1) entered blocking state
Oct 28 09:40:13 pvestkc kernel: vmbr0: port 2(fwpr800p1) entered forwarding state
Oct 28 09:40:14 pvestkc kernel: fwbr800i1: port 2(tap800i1) entered blocking state
Oct 28 09:40:14 pvestkc kernel: fwbr800i1: port 2(tap800i1) entered disabled state
Oct 28 09:40:14 pvestkc kernel: fwbr800i1: port 2(tap800i1) entered blocking state
Oct 28 09:40:14 pvestkc kernel: fwbr800i1: port 2(tap800i1) entered forwarding state
Oct 28 09:40:15 pvestkc pvestatd[1836]: status update time (14.881 seconds)
Oct 28 09:40:21 pvestkc kernel: device tap100i1 entered promiscuous mode
Oct 28 09:40:21 pvestkc kernel: vmbr1: port 3(tap100i1) entered blocking state
Oct 28 09:40:21 pvestkc kernel: vmbr1: port 3(tap100i1) entered disabled state
Oct 28 09:40:21 pvestkc kernel: vmbr1: port 3(tap100i1) entered blocking state
Oct 28 09:40:21 pvestkc kernel: vmbr1: port 3(tap100i1) entered forwarding state
Oct 28 09:40:23 pvestkc kernel: device tap200i1 entered promiscuous mode

VM configuration
bootdisk: ide0
cores: 4
ide0: local:100/vm-100-disk-0.raw,cache=writeback,size=450G
ide2: none,media=cdrom
memory: 4096
name: remote
net0: e1000=EA:84:76:B8:9A:DE,bridge=vmbr0
net1: e1000=6E:DF:8C:16:8B:CE,bridge=vmbr1
numa: 0
ostype: win7
scsihw: virtio-scsi-pci
smbios1: uuid=f3881bad-f17d-4e74-99b1-c3eb49defe76
sockets: 1
vga: std
 
Interesting.

Please feel free to post here again if the problem appears again or if you find a way to reproduce it.
 
You must log in or register to reply here.
Top Bottom