XenServer - how to forward a network interface in trunk mode so that a vlan can be removed from a VM?

Question

Network administration

I installed kerio 8.2.2 as a VM, since it does not have virtualization drivers, you can throw no more than 6 virtual interfaces, but I need more than a dozen. The solution to my problem would be the ability to start a vlan inside the VM itself, but xenserver does not let the port inside in the form of a trunk. Since the vlan ports inside the VM do not work.

Answer 1

Understanding this issue, I came across the official documentation, in which everything is described. Of course, the interface mode should be Trunk, up to the heap and the "carrier" vlan should be 1st. If you use this vlan on the hypervisor host, then by forwarding such a vlan to the VM you will not receive data from it, which was the case with me. Well, accordingly, vlan inside the VM didn’t work for me, in principle, due to the fact that my main one was vlan12.
Here is an excerpt from the documentation:
To configure the switch on a VLAN network, you must configure it as follows:
*Port connected to XenServer on the switch must be configured as trunk port.
*Port on the switch must be configured for 802.1q encapsulation.
*Port security cannot be set on the trunk port.
*Port designated as trunk should be assigned a native VLAN; use 1 as default.
Note: If a Native VLAN is used on the switch trunk port, then you cannot assign that VLAN number to a Virtual Machine on the XenServer. Refer to the following example for a working tested model.