VLAN created inside VM doesn't work

Discussion in 'Networking Questions' started by SteveITS, Mar 11, 2015.

  1. SteveITS

    SteveITS Tera Poster

    Messages:
    251
    I struggled a bit setting up a VLAN on a virtual machine this week and came to the following conclusion:
    • If the hardware node has no VLAN set up, and the VM is configured with a VLAN adapter (inside the VM), the VM can't communicate.
    • If the hardware node does have a VLAN set up, and the VM is also configured for a VLAN, the VM can't communicate.
    • If the hardware node does have a VLAN set up, and the VM is not configured for a VLAN, the VM can communicate successfully over that adapter.
    I am wondering if that is the intent, or a bug? In my specific case I used pfSense 2.2 and its built in functionality to create a VLAN on any of its detected NICs.

    The distinction, it seems to me, is that if the VM has the VLAN set up, the VLAN would move with the VM to another host. Otherwise we would need to create the VLAN and a Virtual Network on all hosts, so that the VM could join its card to the correct Virtual Network and hence the VLAN.
     
  2. KonstantinB

    KonstantinB Odin Team

    Messages:
    68
    Hi Steve,

    Yes, we suggest to create VLANs on all hosts and attach virtual networks with the same name to them to avoid migration problem.
    There is a problem with hardware acceleration of VLAN tag processing by e1000 virtual adapter. Prl_eth and virtio should work.
     
    Last edited: Mar 18, 2015

Share This Page