External/libvirt
1
0
Fork 0
mirror of https://gitlab.com/libvirt/libvirt.git synced 2024-10-05 05:45:46 +00:00
Code Issues Packages Projects Releases Wiki Activity

Document overriding domain interface target

Browse Source 
* docs/formatdomain.html.in: document that vnet and vif are reserved
  names and will be ignored if manually specified.
This commit is contained in:
Cole Robinson 2009-11-20 16:25:58 +01:00 committed by Daniel Veillard
parent c7e1cfc9f4
commit eb81396863
1 changed files with 26 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

31
docs/formatdomain.html.in
View File

@ -484,7 +484,8 @@
of the box which does NAT'ing to the default route and has an IP range of
<code>192.168.22.0/255.255.255.0</code>. Each guest will have an
associated tun device created with a name of vnetN, which can also be
overridden with the &lt;target&gt; element.
overridden with the &lt;target&gt; element (see
<a href="#elementsNICSTargetOverride">overriding the target element</a>).
</p>
<pre>
@ -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
&lt;target&gt; 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 &amp; outgoing net access just like a
physical machine.
&lt;target&gt; element (see
<a href="#elementsNICSTargetOverride">overriding the target element</a>).
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 &amp; outgoing net access just like a physical machine.
</p>
<pre>
@ -652,6 +654,25 @@ qemu-kvm -net nic,model=? /dev/null
ne2k_isa i82551 i82557b i82559er ne2k_pci pcnet rtl8139 e1000 virtio
</p>
<h5><a name="elementsNICSTargetOverride">Overriding the target element</a></h5>
<pre>
...
&lt;interface type='network'&gt;
&lt;source network='default'/&gt;
<b>&lt;target dev='vnet1'/&gt;</b>
&lt;/interface&gt;
...</pre>
<p>
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 <i>must not start with either 'vnet' or
'vif'</i>, which are prefixes reserved by libvirt and certain
hypervisors. Manually specified targets using these prefixes will be
ignored.
</p>
<h4><a name="elementsInput">Input devices</a></h4>
<p>