3 ms·
Yeap, actually I haven't run directly `bhyve` but using the `vm` wrapper as is very convenient. I haven't looked at passrhrough yet, but I do feel that if I ne
by liendolucas 1y ago
Yeap, actually I haven't run directly `bhyve` but using the `vm` wrapper as is very convenient.
I haven't looked at passrhrough yet, but I do feel that if I need to use it I would probably have to fight a bit with it, anyone had a hard experience setting it up?
- BSDobelix 1y agoNo big fight, you just have to exclude the devices at boot so the vm can take them over [1] and if you have a AMD-System add that [2] and use the nvme virtual harddisk [3] [1] https://dflund.se/~getz/Notes/2024/freebsd-gpu/#bhyve-passthrough https://dflund.se/~getz/Notes/2024/freebsd-gpu/#bhyve-passth... [2] https://wiki.freebsd.org/bhyve/pci_passthru#Additional_Notes https://wiki.freebsd.org/bhyve/pci_passthru#Additional_Notes [3] Creating a Windows Server 2019 VM using vm-bhyve : https://klarasystems.com/articles/from-0-to-bhyve-on-freebsd-13-1/ https://klarasystems.com/articles/from-0-to-bhyve-on-freebsd...
- liendolucas 1y agoNice! Thanks for sharing the links.
- nucleardog 1y ago> anyone had a hard experience setting it up? Nothing useful to add, just a "no". I wasn't trying to do GPU passthrough but instead passthrough a PCI card with four independent USB controllers so I could allocate those ports to VMs. Excluded the devices at boot with pptdevs. Using vm for bhyve management so added `passthru0="10/0/0"` (device id) to the vm config. Started it up. Device was in the VM.