Hi, I don't really understant:
1) create VLAN on the host --- I suppose the vlan is configured on the switch. Do you mean the host-wide vlan? 2) link VLAN to an interface on the host And what's the difference between your solution (802.1q) and openvswitch's? Gnep On Sun, Dec 19, 2010 at 6:31 AM, Rangababu Chakravarthula < rb...@hexagrid.com> wrote: > John > Yes you can use 802.1q VLAN tagging to your VM interface. > > The following steps will help you do that. > 1) create VLAN on the host > 2) link VLAN to an interface on the host > 3) create a bridge on the host > 4) associate interface to the bridge > 5) Define the following in VM template > > NIC=[ > BRIDGE=<bridge name given above>, > MAC=00:e5:8d:9f:c1:ba > ] > > Hope this helps. > Ranga > > On Fri, Dec 17, 2010 at 7:45 PM, John Dewey <j...@dewey.ws> wrote: > >> I was curious if anyone has used 802.1q tagging with their VMs. It looks >> as though libvirt supports vlan tagging, >> but OpenNebula at this time does not generate an appropriate deployment >> stanza. >> >> I was hoping I could use network contextualization as a way to configure >> the guest's 802.1q tags. >> I guess I don't understand vlan tagging when "dom0" bridging is in the >> mix. >> >> Does anyone have anymore information on this topic, I would love to talk >> with you a bit more offline. >> >> Thanks - >> John >> >> _______________________________________________ >> Users mailing list >> Users@lists.opennebula.org >> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org >> >> > > _______________________________________________ > Users mailing list > Users@lists.opennebula.org > http://lists.opennebula.org/listinfo.cgi/users-opennebula.org > > -- ================================================= *Often wrong, Never in doubt* =================================================
_______________________________________________ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org