External/libvirt
1
0
Fork 0
mirror of https://gitlab.com/libvirt/libvirt.git synced 2024-08-07 01:13:49 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: Remove broken link to Xen channel doc

Browse Source 
Many of Xen's text documents have been converted to man pages over
the years, the channel doc being one of them. Replace the broken
channel.txt link with the name of the man page providing the same
information.

Signed-off-by: Jim Fehlig <jfehlig@suse.com>
Reviewed-by: Michal Privoznik <mprivozn@redhat.com>
This commit is contained in:
Jim Fehlig 2021-02-04 16:32:50 -07:00
parent 87320046c0
commit 3068294e77
1 changed files with 4 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
docs/formatdomain.rst
View File

@ -6353,11 +6353,10 @@ types have different ``target`` attributes.
``xen`` ``xen``
Paravirtualized Xen channel. Channel is exposed in the guest as a Xen console Paravirtualized Xen channel. Channel is exposed in the guest as a Xen console
but identified with a name. Setup and consumption of a Xen channel depends on but identified with a name. Setup and consumption of a Xen channel depends on
software and configuration in the guest (for more info, please see software and configuration in the guest. See the xen-pv-channel(7) man page
http://xenbits.xen.org/docs/unstable/misc/channel.txt). Channel source path for more information. Channel source path semantics are the same as the virtio
semantics are the same as the virtio target type. The ``state`` attribute is target type. The ``state`` attribute is not supported since Xen channels lack
not supported since Xen channels lack the necessary probing mechanism. the necessary probing mechanism. :since:`Since 2.3.0`
:since:`Since 2.3.0`
``spicevmc`` ``spicevmc``
Paravirtualized SPICE channel. The domain must also have a SPICE server as a Paravirtualized SPICE channel. The domain must also have a SPICE server as a
`graphics device <#elementsGraphics>`__, at which point the host piggy-backs `graphics device <#elementsGraphics>`__, at which point the host piggy-backs