Hello Folks,
I'm having a strange issue. I recently ran some updates on my proxmox node, and restarted one of my WIN10 virtual machines and noticed it wouldn't boot:
TASK ERROR: start failed: command '/usr/bin/kvm -id 101 -name WEB-WIN10 -chardev 'socket,id=qmp,path=/var/run/qemu-server/101.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/101.pid -daemonize -smbios 'type=1,uuid=f990685e-f18f-42d1-8a1f-60edda60ffb1' -smp '4,sockets=2,cores=2,maxcpus=4' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-server/bootsplash.jpg' -vnc unix:/var/run/qemu-server/101.vnc,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,hv_ipi,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 'vmgenid,guid=123197dd-09d6-4ec7-b08e-7d1901bd64a0' -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' -chardev 'socket,path=/var/run/qemu-server/101.qga,server,nowait,id=qga0' -device 'virtio-serial,id=qga0,bus=pci.0,addr=0x8' -device 'virtserialport,chardev=qga0,name=org.qemu.guest_agent.0' -device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3' -iscsi 'initiator-name=iqn.1993-08.org.debian:01:c65773a457f' -drive 'file=/dev/zvol/vm_store1/vm-101-disk-0,if=none,id=drive-ide0,format=raw,cache=none,aio=native,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=tap101i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown' -device 'e1000,mac=DE:C4:16:97:38:C2,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300' -rtc 'driftfix=slew,base=localtime' -machine 'type=pc+pve1' -global 'kvm-pit.lost_tick_policy=discard'' failed: got timeout
I assumed the issue was with the VM, so I tried rolling to a backup of the VM and a snapshot, but no go.
I tried spinning a new machine and I noticed all windows 7/10 and server versions were getting the same error.
I went back to my original VM , went to options, selected "OS Type" and changed it to "Other". It worked. Same with all the new VMs.
Anyone know why changing OS type would do this? Is this expected behavior?
Here is a config print:
qm config 101
agent: 1
bootdisk: ide0
cores: 4
ide0: vm_store1:vm-101-disk-0,size=32G
ide2: local:iso/virtio-win-0.1.171.iso,media=cdrom,size=363020K
memory: 4096
name: WEB-WIN10
net0: virtio=DE:C4:16:97:38:C2,bridge=vmbr0,firewall=1
numa: 0
ostype: other
scsihw: virtio-scsi-pci
smbios1: uuid=f990685e-f18f-42d1-8a1f-60edda60ffb1
sockets: 1
unused0: local-zfs:vm-101-disk-0
vmgenid: 123197dd-09d6-4ec7-b08e-7d1901bd64a0
It's not a huge deal to me, it's just got me stumped. Having my Windows 10 VM set to "Other" as a solution is fine.. I guess I'm not understanding what's changing in the background when you change the OS Type.
This is all I can find regarding this field in documentation:
"OS Settings
When creating a virtual machine (VM), setting the proper Operating System(OS) allows Proxmox VE to optimize some low level parameters. For instance Windows OS expect the BIOS clock to use the local time, while Unix based OS expect the BIOS clock to have the UTC time. "
As seen here:
https://pve.proxmox.com/wiki/Qemu/KVM_Virtual_Machines
Anyway, I'm fairly new to proxmox and absolutely love it!
I'm having a strange issue. I recently ran some updates on my proxmox node, and restarted one of my WIN10 virtual machines and noticed it wouldn't boot:
TASK ERROR: start failed: command '/usr/bin/kvm -id 101 -name WEB-WIN10 -chardev 'socket,id=qmp,path=/var/run/qemu-server/101.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/101.pid -daemonize -smbios 'type=1,uuid=f990685e-f18f-42d1-8a1f-60edda60ffb1' -smp '4,sockets=2,cores=2,maxcpus=4' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-server/bootsplash.jpg' -vnc unix:/var/run/qemu-server/101.vnc,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,hv_ipi,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 'vmgenid,guid=123197dd-09d6-4ec7-b08e-7d1901bd64a0' -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' -chardev 'socket,path=/var/run/qemu-server/101.qga,server,nowait,id=qga0' -device 'virtio-serial,id=qga0,bus=pci.0,addr=0x8' -device 'virtserialport,chardev=qga0,name=org.qemu.guest_agent.0' -device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3' -iscsi 'initiator-name=iqn.1993-08.org.debian:01:c65773a457f' -drive 'file=/dev/zvol/vm_store1/vm-101-disk-0,if=none,id=drive-ide0,format=raw,cache=none,aio=native,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=tap101i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown' -device 'e1000,mac=DE:C4:16:97:38:C2,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300' -rtc 'driftfix=slew,base=localtime' -machine 'type=pc+pve1' -global 'kvm-pit.lost_tick_policy=discard'' failed: got timeout
I assumed the issue was with the VM, so I tried rolling to a backup of the VM and a snapshot, but no go.
I tried spinning a new machine and I noticed all windows 7/10 and server versions were getting the same error.
I went back to my original VM , went to options, selected "OS Type" and changed it to "Other". It worked. Same with all the new VMs.
Anyone know why changing OS type would do this? Is this expected behavior?
Here is a config print:
qm config 101
agent: 1
bootdisk: ide0
cores: 4
ide0: vm_store1:vm-101-disk-0,size=32G
ide2: local:iso/virtio-win-0.1.171.iso,media=cdrom,size=363020K
memory: 4096
name: WEB-WIN10
net0: virtio=DE:C4:16:97:38:C2,bridge=vmbr0,firewall=1
numa: 0
ostype: other
scsihw: virtio-scsi-pci
smbios1: uuid=f990685e-f18f-42d1-8a1f-60edda60ffb1
sockets: 1
unused0: local-zfs:vm-101-disk-0
vmgenid: 123197dd-09d6-4ec7-b08e-7d1901bd64a0
It's not a huge deal to me, it's just got me stumped. Having my Windows 10 VM set to "Other" as a solution is fine.. I guess I'm not understanding what's changing in the background when you change the OS Type.
This is all I can find regarding this field in documentation:
"OS Settings
When creating a virtual machine (VM), setting the proper Operating System(OS) allows Proxmox VE to optimize some low level parameters. For instance Windows OS expect the BIOS clock to use the local time, while Unix based OS expect the BIOS clock to have the UTC time. "
As seen here:
https://pve.proxmox.com/wiki/Qemu/KVM_Virtual_Machines
Anyway, I'm fairly new to proxmox and absolutely love it!
Last edited:
