Re: [CentOS-virt] Vlan trunk/QinQ connected to KVM guest
On Thu, Mar 31, 2011 at 1:49 PM, Nataraj wrote: > On 03/28/2011 06:26 AM, AemNet wrote: >> I'm not sure I'm understanding your problem, but generally I create the >> vlan interface inside the guests machine. Notice that we use *ONLY* >> tagged vlan so we can use different vlan in each switch port. >> > Thank You. I got it working now. I'm not sure why it didn't work the > first time I tried. > Please share how you got it working. Regarding VLAN tagging, my understanding is that each interface through which the frames pass must support tagging. Thus if the frame passes through a device that does not support tagging then the tag information is lost. I am also using KVM for my virtual appliances and in one of the appliance scenario, I will have to use 2 VLANs on one the 'guest' VM's NIC. Thanks, -- Arun Khan ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] Vlan trunk/QinQ connected to KVM guest
On 03/28/2011 06:26 AM, AemNet wrote: > I'm not sure I'm understanding your problem, but generally I create the > vlan interface inside the guests machine. Notice that we use *ONLY* > tagged vlan so we can use different vlan in each switch port. > > B. > ___ > CentOS-virt mailing list > CentOS-virt@centos.org > http://lists.centos.org/mailman/listinfo/centos-virt Thank You. I got it working now. I'm not sure why it didn't work the first time I tried. Nataraj ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] Vlan trunk/QinQ connected to KVM guest
I'm not sure I'm understanding your problem, but generally I create the vlan interface inside the guests machine. Notice that we use *ONLY* tagged vlan so we can use different vlan in each switch port. B. ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] Vlan trunk/QinQ connected to KVM guest
On 03/27/2011 04:09 PM, Nataraj wrote: > I am running KVM guests under Redhat 6. I tried to setup a bridge > device to an interface with a vlan trunk connected to a Juniper switch. > On the KVM host, I am able to define vlans and access them via the vlan > trunk. I was not able to access a vlan from the kvm guest connected to > the bridged interface. I believe this would be what is commonly called > QinQ or 802.1ad. Is this possible to do? I am using virtio drivers. > > If I can't do this, I guess I will end up with alot of bridged vlans. I > tried doing this a while back under the vmware server and it did not > work either. I think the reason that it did not work had something to > do with arp resolution.I believe I read some where that it may be > possible under ESXi. > > Thanks, > Nataraj > > ___ > CentOS-virt mailing list > CentOS-virt@centos.org > http://lists.centos.org/mailman/listinfo/centos-virt After thinking about this further I guess it would look like somehow being able to configure a "port" (the one connected to the kvm VM) on the linux bridge as being a vlan trunk. Alternatively, if the guest (also running linux) were able to support QinQ I think I could configure QinQ on the guest as well as on the port on the Juniper switch, though that would only work with 1 guest, so the first solution would be preferred. Nataraj ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
[CentOS-virt] Vlan trunk/QinQ connected to KVM guest
I am running KVM guests under Redhat 6. I tried to setup a bridge device to an interface with a vlan trunk connected to a Juniper switch. On the KVM host, I am able to define vlans and access them via the vlan trunk. I was not able to access a vlan from the kvm guest connected to the bridged interface. I believe this would be what is commonly called QinQ or 802.1ad. Is this possible to do? I am using virtio drivers. If I can't do this, I guess I will end up with alot of bridged vlans. I tried doing this a while back under the vmware server and it did not work either. I think the reason that it did not work had something to do with arp resolution.I believe I read some where that it may be possible under ESXi. Thanks, Nataraj ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
