From: Cole Robinson 192.168.22.0/255.255.255.0. Each guest will have an
associated tun device created with a name of vnetN, which can also be
- overridden with the <target> element.
+ overridden with the <target> element (see
+ overriding the target element).
@@ -514,10 +515,11 @@
there is a bridge device on the host which has one or more of the hosts
physical NICs enslaved. The guest VM will have an associated tun device
created with a name of vnetN, which can also be overridden with the
- <target> element. The tun device will be enslaved to the bridge.
- The IP range / network configuration is whatever is used on the LAN. This
- provides the guest VM full incoming & outgoing net access just like a
- physical machine.
+ <target> element (see
+ overriding the target element).
+ The tun device will be enslaved to the bridge. The IP range / network
+ configuration is whatever is used on the LAN. This provides the guest VM
+ full incoming & outgoing net access just like a physical machine.
@@ -652,6 +654,25 @@ qemu-kvm -net nic,model=? /dev/null
ne2k_isa i82551 i82557b i82559er ne2k_pci pcnet rtl8139 e1000 virtio
+ Overriding the target element
+
+
+ ...
+ <interface type='network'>
+ <source network='default'/>
+ <target dev='vnet1'/>
+ </interface>
+ ...
+
+
+ If no target is specified, certain hypervisors will automatically
+ generate a name for the created tun device. This name can be manually
+ specifed, however the name must not start with either 'vnet' or
+ 'vif', which are prefixes reserved by libvirt and certain
+ hypervisors. Manually specified targets using these prefixes will be
+ ignored.
+
+
Input devices