Hacker News new | ask | show | jobs
by mindcrash 36 days ago
> I'll keep a small Proxmox host around for experimenting with new kernel features (Intel GVT-g / SR-IOV graphics) and old operating systems like Windows XP or anything else that needs special QEMU options.

The VM feature of Incus is based on QEMU/KVM so actually there's no need to keep Proxmox around, unless you really want to keep a host or cluster for experimentation with the Proxmox environment. With some configuration you can get SR-IOV and older operating systems working aswell.

1 comments

I would like to see the configuration for SR-IOV. So far my experience has been that IncusOS is very rigid in it's configuration (in a good way!). I expect it's feasible to do with just Incus running on a general purpose Linux distribution like Debian with a recent kernel.
incus config is your friend

There's a entire section about allocating GPUs to containers or VMs here: https://linuxcontainers.org/incus/docs/main/reference/device...

You can do the same with USB devices, NICs, infiniband adapters and whatever (as can be seen below and above the gpu part in the documentation)

For SR-IOV with VFs on a virtual machine the CLI command should look something like:

incus config device add <instance name> <device name> gpu gputype=sriov pci=<pci address>

https://linuxcontainers.org/incus/docs/main/reference/device...

But the possibility to just reroute a entire GPU to a virtual machine or container might be even more interesting:

incus config device add <instance name> <device name> gpu gputype=physical pci=<pci address>

https://linuxcontainers.org/incus/docs/main/reference/device...

Note that there's a possibility you'll need to play with the parameters a bit. All are mentioned in the docs.