SR-IOV an configuring transparent VLANs

pos

Member

Reaction score: 10
Messages: 43

Hi

If using a linux host, you can use the NIC:s capabilities of transparent VLANs (it its SR-IOV feature set has it). It means (if the host has a VLAN trunk) that you could set a VLAN tag on the VF that you then hand out to the guest. Then the guest sees this as a non VLAN:ed interface. I have used this a lot with a linux host running KVM.

I would definitely not let the VM guest root user set VLAN tags on the VF. Then the guest VM admin could place the host on any VLAN in the trunk.

How do I config transparent VLAN on the SR-IOV VF:s in FreeBSD?
 
OP
OP
pos

pos

Member

Reaction score: 10
Messages: 43

I will probably revert to Linux/KVM on the hypervisor host as FreeBSD have no way to solve my issues. This is too bad, because the actual VMs is *very* responsive and snappy in bhyve. Better than KVM. Just the networking issues I mention… It seems there is no work around at this time if using FreeBSD. Or is there?

I need one or the other of the following:
* A bridge that has good network performance
When attaching a vlan interface to it and use this for the VMs the network performance is not good. A know problem due to the locks in the bridge code.

or

* Transparent VLANs on the VFs when using SR-IOV
Setting a VLAN tag on the VF that is handed out to the VM (an SR-IOV feature). Then this tag is automatically stripped so the VM does not have to have any knowledge of VLANs. Little like an access port in a switch. This is soemthing you want to do if there is a trunk interface to the hypervisor host. This support seems to be non-existent in the FreeBSD drivers for Chelsio or Intel, but works in both Chelsio and intel drivers on Linux


If anyone can come up with a workaround or point me in a direction to solve this that I have not seen, I will be very glad

/Peo
 
Top