docs: manpages: Clarify that only TLS/TCP remote access needs 'virtproxyd'

Spell out that TCP and TLS needs virtproxyd as 'off-host' might mean
that also ssh transport requires it.

Also fix the name of the 'virtproxyd' daemon.

Signed-off-by: Peter Krempa <pkrempa@redhat.com>
Reviewed-by: Michal Privoznik <mprivozn@redhat.com>
This commit is contained in:
Peter Krempa 2023-04-20 10:58:18 +02:00
parent 93f6b820e2
commit b9725e7045
12 changed files with 24 additions and 24 deletions

View File

@ -30,8 +30,8 @@ This daemon runs on virtualization hosts to provide management for bhyve virtual
machines.
The ``virtbhyved`` daemon only listens for requests on a local Unix domain
socket. Remote off-host access and backwards compatibility with legacy
clients expecting ``libvirtd`` is provided by the ``virtproxy`` daemon.
socket. Remote access via TLS/TCP and backwards compatibility with legacy
clients expecting ``libvirtd`` is provided by the ``virtproxyd`` daemon.
Restarting ``virtbhyved`` does not interrupt running guests. Guests continue to
operate and changes in their state will generally be picked up automatically

View File

@ -30,8 +30,8 @@ This daemon runs on virtualization hosts to provide management for host network
interfaces.
The ``virtinterfaced`` daemon only listens for requests on a local Unix domain
socket. Remote off-host access and backwards compatibility with legacy
clients expecting ``libvirtd`` is provided by the ``virtproxy`` daemon.
socket. Remote access via TLS/TCP and backwards compatibility with legacy
clients expecting ``libvirtd`` is provided by the ``virtproxyd`` daemon.
Restarting ``virtinterfaced`` does not interrupt running guests. Guests continue to
operate and changes in their state will generally be picked up automatically

View File

@ -30,8 +30,8 @@ This daemon runs on virtualization hosts to provide management for LXC
containers.
The ``virtlxcd`` daemon only listens for requests on a local Unix domain
socket. Remote off-host access and backwards compatibility with legacy
clients expecting ``libvirtd`` is provided by the ``virtproxy`` daemon.
socket. Remote access via TLS/TCP and backwards compatibility with legacy
clients expecting ``libvirtd`` is provided by the ``virtproxyd`` daemon.
Restarting ``virtlxcd`` does not interrupt running guests. Guests continue to
operate and changes in their state will generally be picked up automatically

View File

@ -30,8 +30,8 @@ This daemon runs on virtualization hosts to provide management for virtual
networks.
The ``virtnetworkd`` daemon only listens for requests on a local Unix domain
socket. Remote off-host access and backwards compatibility with legacy
clients expecting ``libvirtd`` is provided by the ``virtproxy`` daemon.
socket. Remote access via TLS/TCP and backwards compatibility with legacy
clients expecting ``libvirtd`` is provided by the ``virtproxyd`` daemon.
Restarting ``virtnetworkd`` does not interrupt running guests. Guests continue to
operate and changes in their state will generally be picked up automatically

View File

@ -29,8 +29,8 @@ previously provided by the monolithic ``libvirtd`` daemon.
This daemon runs on virtualization hosts to provide management for host devices.
The ``virtnodedevd`` daemon only listens for requests on a local Unix domain
socket. Remote off-host access and backwards compatibility with legacy
clients expecting ``libvirtd`` is provided by the ``virtproxy`` daemon.
socket. Remote access via TLS/TCP and backwards compatibility with legacy
clients expecting ``libvirtd`` is provided by the ``virtproxyd`` daemon.
Restarting ``virtnodedevd`` does not interrupt running guests. Guests continue to
operate and changes in their state will generally be picked up automatically

View File

@ -30,8 +30,8 @@ This daemon runs on virtualization hosts to provide management for network
filters.
The ``virtnwfilterd`` daemon only listens for requests on a local Unix domain
socket. Remote off-host access and backwards compatibility with legacy
clients expecting ``libvirtd`` is provided by the ``virtproxy`` daemon.
socket. Remote access via TLS/TCP and backwards compatibility with legacy
clients expecting ``libvirtd`` is provided by the ``virtproxyd`` daemon.
Restarting ``virtnwfilterd`` does not interrupt running guests. Guests continue to
operate and changes in their state will generally be picked up automatically

