GPU PCI Pass Through - Revision history

Wikisailor: /* 3.1. Shut Down Current GPU VM (if switching) */

2026-01-27T15:18:17Z

3.1. Shut Down Current GPU VM (if switching)

← Older revision		Revision as of 15:18, 27 January 2026
Line 93:		Line 93:

	==== 3.1. Shut Down Current GPU VM (if switching) ====		==== 3.1. Shut Down Current GPU VM (if switching) ====
	If the GPU is currently passed through to another VM eg Walnut , shut down that VM gracefully and remove the PCI Device from its hardware configuration in the Proxmox web GUI.		If the GPU is currently passed through to another VM eg '''[[Remote Access Terminal \| Walnut ]]''', shut down that VM gracefully and remove the PCI Device from its hardware configuration in the Proxmox web GUI.

	==== 3.2. Set VM Display to None ====		==== 3.2. Set VM Display to None ====

Wikisailor: /* Updated information */

2026-01-27T15:17:29Z

Updated information

← Older revision		Revision as of 15:17, 27 January 2026
Line 7:		Line 7:
	===Addition of 2.5 Gb p/s NIC ===		===Addition of 2.5 Gb p/s NIC ===

	The addition of a 2.5 Gb p/s NIC and managed switch to the homelab detailed in [[Network Configuration]] caused the GPU to change its PCIe bus information because the NIC grouped the all of the PCIes together and while they were being separated the onboard NIC somehow changed to ID 6 and the GPU changed to ID 7. So when '''[[Remote Access Terminal \| ~~walnut~~ ]]''' booted Proxmox passed the NIC through to Walnut and as walnut was expecting it to be a GPU it failed to boot and as the onboard NIC is used to manage the Proxmox PVE the connection to the WebGUI was lost. The resulting lesson learned is that any changes to PCIe or GPU will have unforeseen effects and to check the configuration carefully.		The addition of a 2.5 Gb p/s NIC and managed switch to the homelab detailed in [[Network Configuration]] caused the GPU to change its PCIe bus information because the NIC grouped the all of the PCIes together and while they were being separated the onboard NIC somehow changed to ID 6 and the GPU changed to ID 7. So when '''[[Remote Access Terminal \| Walnut ]]''' booted Proxmox passed the NIC through to Walnut and as walnut was expecting it to be a GPU it failed to boot and as the onboard NIC is used to manage the Proxmox PVE the connection to the WebGUI was lost. The resulting lesson learned is that any changes to PCIe or GPU will have unforeseen effects and to check the configuration carefully.

	== NVIDIA RTX 5060 PCI Passthrough on Proxmox VE ==		== NVIDIA RTX 5060 PCI Passthrough on Proxmox VE ==

Wikisailor: /* 3. Configure VM for Passthrough (Windows 11 - `walnut` or Ubuntu Desktop - `lychee`) */

2026-01-27T15:17:02Z

3. Configure VM for Passthrough (Windows 11 - `walnut` or Ubuntu Desktop - `lychee`)

← Older revision		Revision as of 15:17, 27 January 2026
Line 93:		Line 93:

	==== 3.1. Shut Down Current GPU VM (if switching) ====		==== 3.1. Shut Down Current GPU VM (if switching) ====
	If the GPU is currently passed through to another VM ~~(e.g., `walnut`)~~, shut down that VM gracefully and remove the PCI Device from its hardware configuration in the Proxmox web GUI.		If the GPU is currently passed through to another VM eg Walnut , shut down that VM gracefully and remove the PCI Device from its hardware configuration in the Proxmox web GUI.

	==== 3.2. Set VM Display to None ====		==== 3.2. Set VM Display to None ====

Wikisailor: /* Addition of 2.5 Gb p/s NIC */

2026-01-27T15:15:16Z

Addition of 2.5 Gb p/s NIC

