Hi all,
I have been perusing the forums here, and I see some similar threads related to a VM backup failing when PCIe devices are passed through to multiple VMs, but that doesn't quite match my situation.
https://forum.proxmox.com/threads/b...-vms-fails-when-using-gpu-passthrough.147970/
https://forum.proxmox.com/threads/backup-vm-same-pcie-device-iommu-on-two-vm.129600/
Context and Issues
I have a single WIN10 VM that has a PCIe passthrough device (GPU) and it consistently fails backup operations. I get this message when it does fail:
I do have a VM with a different PCIe device passed through to it, but that doesn't seem to track the other issues folks have reported - here are the two Hardware Configs for the VMs.
This VM is backed up prior to the one that fails:
and the one that fails:
After the VM fails to backup, I cannot seem to startup the VM . This is the status that pops up in the task viewer:
I seem to need to reboot the Proxmox host, as per this thread:
https://forum.proxmox.com/threads/s...ing-state-file-proxmox-8-0-4-win11-vm.137632/
Questions:
Is it possible this is related to the VM backup failing?
I am unfamiliar with the reference to "hugepages" - what is that? How can I configure whatever needs to be configured there?
TIA
-Dan
I have been perusing the forums here, and I see some similar threads related to a VM backup failing when PCIe devices are passed through to multiple VMs, but that doesn't quite match my situation.
https://forum.proxmox.com/threads/b...-vms-fails-when-using-gpu-passthrough.147970/
https://forum.proxmox.com/threads/backup-vm-same-pcie-device-iommu-on-two-vm.129600/
Context and Issues
I have a single WIN10 VM that has a PCIe passthrough device (GPU) and it consistently fails backup operations. I get this message when it does fail:
Code:
NFO: VM Name: E3D-SW-01
INFO: include disk 'virtio0' 'local-nvme-1tb:vm-105-disk-0' 128G
INFO: exclude disk 'virtio1' 'local-hdd-4tb:vm-105-disk-3' (backup=no)
INFO: include disk 'efidisk0' 'local-nvme-1tb:vm-105-disk-1' 1M
INFO: include disk 'tpmstate0' 'local-nvme-1tb:vm-105-disk-2' 4M
INFO: creating Proxmox Backup Server archive 'vm/105/2024-10-18T02:12:39Z'
INFO: starting kvm to execute backup task
swtpm_setup: Not overwriting existing state file.
ERROR: Backup of VM 105 failed - start failed: command '/usr/bin/kvm -id 105 -name 'E3D-SW-01,debug-threads=on' -no-shutdown -chardev 'socket,id=qmp,path=/var/run/qemu-server/105.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/105.pid -daemonize -smbios 'type=1,uuid=0380b211-070f-4a19-85c0-5c6d91e0cdc6' -drive 'if=pflash,unit=0,format=raw,readonly=on,file=/usr/share/pve-edk2-firmware//OVMF_CODE_4M.secboot.fd' -drive 'if=pflash,unit=1,id=drive-efidisk0,format=raw,file=/dev/zvol/local-nvme-1tb/vm-105-disk-1,size=540672' -smp '16,sockets=1,cores=16,maxcpus=16' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-server/bootsplash.jpg' -vnc 'unix:/var/run/qemu-server/105.vnc,password=on' -cpu 'host,hv_ipi,hv_relaxed,hv_reset,hv_runtime,hv_spinlocks=0x1fff,hv_stimer,hv_synic,hv_time,hv_vapic,hv_vpindex,+kvm_pv_eoi,+kvm_pv_unhalt' -m 32768 -object 'iothread,id=iothread-virtio0' -object 'iothread,id=iothread-virtio1' -readconfig /usr/share/qemu-server/pve-q35-4.0.cfg -device 'vmgenid,guid=64e70d1b-b16b-489e-9895-10a13a759fa6' -device 'usb-tablet,id=tablet,bus=ehci.0,port=1' -device 'vfio-pci,host=0000:06:00.0,id=hostpci0.0,bus=ich9-pcie-port-1,addr=0x0.0,multifunction=on' -device 'vfio-pci,host=0000:06:00.1,id=hostpci0.1,bus=ich9-pcie-port-1,addr=0x0.1' -device 'ich9-intel-hda,id=audiodev0,bus=pci.2,addr=0xc' -device 'hda-micro,id=audiodev0-codec0,bus=audiodev0.0,cad=0,audiodev=spice-backend0' -device 'hda-duplex,id=audiodev0-codec1,bus=audiodev0.0,cad=1,audiodev=spice-backend0' -audiodev 'spice,id=spice-backend0' -chardev 'socket,id=tpmchar,path=/var/run/qemu-server/105.swtpm' -tpmdev 'emulator,id=tpmdev,chardev=tpmchar' -device 'tpm-tis,tpmdev=tpmdev' -device 'virtio-vga,id=vga,bus=pcie.0,addr=0x1' -chardev 'socket,path=/var/run/qemu-server/105.qga,server=on,wait=off,id=qga0' -device 'virtio-serial,id=qga0,bus=pci.0,addr=0x8' -device 'virtserialport,chardev=qga0,name=org.qemu.guest_agent.0' -device 'virtio-serial,id=spice,bus=pci.0,addr=0x9' -chardev 'spicevmc,id=vdagent,name=vdagent' -device 'virtserialport,chardev=vdagent,name=com.redhat.spice.0' -spice 'tls-port=61000,addr=127.0.0.1,tls-ciphers=HIGH,seamless-migration=on' -device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3,free-page-reporting=on' -iscsi 'initiator-name=iqn.1993-08.org.debian:01:df5c5d3c96d4' -drive 'if=none,id=drive-ide0,media=cdrom,aio=io_uring' -device 'ide-cd,bus=ide.0,unit=0,drive=drive-ide0,id=ide0,bootindex=102' -drive 'file=/dev/zvol/local-nvme-1tb/vm-105-disk-0,if=none,id=drive-virtio0,format=raw,cache=none,aio=io_uring,detect-zeroes=on' -device 'virtio-blk-pci,drive=drive-virtio0,id=virtio0,bus=pci.0,addr=0xa,iothread=iothread-virtio0,bootindex=100' -drive 'file=/dev/zvol/local-hdd-4tb/vm-105-disk-3,if=none,id=drive-virtio1,cache=writethrough,format=raw,aio=io_uring,detect-zeroes=on' -device 'virtio-blk-pci,drive=drive-virtio1,id=virtio1,bus=pci.0,addr=0xb,iothread=iothread-virtio1' -netdev 'type=tap,id=net0,ifname=tap105i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' -device 'virtio-net-pci,mac=bc:24:11:30:b2:99,netdev=net0,bus=pci.0,addr=0x12,id=net0,rx_queue_size=1024,tx_queue_size=256,bootindex=101' -rtc 'driftfix=slew,base=localtime' -machine 'hpet=off,type=pc-q35-8.0+pve0' -global 'kvm-pit.lost_tick_policy=discard' -S' failed: got timeout
INFO: Failed at 2024-10-17 22:15:52I do have a VM with a different PCIe device passed through to it, but that doesn't seem to track the other issues folks have reported - here are the two Hardware Configs for the VMs.
This VM is backed up prior to the one that fails:
and the one that fails:
After the VM fails to backup, I cannot seem to startup the VM . This is the status that pops up in the task viewer:
Code:
swtpm_setup: Not overwriting existing state file.
TASK ERROR: start failed: command '/usr/bin/kvm -id 105 -name 'E3D-SW-01,debug-threads=on' -no-shutdown -chardev 'socket,id=qmp,path=/var/run/qemu-server/105.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/105.pid -daemonize -smbios 'type=1,uuid=0380b211-070f-4a19-85c0-5c6d91e0cdc6' -drive 'if=pflash,unit=0,format=raw,readonly=on,file=/usr/share/pve-edk2-firmware//OVMF_CODE_4M.secboot.fd' -drive 'if=pflash,unit=1,id=drive-efidisk0,format=raw,file=/dev/zvol/local-nvme-1tb/vm-105-disk-1,size=540672' -smp '16,sockets=1,cores=16,maxcpus=16' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-server/bootsplash.jpg' -vnc 'unix:/var/run/qemu-server/105.vnc,password=on' -cpu 'host,hv_ipi,hv_relaxed,hv_reset,hv_runtime,hv_spinlocks=0x1fff,hv_stimer,hv_synic,hv_time,hv_vapic,hv_vpindex,+kvm_pv_eoi,+kvm_pv_unhalt' -m 32768 -object 'iothread,id=iothread-virtio0' -object 'iothread,id=iothread-virtio1' -readconfig /usr/share/qemu-server/pve-q35-4.0.cfg -device 'vmgenid,guid=64e70d1b-b16b-489e-9895-10a13a759fa6' -device 'usb-tablet,id=tablet,bus=ehci.0,port=1' -device 'vfio-pci,host=0000:06:00.0,id=hostpci0.0,bus=ich9-pcie-port-1,addr=0x0.0,multifunction=on' -device 'vfio-pci,host=0000:06:00.1,id=hostpci0.1,bus=ich9-pcie-port-1,addr=0x0.1' -device 'ich9-intel-hda,id=audiodev0,bus=pci.2,addr=0xc' -device 'hda-micro,id=audiodev0-codec0,bus=audiodev0.0,cad=0,audiodev=spice-backend0' -device 'hda-duplex,id=audiodev0-codec1,bus=audiodev0.0,cad=1,audiodev=spice-backend0' -audiodev 'spice,id=spice-backend0' -chardev 'socket,id=tpmchar,path=/var/run/qemu-server/105.swtpm' -tpmdev 'emulator,id=tpmdev,chardev=tpmchar' -device 'tpm-tis,tpmdev=tpmdev' -device 'virtio-vga,id=vga,bus=pcie.0,addr=0x1' -chardev 'socket,path=/var/run/qemu-server/105.qga,server=on,wait=off,id=qga0' -device 'virtio-serial,id=qga0,bus=pci.0,addr=0x8' -device 'virtserialport,chardev=qga0,name=org.qemu.guest_agent.0' -device 'virtio-serial,id=spice,bus=pci.0,addr=0x9' -chardev 'spicevmc,id=vdagent,name=vdagent' -device 'virtserialport,chardev=vdagent,name=com.redhat.spice.0' -spice 'tls-port=61000,addr=127.0.0.1,tls-ciphers=HIGH,seamless-migration=on' -device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3,free-page-reporting=on' -iscsi 'initiator-name=iqn.1993-08.org.debian:01:df5c5d3c96d4' -drive 'if=none,id=drive-ide0,media=cdrom,aio=io_uring' -device 'ide-cd,bus=ide.0,unit=0,drive=drive-ide0,id=ide0,bootindex=102' -drive 'file=/dev/zvol/local-nvme-1tb/vm-105-disk-0,if=none,id=drive-virtio0,format=raw,cache=none,aio=io_uring,detect-zeroes=on' -device 'virtio-blk-pci,drive=drive-virtio0,id=virtio0,bus=pci.0,addr=0xa,iothread=iothread-virtio0,bootindex=100' -drive 'file=/dev/zvol/local-hdd-4tb/vm-105-disk-3,if=none,id=drive-virtio1,cache=writethrough,format=raw,aio=io_uring,detect-zeroes=on' -device 'virtio-blk-pci,drive=drive-virtio1,id=virtio1,bus=pci.0,addr=0xb,iothread=iothread-virtio1' -netdev 'type=tap,id=net0,ifname=tap105i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' -device 'virtio-net-pci,mac=bc:24:11:30:b2:99,netdev=net0,bus=pci.0,addr=0x12,id=net0,rx_queue_size=1024,tx_queue_size=256,bootindex=101' -rtc 'driftfix=slew,base=localtime' -machine 'hpet=off,type=pc-q35-8.0+pve0' -global 'kvm-pit.lost_tick_policy=discard'' failed: got timeoutI seem to need to reboot the Proxmox host, as per this thread:
https://forum.proxmox.com/threads/s...ing-state-file-proxmox-8-0-4-win11-vm.137632/
Questions:
Is it possible this is related to the VM backup failing?
I am unfamiliar with the reference to "hugepages" - what is that? How can I configure whatever needs to be configured there?
TIA
-Dan
