and hda disks will boot from hda (sorted disks are: hda, hdc, vda, vdb). It
can be tricky to configure in the desired way, which is why per-device boot
elements (see `Hard drives, floppy disks, CDROMs`_, `network
- interfaces <#elementsNICS>`__, and `USB and PCI devices <#elementsHostDev>`__
+ interfaces <#elementsNICS>`__, and `Host device assignment`_
sections below) were introduced and they are the preferred way providing full
control over booting order. The ``boot`` element and per-device boot elements
are mutually exclusive. :since:`Since 0.1.3, per-device boot since 0.8.8`
The offset specifies where the lease is stored within the file. If the lock
manager does not require an offset, just pass 0.
-:anchor:`<a id="elementsHostDev"/>`
Host device assignment
~~~~~~~~~~~~~~~~~~~~~~
There are several libvirt functions, all with the prefix ``virNodeDevice``,
which deal with management of host devices that can be handed to guests via
passthrough as <hostdev> elements in `the domain
-XML <formatdomain.html#elementsHostDev>`__. These devices are represented as a
+XML <formatdomain.html#host-device-assignment>`__. These devices are represented as a
hierarchy, where a device on a bus has a parent of the bus controller device;
the root of the hierarchy is the node named "computer".