← Older revision		Revision as of 15:15, 27 January 2026
Line 7:		Line 7:
	===Addition of 2.5 Gb p/s NIC ===		===Addition of 2.5 Gb p/s NIC ===

	The addition of a 2.5 Gb p/s NIC and managed switch to the homelab detailed in [[Network Configuration]] caused the GPU to change its PCIe bus information because the NIC grouped the all of the PCIes together and while they were being separated the onboard NIC somehow changed to ID 6 and the GPU changed to ID 7. So when walnut booted Proxmox passed the NIC through to Walnut and as walnut was expecting it to be a GPU it failed to boot and as the onboard NIC is used to manage the Proxmox PVE the connection to the WebGUI was lost. The resulting lesson learned is that any changes to PCIe or GPU will have unforeseen effects and to check the configuration carefully.		The addition of a 2.5 Gb p/s NIC and managed switch to the homelab detailed in [[Network Configuration]] caused the GPU to change its PCIe bus information because the NIC grouped the all of the PCIes together and while they were being separated the onboard NIC somehow changed to ID 6 and the GPU changed to ID 7. So when '''[[Remote Access Terminal \| walnut ]]''' booted Proxmox passed the NIC through to Walnut and as walnut was expecting it to be a GPU it failed to boot and as the onboard NIC is used to manage the Proxmox PVE the connection to the WebGUI was lost. The resulting lesson learned is that any changes to PCIe or GPU will have unforeseen effects and to check the configuration carefully.

	== NVIDIA RTX 5060 PCI Passthrough on Proxmox VE ==		== NVIDIA RTX 5060 PCI Passthrough on Proxmox VE ==

Wikisailor: /* Addition of 2.5 Gb p/s NIC */

2026-01-27T15:11:05Z

Addition of 2.5 Gb p/s NIC

← Older revision		Revision as of 15:11, 27 January 2026
Line 7:		Line 7:
	===Addition of 2.5 Gb p/s NIC ===		===Addition of 2.5 Gb p/s NIC ===

	The addition of a 2.5 Gb p/s NIC and managed switch to the homelab detailed in [[Network Configuration]] caused the GPU to change its PCIe bus information because the NIC grouped the all of the PCIes together and while they were being separated the onboard NIC somehow changed to ID 6 and the GPU changed to ID 7. So when walnut booted Proxmox passed the NIC through to Walnut and as walnut was expecting it to be a GPU it failed to boot and as the onboard NIC is used to manage the Proxmox PVE the connection to the WebGUI was lost. The resulting lesson learned is that any changes to PCIe or GPU will have unforeseen effects and to check the configuration carefully		The addition of a 2.5 Gb p/s NIC and managed switch to the homelab detailed in [[Network Configuration]] caused the GPU to change its PCIe bus information because the NIC grouped the all of the PCIes together and while they were being separated the onboard NIC somehow changed to ID 6 and the GPU changed to ID 7. So when walnut booted Proxmox passed the NIC through to Walnut and as walnut was expecting it to be a GPU it failed to boot and as the onboard NIC is used to manage the Proxmox PVE the connection to the WebGUI was lost. The resulting lesson learned is that any changes to PCIe or GPU will have unforeseen effects and to check the configuration carefully.

	== NVIDIA RTX 5060 PCI Passthrough on Proxmox VE ==		== NVIDIA RTX 5060 PCI Passthrough on Proxmox VE ==

Wikisailor: /* Updated information */

2026-01-27T15:10:42Z

Updated information

← Older revision		Revision as of 15:10, 27 January 2026
Line 3:		Line 3:

	==Updated information ==		==Updated information ==
			Any changes to the GPU passthough need to be noted here so that We have a complete history of the GPU passthrough

			===Addition of 2.5 Gb p/s NIC ===

			The addition of a 2.5 Gb p/s NIC and managed switch to the homelab detailed in [[Network Configuration]] caused the GPU to change its PCIe bus information because the NIC grouped the all of the PCIes together and while they were being separated the onboard NIC somehow changed to ID 6 and the GPU changed to ID 7. So when walnut booted Proxmox passed the NIC through to Walnut and as walnut was expecting it to be a GPU it failed to boot and as the onboard NIC is used to manage the Proxmox PVE the connection to the WebGUI was lost. The resulting lesson learned is that any changes to PCIe or GPU will have unforeseen effects and to check the configuration carefully

	== NVIDIA RTX 5060 PCI Passthrough on Proxmox VE ==		== NVIDIA RTX 5060 PCI Passthrough on Proxmox VE ==

Wikisailor: /* Introduction */

2026-01-27T14:57:08Z

Introduction

← Older revision		Revision as of 14:57, 27 January 2026
Line 1:		Line 1:
	==Introduction==		==Introduction==
	Wit the the successful GPU PCI Pass Through of the Nvidia GPU Walnut is able to run jellyfish quite well. However, I would prefer to have a Linux host with the GPU mainly because I already have a Windows 11 desktop with a powerful GPU so it will be better to have this the small Nvida on a Linux host. I am getting the AI Gemmini to generate the instructions for the wiki so they may be a bit different to the usual form of my notes		Wit the the successful GPU PCI Pass Through of the Nvidia GPU, Walnut, is able to run jellyfish quite well. However, I would prefer to have a Linux host on the '''[[Home Lab]]''' with the GPU mainly because I already have a Windows 11 desktop with a powerful GPU so it will be better to have this the small Nvida on a Linux host and within a '''[[Home Lab]]''' enviroment. I am getting the AI Gemmini to generate the instructions for the wiki so they may be a bit different to the usual form of my notes

	==Updated information ==		==Updated information ==

