External/libvirt
1
0
Fork 0
Code

docs: Slightly alter disks-uri description in virsh man

Browse Source 
It's more accurate this way.

https://bugzilla.redhat.com/show_bug.cgi?id=1638889

Signed-off-by: Martin Kletzander <mkletzan@redhat.com>
This commit is contained in:
Martin Kletzander 2020-12-13 22:27:33 +01:00
parent 5db1fc5602
commit b17eb73446
1 changed files with 11 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
docs/manpages/virsh.rst
View File

@ -3346,17 +3346,17 @@ bind to for incoming disks traffic. Currently it is supported only by QEMU.
Optional *disks-uri* can also be specified (mutually exclusive with Optional *disks-uri* can also be specified (mutually exclusive with
*disks-port*) to specify what the remote hypervisor should bind/connect to when *disks-port*) to specify what the remote hypervisor should bind/connect to when
migrating disks. This can be *tcp://address:port* to specify a listen address migrating disks. This can be *tcp://address:port* to specify a listen address
(which overrides *--listen-address* for the disk migration) and a port or (which overrides *--migrate-uri* and *--listen-address* for the disk migration)
*unix:///path/to/socket* in case you need the disk migration to happen over a and a port or *unix:///path/to/socket* in case you need the disk migration to
UNIX socket with that specified path. In this case you need to make sure the happen over a UNIX socket with that specified path. In this case you need to
same socket path is accessible to both source and destination hypervisors and make sure the same socket path is accessible to both source and destination
connecting to the socket on the source (after hypervisor creates it on the hypervisors and connecting to the socket on the source (after hypervisor creates
destination) will actually connect to the destination. If you are using SELinux it on the destination) will actually connect to the destination. If you are
(at least on the source host) you need to make sure the socket on the source is using SELinux (at least on the source host) you need to make sure the socket on
accessible to libvirtd/QEMU for connection. Libvirt cannot change the context the source is accessible to libvirtd/QEMU for connection. Libvirt cannot change
of the existing socket because it is different from the file representation of the context of the existing socket because it is different from the file
the socket and the context is chosen by its creator (usually by using representation of the socket and the context is chosen by its creator (usually
*setsockcreatecon{,_raw}()* functions). by using *setsockcreatecon{,_raw}()* functions).
migrate-compcache migrate-compcache