search for: br600

Hello I have a problem with attaching VMs to a VLAN interface. Here is my setup: I have several physical hosts connected by a physical switch.  Each host has two NICs leading to the switch, which have been combined into a team, team0. Each host a has a bridge br1, which has team0 as a slave. So communication between hosts is based on the IP address of bridge br1 on each host. Up until

...transparent to the guests, right? > > The simplest way to handle this is to create a vlan interface off of > the ethernet that you have attached to br1 (not br1 itself), so it > would be named something like "eth0.600", and then create a new bridge > (call it, say "br600") and attach eth0.600 to br600. Then your guests > would be created with "--network bridge=br600" > > (Note that Linux host bridges do now support vlan tagging (and maybe > even trunking) at the port level, but libvirt hasn't added support for > it. (in other wo...

...and you want that to be transparent to the guests, right? The simplest way to handle this is to create a vlan interface off of the ethernet that you have attached to br1 (not br1 itself), so it would be named something like "eth0.600", and then create a new bridge (call it, say "br600") and attach eth0.600 to br600. Then your guests would be created with "--network bridge=br600" (Note that Linux host bridges do now support vlan tagging (and maybe even trunking) at the port level, but libvirt hasn't added support for it. (in other words, "Patches Welco...

...gt;> >>> The simplest way to handle this is to create a vlan interface off of >>> the ethernet that you have attached to br1 (not br1 itself), so it >>> would be named something like "eth0.600", and then create a new >>> bridge (call it, say "br600") and attach eth0.600 to br600. Then >>> your guests would be created with "--network bridge=br600" >>> >>> (Note that Linux host bridges do now support vlan tagging (and maybe >>> even trunking) at the port level, but libvirt hasn't added su...

...#39;virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> <interface type='bridge'> <mac address='00:16:36:e2:20:eb'/> <source bridge='br600'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </interface> As you can see, there are two interfaces defined in this VM's XML file. One is connected t...

...guests, right? >> >> The simplest way to handle this is to create a vlan interface off of >> the ethernet that you have attached to br1 (not br1 itself), so it >> would be named something like "eth0.600", and then create a new >> bridge (call it, say "br600") and attach eth0.600 to br600. Then your >> guests would be created with "--network bridge=br600" >> >> (Note that Linux host bridges do now support vlan tagging (and maybe >> even trunking) at the port level, but libvirt hasn't added support >>...

Tried that as well, but this has to be something that gets set at the OS level and loaded, as if you look at dmesg output, you can see all the vnet?? nodes as the OS comes online. So the question is, what is virt-install doing that creates the needed vnet interface that is part of the bridge. I really had to kill and reload the VM just to load a second interface.. --- Howard Leadmon

...rtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> <interface type='bridge'> <mac address='00:16:36:e2:20:eb'/> <source bridge='br600'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </interface> As you can see, there are two interfaces defined in this VM's XML file. One is connec...

...<address type='pci' domain='0x0000' bus='0x00' slot='0x03' > function='0x0'/> > </interface> > <interface type='bridge'> > <mac address='00:16:36:e2:20:eb'/> > <source bridge='br600'/> > <model type='virtio'/> > <address type='pci' domain='0x0000' bus='0x00' slot='0x06' > function='0x0'/> > </interface> > > As you can see, there are two interfaces defined in this VM'...