20.16.9. Network Interfaces
... <devices> <interface type='bridge'> <source bridge='xenbr0'/> <mac address='00:16:3e:5d:c7:9e'/> <script path='vif-bridge'/> <boot order='1'/> <rom bar='off'/> </interface> </devices> ...
Figure 20.35. Devices - network interfaces
<interface>element has an optional
<address>sub-element that can tie the interface to a particular pci slot, with attribute
type='pci'(Refer to Section 20.16.3, “Device Addresses”).
184.108.40.206. Virtual networks
<network>definition). In addition, it provides a connection whose details are described by the named network definition. Depending on the virtual network's
forward modeconfiguration, the network may be totally isolated (no
<forward>element given), NAT'ing to an explicit network device or to the default route (
forward mode='nat'), routed with no NAT (
forward mode='route'/), or connected directly to one of the host physical machine's network interfaces (using macvtap) or bridge devices (
forward mode=' bridge|private|vepa|passthrough'/)
virsh net-dumpxml [networkname]. There is one virtual network called 'default' setup out of the box which does NAT'ing to the default route and has an IP range of 192.168.122.0/255.255.255.0. Each guest virtual machine will have an associated tun device created with a name of vnetN, which can also be overridden with the
<target>element (refer to Section 220.127.116.11, “Overriding the target element”).
<direct>network connections (described below), a connection of type
networkmay specify a
<virtualport>element, with configuration data to be forwarded to a vepa (802.1Qbg) or 802.1Qbh-compliant switch, or to an Open vSwitch virtual switch.
<network>on the host physical machine, it is acceptable to omit the virtualport type attribute, and specify attributes from multiple different virtualport types (and also to leave out certain attributes); at domain startup time, a complete
<virtualport>element will be constructed by merging together the type and attributes defined in the network and the portgroup referenced by the interface. The newly-constructed virtualport is a combination of both. The attributes from lower virtualport cannot make changes on the ones defined in higher virtualport. Interfaces take the highest priority, portgroup is lowest priority.
interfaceidmust be supplied. The other attributes to be filled in from the virtual port, such as such as
profileid, are optional.
... <devices> <interface type='network'> <source network='default'/> </interface> ... <interface type='network'> <source network='default' portgroup='engineering'/> <target dev='vnet7'/> <mac address="00:11:22:33:44:55"/> <virtualport> <parameters instanceid='09b11c53-8b5c-4eeb-8f00-d84eaa0aaa4f'/> </virtualport> </interface> </devices> ...
Figure 20.36. Devices - network interfaces- virtual networks