Thomas Hipp

The current status is that it's not working. For SR-IOV I'm getting: ``` ubuntu@lantea:~$ lxc config device add v1 ib infiniband parent=ibp4s0 nictype=sriov Device ib added to v1 ubuntu@lantea:~$ lxc...

> Have you confirmed that the container functionality is working first, so we have a line in the sand that we know SRIOV and physical passthrough is working for containers?...

> What does `ip l` show? ``` ubuntu@lantea:~$ ip l 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: enp2s0:...

So, the current state is that SR-IOV now works for VMs. However, I'm still getting the following error when doing `nictype=physical`: ``` ubuntu@lantea:~$ lxc config device add v1 ib infiniband...

> @monstermunchkin has the device been unbound from the host before passing in? Yes, both `pci` and `infiniband` device types unbind the device.

> when testing passthrough, did you disable sr-iov? I believe I did as I thought that was causing the issue. I'll check again once lantea is available.

@stgraber I just checked again, and sr-iov is disabled. The error remains the same: ``` qemu-system-x86_64:/var/snap/lxd/common/lxd/logs/v1/qemu.conf:265: vfio 0000:04:00.0: Failed to set up TRIGGER eventfd signaling for interrupt INTX-0: VFIO_DEVICE_SET_IRQS failure:...

> In general, the test for this should be: > > ``` > rmmod mlx4_ib > rmmod mlx4_en > rmmod mlx4_core > modprobe mlx4_core num_vfs=16 probe_vf=16 > ``` @stgraber I...

@stgraber did you mange to get `nictype=physical` working?

> Hello. I was recently fiddling with LXC/LXD on Void Linux and figured I'd take a brief look into the void template for LXC. To say it is impressively un-void...