Wikisailor: /* Updated information = */

2026-01-27T14:54:29Z

Updated information =

← Older revision		Revision as of 14:54, 27 January 2026
Line 2:		Line 2:
	Wit the the successful GPU PCI Pass Through of the Nvidia GPU Walnut is able to run jellyfish quite well. However, I would prefer to have a Linux host with the GPU mainly because I already have a Windows 11 desktop with a powerful GPU so it will be better to have this the small Nvida on a Linux host. I am getting the AI Gemmini to generate the instructions for the wiki so they may be a bit different to the usual form of my notes		Wit the the successful GPU PCI Pass Through of the Nvidia GPU Walnut is able to run jellyfish quite well. However, I would prefer to have a Linux host with the GPU mainly because I already have a Windows 11 desktop with a powerful GPU so it will be better to have this the small Nvida on a Linux host. I am getting the AI Gemmini to generate the instructions for the wiki so they may be a bit different to the usual form of my notes

	==Updated information ===		==Updated information ==

	== NVIDIA RTX 5060 PCI Passthrough on Proxmox VE ==		== NVIDIA RTX 5060 PCI Passthrough on Proxmox VE ==

Wikisailor: /* Introduction */

2026-01-27T14:54:20Z

Introduction

← Older revision		Revision as of 14:54, 27 January 2026
Line 1:		Line 1:
	==Introduction==		==Introduction==
	Wit the the successful GPU PCI Pass Through of the Nvidia GPU Walnut is able to run jellyfish quite well. However, I would prefer to have a Linux host with the GPU mainly because I already have a Windows 11 desktop with a powerful GPU so it will be better to have this the small Nvida on a Linux host. I am getting the AI Gemmini to generate the instructions for the wiki so they may be a bit different to the usual form of my notes		Wit the the successful GPU PCI Pass Through of the Nvidia GPU Walnut is able to run jellyfish quite well. However, I would prefer to have a Linux host with the GPU mainly because I already have a Windows 11 desktop with a powerful GPU so it will be better to have this the small Nvida on a Linux host. I am getting the AI Gemmini to generate the instructions for the wiki so they may be a bit different to the usual form of my notes

			==Updated information ===

	== NVIDIA RTX 5060 PCI Passthrough on Proxmox VE ==		== NVIDIA RTX 5060 PCI Passthrough on Proxmox VE ==

Wikisailor: /* 1.4. Force VFIO to Bind to the NVIDIA GPU's PCI ID */

2025-05-26T00:58:02Z

1.4. Force VFIO to Bind to the NVIDIA GPU's PCI ID

← Older revision		Revision as of 00:58, 26 May 2025
Line 44:		Line 44:

	# Identify your GPU's PCI ID (Vendor ID:Device ID)		# Identify your GPU's PCI ID (Vendor ID:Device ID)
	~~root@pear:~#~~ lspci -n -s 06:00.0		lspci -n -s 06:00.0
	# Example output: 06:00.0 0300: 10de:2d05 (rev a1)		* Example output: 06:00.0 0300: 10de:2d05 (rev a1)
	# Note: 10de is NVIDIA's Vendor ID, 2d05 is the Device ID for the VGA function.		* Note: 10de is NVIDIA's Vendor ID, 2d05 is the Device ID for the VGA function.
	# Also identify the GPU's Audio Device PCI ID (e.g., 06:00.1 0403: 10de:22eb)		* Also identify the GPU's Audio Device PCI ID (e.g., 06:00.1 0403: 10de:22eb)
			nano /etc/modprobe.d/vfio.conf
	~~root@pear:~#~~ nano /etc/modprobe.d/vfio.conf		(Create this file if it doesn't exist)
	# (Create this file if it doesn't exist)

	Add this line, replacing `10de:2d05` and `10de:22eb` with your GPU's exact Vendor:Device IDs for both the VGA and Audio functions:		Add this line, replacing `10de:2d05` and `10de:22eb` with your GPU's exact Vendor:Device IDs for both the VGA and Audio functions:
			options vfio-pci ids=10de:2d05,10de:22eb
	options vfio-pci ids=10de:2d05,10de:22eb

	Save and exit.		Save and exit.