View File

@ -30,8 +30,8 @@ This daemon runs on virtualization hosts to provide management for QEMU virtual
machines.
The ``virtqemud`` daemon only listens for requests on a local Unix domain
socket. Remote off-host access and backwards compatibility with legacy
clients expecting ``libvirtd`` is provided by the ``virtproxy`` daemon.
socket. Remote access via TLS/TCP and backwards compatibility with legacy
clients expecting ``libvirtd`` is provided by the ``virtproxyd`` daemon.
Restarting ``virtqemud`` does not interrupt running guests. Guests continue to
operate and changes in their state will generally be picked up automatically

View File

@ -29,8 +29,8 @@ previously provided by the monolithic ``libvirtd`` daemon.
This daemon runs on virtualization hosts to provide management for secret data.
The ``virtsecretd`` daemon only listens for requests on a local Unix domain
socket. Remote off-host access and backwards compatibility with legacy
clients expecting ``libvirtd`` is provided by the ``virtproxy`` daemon.
socket. Remote access via TLS/TCP and backwards compatibility with legacy
clients expecting ``libvirtd`` is provided by the ``virtproxyd`` daemon.
Restarting ``virtsecretd`` does not interrupt running guests. Guests continue to
operate and changes in their state will generally be picked up automatically

View File

@ -30,8 +30,8 @@ This daemon runs on virtualization hosts to provide management for storage
pools.
The ``virtstoraged`` daemon only listens for requests on a local Unix domain
socket. Remote off-host access and backwards compatibility with legacy
clients expecting ``libvirtd`` is provided by the ``virtproxy`` daemon.
socket. Remote access via TLS/TCP and backwards compatibility with legacy
clients expecting ``libvirtd`` is provided by the ``virtproxyd`` daemon.
Restarting ``virtstoraged`` does not interrupt running guests. Guests continue to
operate and changes in their state will generally be picked up automatically

View File

@ -30,8 +30,8 @@ This daemon runs on virtualization hosts to provide management for VirtualBox
virtual machines.
The ``virtvboxd`` daemon only listens for requests on a local Unix domain
socket. Remote off-host access and backwards compatibility with legacy
clients expecting ``libvirtd`` is provided by the ``virtproxy`` daemon.
socket. Remote access via TLS/TCP and backwards compatibility with legacy
clients expecting ``libvirtd`` is provided by the ``virtproxyd`` daemon.
Restarting ``virtvboxd`` does not interrupt running guests. Guests continue to
operate and changes in their state will generally be picked up automatically

View File

@ -30,8 +30,8 @@ This daemon runs on virtualization hosts to provide management for Virtuozzo
virtual machines.
The ``virtvzd`` daemon only listens for requests on a local Unix domain
socket. Remote off-host access and backwards compatibility with legacy
clients expecting ``libvirtd`` is provided by the ``virtproxy`` daemon.
socket. Remote access via TLS/TCP and backwards compatibility with legacy
clients expecting ``libvirtd`` is provided by the ``virtproxyd`` daemon.
Restarting ``virtvzd`` does not interrupt running guests. Guests continue to
operate and changes in their state will generally be picked up automatically

View File

@ -30,8 +30,8 @@ This daemon runs on virtualization hosts to provide management for Xen virtual
machines.
The ``virtxend`` daemon only listens for requests on a local Unix domain
socket. Remote off-host access and backwards compatibility with legacy
clients expecting ``libvirtd`` is provided by the ``virtproxy`` daemon.
socket. Remote access via TLS/TCP and backwards compatibility with legacy
clients expecting ``libvirtd`` is provided by the ``virtproxyd`` daemon.
Restarting ``virtxend`` does not interrupt running guests. Guests continue to
operate and changes in their state will generally be picked up automatically