How do I set up trunk ports (802.3q) on VMs?

[vitaprimo]

I'm attempting to set up a network appliance-type of VM. I need the equivalent for a [distributed] port group on pseudo-VLAN 4095.

 

I hadn't used Unraid in a minute, but I remember once — while reading some Unraid article —  I learned about macvtap, which is essentially sort of "a macvlan" but at the port/interface level but bypassing the networking stack since it's already handled or som' like that; it's kind of like cloning/aliasing an interface, MAC-spoofing it, while the physical pays the bills or moves the packets in this case; interface impersonation. Whatever it is, it seems like it may be able to support tagged traffic of its own whereas macvlan needs to target directly a subinterface to handle its otherwise tagged traffic. (Correct me where needed, please.)

 

The article where I read this not about it, but about a workaround for a bug. Add just enough time to that and now I don't remember how to find it anymore. I remember that it was enabled by disabling bridging, specifically so because it was counterintuitive. I did that and it seems to have worked. If I'm not misreading the logs (attached below). Although I'm still lost about setting the interface to allow guests to set up their own access to VLANs. Is it possible? I still have two options left, I think; SR-IOV network virtual functions and PCIe passthrough. I've never set up SR-IOV VF networking on Unraid before though and the volume of traffic isn't high enough to warrant a VF, let alone a full NIC. It'd be wasteful.

 

Log:

…
Aug 25 16:01:56 zx4 root: Starting virtlockd...               # ↙︎ No longer references virtual construct 
Aug 25 16:01:56 zx4 kernel: eth0: renamed from vethbc9e72e    # ← but rather an interface directly
Aug 25 16:01:56 zx4 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vetha63b935: link becomes ready
Aug 25 16:01:56 zx4 kernel: docker0: port 1(vetha63b935) entered blocking state
Aug 25 16:01:56 zx4 kernel: docker0: port 1(vetha63b935) entered forwarding state
Aug 25 16:01:56 zx4 root: Starting virtlogd...
Aug 25 16:01:56 zx4 rc.libvirt: change br0.9 to macvtap in /etc/libvirt/qemu/machine-spec1.xml # ← macvtap
Aug 25 16:01:56 zx4 rc.docker: container01: started succesfully!
Aug 25 16:01:56 zx4 rc.libvirt: change br0.9 to macvtap in /etc/libvirt/qemu/machine-spec2.xml # ←
Aug 25 16:01:56 zx4 rc.libvirt: change br0 to macvtap in /etc/libvirt/qemu/machine-spec3.xml   # ←
Aug 25 16:01:56 zx4 root: Starting libvirtd...
Aug 25 16:01:56 zx4 kernel: ccp 0000:09:00.2: psp enabled
Aug 25 16:01:56 zx4 kernel: SVM: TSC scaling supported
Aug 25 16:01:56 zx4 kernel: kvm: Nested Virtualization enabled
Aug 25 16:01:56 zx4 kernel: SVM: kvm: Nested Paging enabled
Aug 25 16:01:56 zx4 kernel: SEV enabled (ASIDs 0 - 15)
Aug 25 16:01:56 zx4 kernel: SEV-ES enabled (ASIDs 0 - 4294967295)
Aug 25 16:01:56 zx4 kernel: SVM: Virtual VMLOAD VMSAVE supported
Aug 25 16:01:56 zx4 kernel: SVM: Virtual GIF supported
Aug 25 16:01:56 zx4 kernel: SVM: LBR virtualization supported
Aug 25 16:01:56 zx4 kernel: tun: Universal TUN/TAP device driver, 1.6
Aug 25 16:01:56 zx4 dnsmasq[2263]: started, version 2.89 cachesize 150
Aug 25 16:01:56 zx4 dnsmasq[2263]: compile time options: IPv6 GNU-getopt DBus no-UBus i18n IDN2 DHCP DHCPv6 no-Lua TFTP conntrack ipset no-nftset auth cryptohash DNSSEC loop-detect inotify dumpfile
Aug 25 16:01:56 zx4 dnsmasq-dhcp[2263]: DHCP, IP range 192.168.122.2 -- 192.168.122.254, lease time 1h
Aug 25 16:01:56 zx4 dnsmasq-dhcp[2263]: DHCP, sockets bound exclusively to interface virbr0
…

and, consistent to some light research on the Internet, the interfaces change their names too:

 

If I choose the parent interface, "vhost0", is that VLAN-agnostic pass through like VLAN4095? Or is it like VLAN0; the untagged VLAN and nothing else?

 

All advice (and education) is welcome.

 

Thanks.