<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>pci-passthrough on vNinja.net | VMware, VCF &amp; Homelab</title><link>https://vninja.net/tags/pci-passthrough/</link><description>Recent content in pci-passthrough on vNinja.net | VMware, VCF &amp; Homelab</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>&amp;copy; 2010 - 2026 &lt;b&gt;vNinja.net&lt;/b&gt; &lt;br/&gt; &lt;em&gt;There is a thin line between agile and fragile&lt;/em&gt;</copyright><lastBuildDate>Tue, 03 Nov 2026 10:56:57 +0100</lastBuildDate><atom:link href="https://vninja.net/tags/pci-passthrough/index.xml" rel="self" type="application/rss+xml"/><item><title>PCI Resource Mappings for SR-IOV GPU Passthrough on Proxmox VE</title><link>https://vninja.net/2026/11/02/pci-resource-mappings-for-sriov-passthrough-on-proxmox-ve/</link><pubDate>Mon, 02 Nov 2026 14:00:00 +0100</pubDate><guid>https://vninja.net/2026/11/02/pci-resource-mappings-for-sriov-passthrough-on-proxmox-ve/</guid><description>Raw PCI addresses for SR-IOV virtual functions aren't portable across a Proxmox VE cluster. Building a second GPU-passthrough VM exposed that the hard way, and PCI Resource Mappings fix it properly.</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://vninja.net/2026/11/02/pci-resource-mappings-for-sriov-passthrough-on-proxmox-ve/featured.png"/></item></channel></rss>