Project

General

Profile

Actions

Bug #10315

closed

Cannot add network devices using PCI Passthrough from QEMU hypervisor

Added by Bryon Baker about 4 years ago. Updated about 4 years ago.

Status:
Needs Patch
Priority:
Normal
Assignee:
-
Category:
FreeBSD
Target version:
-
Start date:
03/05/2020
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
Affected Architecture:

Description

When running pfSense as a VM in QEMU you are unable to use PCIe passthrough of network devices.
For example, you cannot pass through a PCIe Wireless card to pfSense to create a Wifi Access point. Nor can you dedicate NICs to pfSense - you have to create a bridge.

This problem is caused by a bug in freeBSD (https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243640)
The fix is to make sure you pick up the latest kernel once freeBSD implement it.

Steps to reproduce
Install pfSense in Proxmox
Configure PCIe passthrough per instructions here: https://pve.proxmox.com/wiki/PCI_Passthrough
Update ID.conf in /etc/pve/qemu-server with:
hostpci0: 03:00,pcie=1,rombar=0
machine: q35
(Note the PCIe device ID will be different. Get that from lspci)

Further documentation on freeBSD issue with Proxmox: https://forum.proxmox.com/threads/vm-w-pcie-passthrough-not-working-after-upgrading-to-6-0.56021/#post-259123

Actions #1

Updated by Bryon Baker about 4 years ago

Update to details above:
Passing through the PCIe-based WiFi is necessary for a proxmox hypervisor because proxmox deliberately does not support wifi NICs due to issues with bridge networks.

Actions #2

Updated by Jim Pingle about 4 years ago

  • Category set to FreeBSD
  • Status changed from New to Needs Patch

There is nothing actionable for us here. It's a problem in FreeBSD that must be addressed upstream.

Actions #3

Updated by Jim Pingle about 4 years ago

We can't keep open duplicate entries for everything in the FreeBSD PR system, even if they might be relevant to certain people.

Note that I set this to "Needs Patch" that while it is a closed state, also indicates that it isn't rejected, but must be solved via outside/upstream action.

Actions

Also available in: Atom PDF