20 Haziran 2012 Çarşamba 05:22
I have a Hyper-V server 2008 with one physical NIC connected to a trunk switch port. The virtual NIC on the host is configured to use VLAN 1 and indeed it works. I configured a NIC in a VM to VLAN 2 and it also works. The host communicates on VLAN 1 and the guest on VLAN 2. All good.
Now in one particular VM, I want the guest OS to manage the VLANs itself, i.e. I want Hyper-V to forward the trunk inside the VM. I cleared the 'enable virtual LAN identification' for that particular VM, but it doesn't seem to work, no networking inside the guest.
Is this at all possible with Hyper-V? VMware ESXi supports this by assigning the virtual network to a reserved VLAN id 4095.
20 Haziran 2012 Çarşamba 07:36
As far as I am aware that won't work in Hyper-V. Hyper-V is "VLAN aware" so that it handles tagged packets successfully. It is not "VLAN capable" so it cannot do its own tagging.