KVM Network Design possibilities

Linux bridge support

Perform the following tasks to add and remove TAP network devices to and from the bridges when you start and stop a guest operating system:

1. Create the bridges before you start the first guest operating system.
2. If you want the guest operating system to access the physical network, add an Ethernet device to the bridge.
3. Specify a script for configuring the tap network device and a script for unconfiguring the tap network device.

Guest operating systems that you add to the same bridge can communicate with each other. If you want multiple subnets available to the guest operating systems, define multiple bridges. In this situation, each bridge is for a unique subnet. Each bridge contains the TAP devices that are associated with the NICs of the guest operating systems that are part of the same subnet.

Note: When working with KVM bridged interfaces, KVM will automatically name the virtual NIC that is spawned when the VM is started. This typically follows a naming convention of:

vnet0, vnet1, vnet2, ..., vnetN


VEPA