Hey folks,
Owner of a Dell R720 running Proxmox 6.4-13. I have installed an Nvidia Quadro P400 and am looking to get GPU passthrough working on either a Windows 10 VM or a Debian-based Linux VM. I have followed the steps associated with GPU passthrough outlined on the Proxmox website but have, so far, been unsuccessful. I'd appreciate any guidance that might be provided in helping me understand what might be going wrong.
Steps Followed
I'm not sure what to provide but will start with the Proxmox syslog related to the starting of a debian linux VM I created using GPU passthrough. Cheers.
Aug 11 11:50:00 variableman systemd[1]: Starting Proxmox VE replication runner...
Aug 11 11:50:01 variableman systemd[1]: pvesr.service: Succeeded.
Aug 11 11:50:01 variableman systemd[1]: Started Proxmox VE replication runner.
Aug 11 11:50:28 variableman pvedaemon[3418056]: VM 109 qmp command failed - VM 109 not running
Aug 11 11:50:34 variableman pvedaemon[3418056]: <root@pam> starting task UPID:variableman:00373902:06B47D20:61141BFA:qmstart:109:root@pam:
Aug 11 11:50:34 variableman pvedaemon[3619074]: start VM 109: UPID:variableman:00373902:06B47D20:61141BFA:qmstart:109:root@pam:
Aug 11 11:50:34 variableman systemd[1]: Started 109.scope.
Aug 11 11:50:35 variableman systemd-udevd[3619081]: Using default interface naming scheme 'v240'.
Aug 11 11:50:35 variableman systemd-udevd[3619081]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Aug 11 11:50:35 variableman systemd-udevd[3619081]: Could not generate persistent MAC address for tap109i0: No such file or directory
Aug 11 11:50:35 variableman kernel: device tap109i0 entered promiscuous mode
Aug 11 11:50:35 variableman systemd-udevd[3619081]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Aug 11 11:50:35 variableman systemd-udevd[3619081]: Could not generate persistent MAC address for fwbr109i0: No such file or directory
Aug 11 11:50:35 variableman systemd-udevd[3619083]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Aug 11 11:50:35 variableman systemd-udevd[3619083]: Using default interface naming scheme 'v240'.
Aug 11 11:50:35 variableman systemd-udevd[3619083]: Could not generate persistent MAC address for fwpr109p0: No such file or directory
Aug 11 11:50:35 variableman systemd-udevd[3619085]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Aug 11 11:50:35 variableman systemd-udevd[3619085]: Using default interface naming scheme 'v240'.
Aug 11 11:50:35 variableman systemd-udevd[3619085]: Could not generate persistent MAC address for fwln109i0: No such file or directory
Aug 11 11:50:35 variableman kernel: fwbr109i0: port 1(fwln109i0) entered blocking state
Aug 11 11:50:35 variableman kernel: fwbr109i0: port 1(fwln109i0) entered disabled state
Aug 11 11:50:35 variableman kernel: device fwln109i0 entered promiscuous mode
Aug 11 11:50:35 variableman kernel: fwbr109i0: port 1(fwln109i0) entered blocking state
Aug 11 11:50:35 variableman kernel: fwbr109i0: port 1(fwln109i0) entered forwarding state
Aug 11 11:50:35 variableman kernel: vmbr0: port 4(fwpr109p0) entered blocking state
Aug 11 11:50:35 variableman kernel: vmbr0: port 4(fwpr109p0) entered disabled state
Aug 11 11:50:35 variableman kernel: device fwpr109p0 entered promiscuous mode
Aug 11 11:50:35 variableman kernel: vmbr0: port 4(fwpr109p0) entered blocking state
Aug 11 11:50:35 variableman kernel: vmbr0: port 4(fwpr109p0) entered forwarding state
Aug 11 11:50:35 variableman kernel: fwbr109i0: port 2(tap109i0) entered blocking state
Aug 11 11:50:35 variableman kernel: fwbr109i0: port 2(tap109i0) entered disabled state
Aug 11 11:50:35 variableman kernel: fwbr109i0: port 2(tap109i0) entered blocking state
Aug 11 11:50:35 variableman kernel: fwbr109i0: port 2(tap109i0) entered forwarding state
Aug 11 11:50:41 variableman pvedaemon[3605410]: VM 109 qmp command failed - VM 109 qmp command 'query-proxmox-support' failed - unable to connect to VM 109 qmp socket - timeout after 31 retries
Aug 11 11:50:42 variableman pvestatd[1485]: VM 109 qmp command failed - VM 109 qmp command 'query-proxmox-support' failed - unable to connect to VM 109 qmp socket - timeout after 31 retries
Aug 11 11:50:44 variableman pvestatd[1485]: status update time (7.213 seconds)
Aug 11 11:50:52 variableman pvestatd[1485]: VM 109 qmp command failed - VM 109 qmp command 'query-proxmox-support' failed - unable to connect to VM 109 qmp socket - timeout after 31 retries
Aug 11 11:50:53 variableman pvestatd[1485]: status update time (7.228 seconds)
Aug 11 11:51:00 variableman systemd[1]: Starting Proxmox VE replication runner...
Aug 11 11:51:01 variableman pvedaemon[3605410]: VM 109 qmp command failed - VM 109 qmp command 'query-proxmox-support' failed - unable to connect to VM 109 qmp socket - timeout after 31 retries
Aug 11 11:51:01 variableman systemd[1]: pvesr.service: Succeeded.
Aug 11 11:51:01 variableman systemd[1]: Started Proxmox VE replication runner.
Aug 11 11:51:02 variableman pvestatd[1485]: VM 109 qmp command failed - VM 109 qmp command 'query-proxmox-support' failed - unable to connect to VM 109 qmp socket - timeout after 31 retries
Aug 11 11:51:02 variableman kernel: vfio-pci 0000:04:00.0: vfio_ecap_init: hiding ecap 0x19@0x900
Aug 11 11:51:03 variableman pvestatd[1485]: status update time (6.702 seconds)
Aug 11 11:51:04 variableman pvedaemon[3418056]: VM 109 qmp command failed - VM 109 qmp command 'human-monitor-command' failed - unable to connect to VM 109 qmp socket - timeout after 31 retries
Aug 11 11:51:04 variableman pvedaemon[3418056]: <root@pam> end task UPID:variableman:00373902:06B47D20:61141BFA:qmstart:109:root@pam: OK
Aug 11 11:51:13 variableman kernel: usb 1-1.4: reset full-speed USB device number 3 using ehci-pci
Aug 11 11:51:14 variableman kernel: usb 2-1.2: reset low-speed USB device number 3 using ehci-pci
Aug 11 11:51:59 variableman pvedaemon[3418056]: worker exit
Aug 11 11:51:59 variableman pvedaemon[1515]: worker 3418056 finished
Owner of a Dell R720 running Proxmox 6.4-13. I have installed an Nvidia Quadro P400 and am looking to get GPU passthrough working on either a Windows 10 VM or a Debian-based Linux VM. I have followed the steps associated with GPU passthrough outlined on the Proxmox website but have, so far, been unsuccessful. I'd appreciate any guidance that might be provided in helping me understand what might be going wrong.
Steps Followed
I'm not sure what to provide but will start with the Proxmox syslog related to the starting of a debian linux VM I created using GPU passthrough. Cheers.
Aug 11 11:50:00 variableman systemd[1]: Starting Proxmox VE replication runner...
Aug 11 11:50:01 variableman systemd[1]: pvesr.service: Succeeded.
Aug 11 11:50:01 variableman systemd[1]: Started Proxmox VE replication runner.
Aug 11 11:50:28 variableman pvedaemon[3418056]: VM 109 qmp command failed - VM 109 not running
Aug 11 11:50:34 variableman pvedaemon[3418056]: <root@pam> starting task UPID:variableman:00373902:06B47D20:61141BFA:qmstart:109:root@pam:
Aug 11 11:50:34 variableman pvedaemon[3619074]: start VM 109: UPID:variableman:00373902:06B47D20:61141BFA:qmstart:109:root@pam:
Aug 11 11:50:34 variableman systemd[1]: Started 109.scope.
Aug 11 11:50:35 variableman systemd-udevd[3619081]: Using default interface naming scheme 'v240'.
Aug 11 11:50:35 variableman systemd-udevd[3619081]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Aug 11 11:50:35 variableman systemd-udevd[3619081]: Could not generate persistent MAC address for tap109i0: No such file or directory
Aug 11 11:50:35 variableman kernel: device tap109i0 entered promiscuous mode
Aug 11 11:50:35 variableman systemd-udevd[3619081]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Aug 11 11:50:35 variableman systemd-udevd[3619081]: Could not generate persistent MAC address for fwbr109i0: No such file or directory
Aug 11 11:50:35 variableman systemd-udevd[3619083]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Aug 11 11:50:35 variableman systemd-udevd[3619083]: Using default interface naming scheme 'v240'.
Aug 11 11:50:35 variableman systemd-udevd[3619083]: Could not generate persistent MAC address for fwpr109p0: No such file or directory
Aug 11 11:50:35 variableman systemd-udevd[3619085]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Aug 11 11:50:35 variableman systemd-udevd[3619085]: Using default interface naming scheme 'v240'.
Aug 11 11:50:35 variableman systemd-udevd[3619085]: Could not generate persistent MAC address for fwln109i0: No such file or directory
Aug 11 11:50:35 variableman kernel: fwbr109i0: port 1(fwln109i0) entered blocking state
Aug 11 11:50:35 variableman kernel: fwbr109i0: port 1(fwln109i0) entered disabled state
Aug 11 11:50:35 variableman kernel: device fwln109i0 entered promiscuous mode
Aug 11 11:50:35 variableman kernel: fwbr109i0: port 1(fwln109i0) entered blocking state
Aug 11 11:50:35 variableman kernel: fwbr109i0: port 1(fwln109i0) entered forwarding state
Aug 11 11:50:35 variableman kernel: vmbr0: port 4(fwpr109p0) entered blocking state
Aug 11 11:50:35 variableman kernel: vmbr0: port 4(fwpr109p0) entered disabled state
Aug 11 11:50:35 variableman kernel: device fwpr109p0 entered promiscuous mode
Aug 11 11:50:35 variableman kernel: vmbr0: port 4(fwpr109p0) entered blocking state
Aug 11 11:50:35 variableman kernel: vmbr0: port 4(fwpr109p0) entered forwarding state
Aug 11 11:50:35 variableman kernel: fwbr109i0: port 2(tap109i0) entered blocking state
Aug 11 11:50:35 variableman kernel: fwbr109i0: port 2(tap109i0) entered disabled state
Aug 11 11:50:35 variableman kernel: fwbr109i0: port 2(tap109i0) entered blocking state
Aug 11 11:50:35 variableman kernel: fwbr109i0: port 2(tap109i0) entered forwarding state
Aug 11 11:50:41 variableman pvedaemon[3605410]: VM 109 qmp command failed - VM 109 qmp command 'query-proxmox-support' failed - unable to connect to VM 109 qmp socket - timeout after 31 retries
Aug 11 11:50:42 variableman pvestatd[1485]: VM 109 qmp command failed - VM 109 qmp command 'query-proxmox-support' failed - unable to connect to VM 109 qmp socket - timeout after 31 retries
Aug 11 11:50:44 variableman pvestatd[1485]: status update time (7.213 seconds)
Aug 11 11:50:52 variableman pvestatd[1485]: VM 109 qmp command failed - VM 109 qmp command 'query-proxmox-support' failed - unable to connect to VM 109 qmp socket - timeout after 31 retries
Aug 11 11:50:53 variableman pvestatd[1485]: status update time (7.228 seconds)
Aug 11 11:51:00 variableman systemd[1]: Starting Proxmox VE replication runner...
Aug 11 11:51:01 variableman pvedaemon[3605410]: VM 109 qmp command failed - VM 109 qmp command 'query-proxmox-support' failed - unable to connect to VM 109 qmp socket - timeout after 31 retries
Aug 11 11:51:01 variableman systemd[1]: pvesr.service: Succeeded.
Aug 11 11:51:01 variableman systemd[1]: Started Proxmox VE replication runner.
Aug 11 11:51:02 variableman pvestatd[1485]: VM 109 qmp command failed - VM 109 qmp command 'query-proxmox-support' failed - unable to connect to VM 109 qmp socket - timeout after 31 retries
Aug 11 11:51:02 variableman kernel: vfio-pci 0000:04:00.0: vfio_ecap_init: hiding ecap 0x19@0x900
Aug 11 11:51:03 variableman pvestatd[1485]: status update time (6.702 seconds)
Aug 11 11:51:04 variableman pvedaemon[3418056]: VM 109 qmp command failed - VM 109 qmp command 'human-monitor-command' failed - unable to connect to VM 109 qmp socket - timeout after 31 retries
Aug 11 11:51:04 variableman pvedaemon[3418056]: <root@pam> end task UPID:variableman:00373902:06B47D20:61141BFA:qmstart:109:root@pam: OK
Aug 11 11:51:13 variableman kernel: usb 1-1.4: reset full-speed USB device number 3 using ehci-pci
Aug 11 11:51:14 variableman kernel: usb 2-1.2: reset low-speed USB device number 3 using ehci-pci
Aug 11 11:51:59 variableman pvedaemon[3418056]: worker exit
Aug 11 11:51:59 variableman pvedaemon[1515]: worker 3418056 finished
Last edited: