NuKVM/libvirt
3
0
Fork 0
mirror of https://github.com/libvirt/libvirt.git synced 2025-02-25 18:55:26 -06:00
Code Issues Packages Projects Releases Wiki Activity

docs: switch to using 'id' attribute instead of 'name' for links

Browse Source 
The 'name' attribute on <a...> elements is deprecated in favour
of the 'id' attribute which is allowed on any element. HTML5
drops 'name' support entirely.

Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
This commit is contained in:
Daniel P. Berrange
2017-07-26 15:52:42 +01:00
parent ba54acd3c7
commit 4e42ff6b7e
62 changed files with 624 additions and 626 deletions
Download Patch File Download Diff File Expand all files Collapse all files

192
docs/formatdomain.html.in
View File

@@ -14,7 +14,7 @@
</p>
<h2><a name="elements">Element and attribute overview</a></h2>
<h2><a id="elements">Element and attribute overview</a></h2>
<p>
The root element required for all virtual machines is
@@ -28,7 +28,7 @@
</p>
<h3><a name="elementsMetadata">General metadata</a></h3>
<h3><a id="elementsMetadata">General metadata</a></h3>
<pre>
&lt;domain type='xen' id='3'&gt;
@@ -82,14 +82,14 @@
element). <span class="since">Since 0.9.10</span></dd>
</dl>
<h3><a name="elementsOS">Operating system booting</a></h3>
<h3><a id="elementsOS">Operating system booting</a></h3>
<p>
There are a number of different ways to boot virtual machines
each with their own pros and cons.
</p>
<h4><a name="elementsOSBIOS">BIOS bootloader</a></h4>
<h4><a id="elementsOSBIOS">BIOS bootloader</a></h4>
<p>
Booting via the BIOS is available for hypervisors supporting
@@ -229,7 +229,7 @@
</dd>
</dl>
<h4><a name="elementsOSBootloader">Host bootloader</a></h4>
<h4><a id="elementsOSBootloader">Host bootloader</a></h4>
<p>
Hypervisors employing paravirtualization do not usually emulate
@@ -262,7 +262,7 @@
</dl>
<h4><a name="elementsOSKernel">Direct kernel boot</a></h4>
<h4><a id="elementsOSKernel">Direct kernel boot</a></h4>
<p>
When installing a new guest OS it is often useful to boot directly
@@ -315,7 +315,7 @@
<span class="since">Since 1.3.5 (QEMU only)</span></dd>
</dl>
<h4><a name="elementsOSContainer">Container boot</a></h4>
<h4><a id="elementsOSContainer">Container boot</a></h4>
<p>
When booting a domain using container based virtualization, instead
@@ -379,7 +379,7 @@
</pre>
<h3><a name="elementsSysinfo">SMBIOS System Information</a></h3>
<h3><a id="elementsSysinfo">SMBIOS System Information</a></h3>
<p>
Some hypervisors allow control over what system information is
@@ -502,7 +502,7 @@
</dd>
</dl>
<h3><a name="elementsCPUAllocation">CPU Allocation</a></h3>
<h3><a id="elementsCPUAllocation">CPU Allocation</a></h3>
<pre>
&lt;domain&gt;
@@ -610,7 +610,7 @@
</dd>
</dl>
<h3><a name="elementsIOThreadsAllocation">IOThreads Allocation</a></h3>
<h3><a id="elementsIOThreadsAllocation">IOThreads Allocation</a></h3>
<p>
IOThreads are dedicated event loop threads for supported disk
devices to perform block I/O requests in order to improve
@@ -667,7 +667,7 @@
</dd>
</dl>
<h3><a name="elementsCPUTuning">CPU Tuning</a></h3>
<h3><a id="elementsCPUTuning">CPU Tuning</a></h3>
<pre>
&lt;domain&gt;
@@ -837,7 +837,7 @@
</dl>
<h3><a name="elementsMemoryAllocation">Memory Allocation</a></h3>
<h3><a id="elementsMemoryAllocation">Memory Allocation</a></h3>
<pre>
&lt;domain&gt;
@@ -910,7 +910,7 @@
</dl>
<h3><a name="elementsMemoryBacking">Memory Backing</a></h3>
<h3><a id="elementsMemoryBacking">Memory Backing</a></h3>
<pre>
&lt;domain&gt;
@@ -980,7 +980,7 @@
</dl>
<h3><a name="elementsMemoryTuning">Memory Tuning</a></h3>
<h3><a id="elementsMemoryTuning">Memory Tuning</a></h3>
<pre>
&lt;domain&gt;
@@ -1044,7 +1044,7 @@
</dl>
<h3><a name="elementsNUMATuning">NUMA Node Tuning</a></h3>
<h3><a id="elementsNUMATuning">NUMA Node Tuning</a></h3>
<pre>
&lt;domain&gt;
@@ -1105,7 +1105,7 @@
</dl>
<h3><a name="elementsBlockTuning">Block I/O Tuning</a></h3>
<h3><a id="elementsBlockTuning">Block I/O Tuning</a></h3>
<pre>
&lt;domain&gt;
...
@@ -1174,7 +1174,7 @@
</dl></dd></dl>
<h3><a name="resPartition">Resource partitioning</a></h3>
<h3><a id="resPartition">Resource partitioning</a></h3>
<p>
Hypervisors may allow for virtual machines to be placed into
@@ -1203,7 +1203,7 @@
in all mounted controllers. <span class="since">Since 1.0.5</span>
</p>
<h3><a name="elementsCPU">CPU model and topology</a></h3>
<h3><a id="elementsCPU">CPU model and topology</a></h3>
<p>
Requirements for CPU model, its features and topology can be specified
@@ -1532,7 +1532,7 @@
This guest NUMA specification is currently available only for QEMU/KVM.
</p>
<h3><a name="elementsEvents">Events configuration</a></h3>
<h3><a id="elementsEvents">Events configuration</a></h3>
<p>
It is sometimes necessary to override the default actions taken
@@ -1643,7 +1643,7 @@
<dd>Keep the domain running as if nothing happened.</dd>
</dl>
<h3><a name="elementsPowerManagement">Power Management</a></h3>
<h3><a id="elementsPowerManagement">Power Management</a></h3>
<p>
<span class="since">Since 0.10.2</span> it is possible to
@@ -1667,7 +1667,7 @@
left with its default value.</dd>
</dl>
<h3><a name="elementsFeatures">Hypervisor features</a></h3>
<h3><a id="elementsFeatures">Hypervisor features</a></h3>
<p>
Hypervisors may allow certain CPU / machine features to be
@@ -1869,7 +1869,7 @@
</dd>
</dl>
<h3><a name="elementsTime">Time keeping</a></h3>
<h3><a id="elementsTime">Time keeping</a></h3>
<p>
The guest clock is typically initialized from the host clock.
@@ -2037,7 +2037,7 @@
</dd>
</dl>
<h3><a name="elementsPerf">Performance monitoring events</a></h3>
<h3><a id="elementsPerf">Performance monitoring events</a></h3>
<p>
Some platforms allow monitoring of performance of the virtual machine and
@@ -2218,7 +2218,7 @@
</tr>
</table>
<h3><a name="elementsDevices">Devices</a></h3>
<h3><a id="elementsDevices">Devices</a></h3>
<p>
The final set of XML elements are all used to describe devices
@@ -2245,7 +2245,7 @@
</dd>
</dl>
<h4><a name="elementsDisks">Hard drives, floppy disks, CDROMs</a></h4>
<h4><a id="elementsDisks">Hard drives, floppy disks, CDROMs</a></h4>
<p>
Any device that looks like a disk, be it a floppy, harddisk,
@@ -3185,7 +3185,7 @@
</dd>
</dl>
<h4><a name="elementsFilesystems">Filesystems</a></h4>
<h4><a id="elementsFilesystems">Filesystems</a></h4>
<p>
A directory on the host that can be accessed directly from the guest.
@@ -3368,7 +3368,7 @@
</dd>
</dl>
<h4><a name="elementsAddress">Device Addresses</a></h4>
<h4><a id="elementsAddress">Device Addresses</a></h4>
<p>
Many devices have an optional <code>&lt;address&gt;</code>
@@ -3485,7 +3485,7 @@
</dd>
</dl>
<h4><a name="elementsVirtio">Virtio-related options</a></h4>
<h4><a id="elementsVirtio">Virtio-related options</a></h4>
<p>
QEMU's virtio devices have some attributes related to the virtio transport under
@@ -3498,7 +3498,7 @@
<span class="since">Since 3.5.0</span>
</p>
<h4><a name="elementsControllers">Controllers</a></h4>
<h4><a id="elementsControllers">Controllers</a></h4>
<p>
Depending on the guest architecture, some device buses can
@@ -3884,7 +3884,7 @@
&lt;/devices&gt;
...</pre>
<h4><a name="elementsLease">Device leases</a></h4>
<h4><a id="elementsLease">Device leases</a></h4>
<p>
When using a lock manager, it may be desirable to record device leases
@@ -3924,9 +3924,9 @@
</dd>
</dl>
<h4><a name="elementsHostDev">Host device assignment</a></h4>
<h4><a id="elementsHostDev">Host device assignment</a></h4>
<h5><a name="elementsHostDevSubsys">USB / PCI / SCSI devices</a></h5>
<h5><a id="elementsHostDevSubsys">USB / PCI / SCSI devices</a></h5>
<p>
USB, PCI and SCSI devices attached to the host can be passed through
@@ -4237,7 +4237,7 @@
</dl>
<h5><a name="elementsHostDevCaps">Block / character devices</a></h5>
<h5><a id="elementsHostDevCaps">Block / character devices</a></h5>
<p>
Block / character devices from the host can be passed through
@@ -4294,7 +4294,7 @@
</dd>
</dl>
<h4><a name="elementsRedir">Redirected devices</a></h4>
<h4><a id="elementsRedir">Redirected devices</a></h4>
<p>
USB device redirection through a character device is
@@ -4361,7 +4361,7 @@
</dd>
</dl>
<h4><a name="elementsSmartcard">Smartcard devices</a></h4>
<h4><a id="elementsSmartcard">Smartcard devices</a></h4>
<p>
A virtual smartcard device can be supplied to the guest via the
@@ -4454,7 +4454,7 @@
smartcard, with an address of bus=0 slot=0.
</p>
<h4><a name="elementsNICS">Network interfaces</a></h4>
<h4><a id="elementsNICS">Network interfaces</a></h4>
<pre>
...
@@ -4494,7 +4494,7 @@
as <a href="#elementsAddress">documented above</a>.
</p>
<h5><a name="elementsNICSVirtual">Virtual network</a></h5>
<h5><a id="elementsNICSVirtual">Virtual network</a></h5>
<p>
<strong><em>
@@ -4600,7 +4600,7 @@
&lt;/devices&gt;
...</pre>
<h5><a name="elementsNICSBridge">Bridge to LAN</a></h5>
<h5><a id="elementsNICSBridge">Bridge to LAN</a></h5>
<p>
<strong><em>
@@ -4691,7 +4691,7 @@
&lt;/devices&gt;
...</pre>
<h5><a name="elementsNICSSlirp">Userspace SLIRP stack</a></h5>
<h5><a id="elementsNICSSlirp">Userspace SLIRP stack</a></h5>
<p>
Provides a virtual LAN with NAT to the outside world. The virtual
@@ -4714,7 +4714,7 @@
...</pre>
<h5><a name="elementsNICSEthernet">Generic ethernet connection</a></h5>
<h5><a id="elementsNICSEthernet">Generic ethernet connection</a></h5>
<p>
Provides a means for the administrator to execute an arbitrary script
@@ -4738,7 +4738,7 @@
&lt;/devices&gt;
...</pre>
<h5><a name="elementsNICSDirect">Direct attachment to physical interface</a></h5>
<h5><a id="elementsNICSDirect">Direct attachment to physical interface</a></h5>
<p>
Provides direct attachment of the virtual machine's NIC to the given
@@ -4883,7 +4883,7 @@
</pre>
<h5><a name="elementsNICSHostdev">PCI Passthrough</a></h5>
<h5><a id="elementsNICSHostdev">PCI Passthrough</a></h5>
<p>
A PCI network device (specified by the &lt;source&gt; element)
@@ -4956,7 +4956,7 @@
...</pre>
<h5><a name="elementsNICSMulticast">Multicast tunnel</a></h5>
<h5><a id="elementsNICSMulticast">Multicast tunnel</a></h5>
<p>
A multicast group is setup to represent a virtual network. Any VMs
@@ -4980,7 +4980,7 @@
&lt;/devices&gt;
...</pre>
<h5><a name="elementsNICSTCP">TCP tunnel</a></h5>
<h5><a id="elementsNICSTCP">TCP tunnel</a></h5>
<p>
A TCP client/server architecture provides a virtual network. One VM
@@ -5006,7 +5006,7 @@
&lt;/devices&gt;
...</pre>
<h5><a name="elementsNICSUDP">UDP unicast tunnel</a></h5>
<h5><a id="elementsNICSUDP">UDP unicast tunnel</a></h5>
<p>
A UDP unicast architecture provides a virtual network which enables
@@ -5030,7 +5030,7 @@
&lt;/devices&gt;
...</pre>
<h5><a name="elementsNICSModel">Setting the NIC model</a></h5>
<h5><a id="elementsNICSModel">Setting the NIC model</a></h5>
<pre>
...
@@ -5065,7 +5065,7 @@ qemu-kvm -net nic,model=? /dev/null
ne2k_isa i82551 i82557b i82559er ne2k_pci pcnet rtl8139 e1000 virtio
</p>
<h5><a name="elementsDriverBackendOptions">Setting NIC driver-specific options</a></h5>
<h5><a id="elementsDriverBackendOptions">Setting NIC driver-specific options</a></h5>
<pre>
...
@@ -5253,7 +5253,7 @@ qemu-kvm -net nic,model=? /dev/null
</dd>
</dl>
<h5><a name="elementsBackendOptions">Setting network backend-specific options</a></h5>
<h5><a id="elementsBackendOptions">Setting network backend-specific options</a></h5>
<pre>
...
@@ -5284,7 +5284,7 @@ qemu-kvm -net nic,model=? /dev/null
adjust the size of send buffer in the host. <span class="since">Since
0.8.8</span>
</p>
<h5><a name="elementsNICSTargetOverride">Overriding the target element</a></h5>
<h5><a id="elementsNICSTargetOverride">Overriding the target element</a></h5>
<pre>
...
@@ -5322,7 +5322,7 @@ qemu-kvm -net nic,model=? /dev/null
&lt;/devices&gt;
...</pre>
<h5><a name="elementsNICSBoot">Specifying boot order</a></h5>
<h5><a id="elementsNICSBoot">Specifying boot order</a></h5>
<pre>
...
@@ -5345,7 +5345,7 @@ qemu-kvm -net nic,model=? /dev/null
<span class="since">Since 0.8.8</span>
</p>
<h5><a name="elementsNICSROM">Interface ROM BIOS configuration</a></h5>
<h5><a id="elementsNICSROM">Interface ROM BIOS configuration</a></h5>
<pre>
...
@@ -5374,7 +5374,7 @@ qemu-kvm -net nic,model=? /dev/null
network device.
<span class="since">Since 0.9.10 (QEMU and KVM only)</span>.
</p>
<h5><a name="elementDomain">Setting up a network backend in a driver domain</a></h5>
<h5><a id="elementDomain">Setting up a network backend in a driver domain</a></h5>
<pre>
...
&lt;devices&gt;
@@ -5398,7 +5398,7 @@ qemu-kvm -net nic,model=? /dev/null
<span class="since">Since 1.2.13 (Xen only)</span>
</p>
<h5><a name="elementQoS">Quality of service</a></h5>
<h5><a id="elementQoS">Quality of service</a></h5>
<pre>
...
@@ -5422,7 +5422,7 @@ qemu-kvm -net nic,model=? /dev/null
the Network XML.
</p>
<h5><a name="elementVlanTag">Setting VLAN tag (on supported network types only)</a></h5>
<h5><a id="elementVlanTag">Setting VLAN tag (on supported network types only)</a></h5>
<pre>
...
@@ -5490,7 +5490,7 @@ qemu-kvm -net nic,model=? /dev/null
traffic for that VLAN will be tagged.
</p>
<h5><a name="elementLink">Modifying virtual link state</a></h5>
<h5><a id="elementLink">Modifying virtual link state</a></h5>
<pre>
...
&lt;devices&gt;
@@ -5511,7 +5511,7 @@ qemu-kvm -net nic,model=? /dev/null
<span class="since">Since 0.9.5</span>
</p>
<h5><a name="mtu">MTU configuration</a></h5>
<h5><a id="mtu">MTU configuration</a></h5>
<pre>
...
&lt;devices&gt;
@@ -5530,7 +5530,7 @@ qemu-kvm -net nic,model=? /dev/null
<span class="since">Since 3.1.0</span>
</p>
<h5><a name="coalesce">Coalesce settings</a></h5>
<h5><a id="coalesce">Coalesce settings</a></h5>
<pre>
...
&lt;devices&gt;
@@ -5557,7 +5557,7 @@ qemu-kvm -net nic,model=? /dev/null
<span class="since">Since 3.3.0</span>
</p>
<h5><a name="ipconfig">IP configuration</a></h5>
<h5><a id="ipconfig">IP configuration</a></h5>
<pre>
...
&lt;devices&gt;
@@ -5636,7 +5636,7 @@ qemu-kvm -net nic,model=? /dev/null
configure the guest side of the interface (described above).
</p>
<h5><a name="elementVhostuser">vhost-user interface</a></h5>
<h5><a id="elementVhostuser">vhost-user interface</a></h5>
<p>
<span class="since">Since 1.2.7</span> the vhost-user enables the
@@ -5673,7 +5673,7 @@ qemu-kvm -net nic,model=? /dev/null
<code>&lt;model&gt;</code> element is mandatory.
</p>
<h5><a name="elementNwfilter">Traffic filtering with NWFilter</a></h5>
<h5><a id="elementNwfilter">Traffic filtering with NWFilter</a></h5>
<p>
<span class="since">Since 0.8.0</span> an <code>nwfilter</code> profile
@@ -5713,7 +5713,7 @@ qemu-kvm -net nic,model=? /dev/null
</p>
<h4><a name="elementsInput">Input devices</a></h4>
<h4><a id="elementsInput">Input devices</a></h4>
<p>
Input devices allow interaction with the graphical framebuffer
@@ -5768,7 +5768,7 @@ qemu-kvm -net nic,model=? /dev/null
set. (<span class="since">Since 3.5.0</span>)
</p>
<h4><a name="elementsHub">Hub devices</a></h4>
<h4><a id="elementsHub">Hub devices</a></h4>
<p>
A hub is a device that expands a single port into several so
@@ -5797,7 +5797,7 @@ qemu-kvm -net nic,model=? /dev/null
above</a>.
</p>
<h4><a name="elementsGraphics">Graphical framebuffers</a></h4>
<h4><a id="elementsGraphics">Graphical framebuffers</a></h4>
<p>
A graphics device allows for graphical interaction with the
@@ -6095,7 +6095,7 @@ qemu-kvm -net nic,model=? /dev/null
</dd>
</dl>
<h4><a name="elementsVideo">Video devices</a></h4>
<h4><a id="elementsVideo">Video devices</a></h4>
<p>
A video device.
</p>
@@ -6210,7 +6210,7 @@ qemu-kvm -net nic,model=? /dev/null
</dd>
</dl>
<h4><a name="elementsConsole">Consoles, serial, parallel &amp; channel devices</a></h4>
<h4><a id="elementsConsole">Consoles, serial, parallel &amp; channel devices</a></h4>
<p>
A character device provides a way to interact with the virtual machine.
@@ -6296,14 +6296,14 @@ qemu-kvm -net nic,model=? /dev/null
slot.
</p>
<h5><a name="elementsCharGuestInterface">Guest interface</a></h5>
<h5><a id="elementsCharGuestInterface">Guest interface</a></h5>
<p>
A character device presents itself to the guest as one of the following
types.
</p>
<h6><a name="elementCharParallel">Parallel port</a></h6>
<h6><a id="elementCharParallel">Parallel port</a></h6>
<pre>
...
@@ -6321,7 +6321,7 @@ qemu-kvm -net nic,model=? /dev/null
usually 0, 1 or 2 parallel ports.
</p>
<h6><a name="elementCharSerial">Serial port</a></h6>
<h6><a id="elementCharSerial">Serial port</a></h6>
<pre>
...
@@ -6350,7 +6350,7 @@ qemu-kvm -net nic,model=? /dev/null
<code>type='pci'</code> to select desired location on the PCI bus.
</p>
<h6><a name="elementCharConsole">Console</a></h6>
<h6><a id="elementCharConsole">Console</a></h6>
<p>
The console element is used to represent interactive consoles. Depending
@@ -6422,7 +6422,7 @@ qemu-kvm -net nic,model=? /dev/null
only 1 console.
</p>
<h6><a name="elementCharChannel">Channel</a></h6>
<h6><a id="elementCharChannel">Channel</a></h6>
<p>
This represents a private communication channel between the host and the
@@ -6514,14 +6514,14 @@ qemu-kvm -net nic,model=? /dev/null
<span class="since">Since 0.8.8</span></dd>
</dl>
<h5><a name="elementsCharHostInterface">Host interface</a></h5>
<h5><a id="elementsCharHostInterface">Host interface</a></h5>
<p>
A character device presents itself to the host as one of the following
types.
</p>
<h6><a name="elementsCharSTDIO">Domain logfile</a></h6>
<h6><a id="elementsCharSTDIO">Domain logfile</a></h6>
<p>
This disables all input on the character device, and sends output
@@ -6538,7 +6538,7 @@ qemu-kvm -net nic,model=? /dev/null
...</pre>
<h6><a name="elementsCharFle">Device logfile</a></h6>
<h6><a id="elementsCharFle">Device logfile</a></h6>
<p>
A file is opened and all data sent to the character
@@ -6555,7 +6555,7 @@ qemu-kvm -net nic,model=? /dev/null
&lt;/devices&gt;
...</pre>
<h6><a name="elementsCharVC">Virtual console</a></h6>
<h6><a id="elementsCharVC">Virtual console</a></h6>
<p>
Connects the character device to the graphical framebuffer in
@@ -6572,7 +6572,7 @@ qemu-kvm -net nic,model=? /dev/null
&lt;/devices&gt;
...</pre>
<h6><a name="elementsCharNull">Null device</a></h6>
<h6><a id="elementsCharNull">Null device</a></h6>
<p>
Connects the character device to the void. No data is ever
@@ -6588,7 +6588,7 @@ qemu-kvm -net nic,model=? /dev/null
&lt;/devices&gt;
...</pre>
<h6><a name="elementsCharPTY">Pseudo TTY</a></h6>
<h6><a id="elementsCharPTY">Pseudo TTY</a></h6>
<p>
A Pseudo TTY is allocated using /dev/ptmx. A suitable client
@@ -6613,7 +6613,7 @@ qemu-kvm -net nic,model=? /dev/null
with existing syntax for &lt;console&gt; tags.
</p>
<h6><a name="elementsCharHost">Host device proxy</a></h6>
<h6><a id="elementsCharHost">Host device proxy</a></h6>
<p>
The character device is passed through to the underlying
@@ -6633,7 +6633,7 @@ qemu-kvm -net nic,model=? /dev/null
&lt;/devices&gt;
...</pre>
<h6><a name="elementsCharPipe">Named pipe</a></h6>
<h6><a id="elementsCharPipe">Named pipe</a></h6>
<p>
The character device writes output to a named pipe. See pipe(7) for
@@ -6650,7 +6650,7 @@ qemu-kvm -net nic,model=? /dev/null
&lt;/devices&gt;
...</pre>
<h6><a name="elementsCharTCP">TCP client/server</a></h6>
<h6><a id="elementsCharTCP">TCP client/server</a></h6>
<p>
The character device acts as a TCP client connecting to a
@@ -6739,7 +6739,7 @@ qemu-kvm -net nic,model=? /dev/null
&lt;/devices&gt;
...</pre>
<h6><a name="elementsCharUDP">UDP network console</a></h6>
<h6><a id="elementsCharUDP">UDP network console</a></h6>
<p>
The character device acts as a UDP netconsole service,
@@ -6757,7 +6757,7 @@ qemu-kvm -net nic,model=? /dev/null
&lt;/devices&gt;
...</pre>
<h6><a name="elementsCharUNIX">UNIX domain socket client/server</a></h6>
<h6><a id="elementsCharUNIX">UNIX domain socket client/server</a></h6>
<p>
The character device acts as a UNIX domain socket server,
@@ -6774,7 +6774,7 @@ qemu-kvm -net nic,model=? /dev/null
&lt;/devices&gt;
...</pre>
<h6><a name="elementsCharSpiceport">Spice channel</a></h6>
<h6><a id="elementsCharSpiceport">Spice channel</a></h6>
<p>
The character device is accessible through spice connection
@@ -6797,7 +6797,7 @@ qemu-kvm -net nic,model=? /dev/null
&lt;/devices&gt;
...</pre>
<h6><a name="elementsNmdm">Nmdm device</a></h6>
<h6><a id="elementsNmdm">Nmdm device</a></h6>
<p>
The nmdm device driver, available on FreeBSD, provides two
@@ -6828,7 +6828,7 @@ qemu-kvm -net nic,model=? /dev/null
to the guest console. Device is specified by a fully qualified path.</dd>
</dl>
<h4><a name="elementsSound">Sound devices</a></h4>
<h4><a id="elementsSound">Sound devices</a></h4>
<p>
A virtual sound card can be attached to the host via the
@@ -6881,7 +6881,7 @@ qemu-kvm -net nic,model=? /dev/null
slot, <a href="#elementsAddress">documented above</a>.
</p>
<h4><a name="elementsWatchdog">Watchdog device</a></h4>
<h4><a id="elementsWatchdog">Watchdog device</a></h4>
<p>
A virtual hardware watchdog device can be added to the guest via
@@ -6971,7 +6971,7 @@ qemu-kvm -net nic,model=? /dev/null
</dd>
</dl>
<h4><a name="elementsMemBalloon">Memory balloon device</a></h4>
<h4><a id="elementsMemBalloon">Memory balloon device</a></h4>
<p>
A virtual memory balloon device is added to all Xen and KVM/QEMU
@@ -7056,7 +7056,7 @@ qemu-kvm -net nic,model=? /dev/null
set. (<span class="since">Since 3.5.0</span>)
</dd>
</dl>
<h4><a name="elementsRng">Random number generator device</a></h4>
<h4><a id="elementsRng">Random number generator device</a></h4>
<p>
The virtual random number generator device allows the host to pass
@@ -7150,7 +7150,7 @@ qemu-kvm -net nic,model=? /dev/null
</dl>
<h4><a name="elementsTpm">TPM device</a></h4>
<h4><a id="elementsTpm">TPM device</a></h4>
<p>
The TPM device enables a QEMU guest to have access to TPM
@@ -7210,7 +7210,7 @@ qemu-kvm -net nic,model=? /dev/null
</dd>
</dl>
<h4><a name="elementsNVRAM">NVRAM device</a></h4>
<h4><a id="elementsNVRAM">NVRAM device</a></h4>
<p>
nvram device is always added to pSeries guest on PPC64, and its address
is allowed to be changed. Element <code>nvram</code> (only valid for
@@ -7244,7 +7244,7 @@ qemu-kvm -net nic,model=? /dev/null
</dd>
</dl>
<h4><a name="elementsPanic">panic device</a></h4>
<h4><a id="elementsPanic">panic device</a></h4>
<p>
panic device enables libvirt to receive panic notification from a QEMU
guest.
@@ -7301,7 +7301,7 @@ qemu-kvm -net nic,model=? /dev/null
</dd>
</dl>
<h4><a name="elementsShmem">Shared memory device</a></h4>
<h4><a id="elementsShmem">Shared memory device</a></h4>
<p>
A shared memory device allows to share a memory region between
@@ -7365,7 +7365,7 @@ qemu-kvm -net nic,model=? /dev/null
</dd>
</dl>
<h4><a name="elementsMemory">Memory devices</a></h4>
<h4><a id="elementsMemory">Memory devices</a></h4>
<p>
In addition to the initial memory assigned to the guest, memory devices
@@ -7508,7 +7508,7 @@ qemu-kvm -net nic,model=? /dev/null
</dd>
</dl>
<h4><a name="elementsIommu">IOMMU devices</a></h4>
<h4><a id="elementsIommu">IOMMU devices</a></h4>
<p>
The <code>iommu</code> element can be used to add an IOMMU device.
@@ -7588,7 +7588,7 @@ qemu-kvm -net nic,model=? /dev/null
</dd>
</dl>
<h3><a name="seclabel">Security label</a></h3>
<h3><a id="seclabel">Security label</a></h3>
<p>
The <code>seclabel</code> element allows control over the
@@ -7717,7 +7717,7 @@ qemu-kvm -net nic,model=? /dev/null
being on a file system that lacks security labeling.
</p>
<h3><a name="keywrap">Key Wrap</a></h3>
<h3><a id="keywrap">Key Wrap</a></h3>
<p>The content of the optional <code>keywrap</code> element specifies
whether the guest will be allowed to perform the S390 cryptographic key
@@ -7756,7 +7756,7 @@ qemu-kvm -net nic,model=? /dev/null
<p>Note: DEA/TDEA is synonymous with DES/TDES.</p>
<h2><a name="examples">Example configs</a></h2>
<h2><a id="examples">Example configs</a></h2>
<p>
Example configurations for each driver are provide on the