mirror of
https://gitlab.com/libvirt/libvirt.git
synced 2025-01-01 02:25:24 +00:00
b18c273a24
Historically URIs handled by the remote driver will always connect to the libvirtd UNIX socket. There will now be one daemon per driver, and each of these has its own UNIX sockets to connect to. It will still be possible to run the traditional monolithic libvirtd though, which will have the original UNIX socket path. In addition there is a virproxyd daemon that doesn't run any drivers, but provides proxying for clients accessing libvirt over IP sockets, or tunnelling to the legacy libvirtd UNIX socket path. Finally when running inside a daemon, the remote driver must not reject connections unconditionally. For example, the QEMU driver needs to be able to connect to the network driver. The remote driver must thus be willing to handle connections even when inside the daemon, provided no local driver is registered. This refactoring enables the remote driver to be able to connect to the per-driver daemons. The URI parameter "mode" accepts the values "auto", "direct" and "legacy" to control which daemons are connected to. The client side libvirt.conf config file also supports a "remote_mode" setting which is used if the URI parameter is not set. If neither the config file or URI parameter set a mode, then "auto" is used, whereby the client looks to see which sockets actually exist right now. The remote driver will only ever spawn the per-driver daemons, or the legacy libvirtd. It won't ever try to spawn virtproxyd, as that is only there for IP based connectivity, or for access from legacy remote clients. If connecting to a remote host over any kind of ssh tunnel, for now we must assume only the legacy socket exists. A future patch will introduce a netcat replacement that is tailored for libvirt to make remote tunnelling easier. The configure arg '--with-remote-default-mode=legacy|direct' allows packagers to set a default at build time. If not given, it will default to legacy mode. Eventually the default will switch to direct mode. Distros can choose to do the switch earlier if desired. The main blocker is testing and suitable SELinux/AppArmor policies. Reviewed-by: Andrea Bolognani <abologna@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com> |
||
---|---|---|
.. | ||
libvirtd-admin.socket.in | ||
libvirtd-ro.socket.in | ||
libvirtd-tcp.socket.in | ||
libvirtd-tls.socket.in | ||
libvirtd.aug.in | ||
libvirtd.conf.in | ||
libvirtd.libxl.logrotate.in | ||
libvirtd.logrotate.in | ||
libvirtd.lxc.logrotate.in | ||
libvirtd.pod | ||
libvirtd.policy | ||
libvirtd.qemu.logrotate.in | ||
libvirtd.rules | ||
libvirtd.sasl | ||
libvirtd.service.in | ||
libvirtd.socket.in | ||
libvirtd.sysconf | ||
libvirtd.sysctl | ||
lxc_protocol.x | ||
Makefile.inc.am | ||
qemu_protocol.x | ||
remote_daemon_config.c | ||
remote_daemon_config.h | ||
remote_daemon_dispatch.c | ||
remote_daemon_dispatch.h | ||
remote_daemon_stream.c | ||
remote_daemon_stream.h | ||
remote_daemon.c | ||
remote_daemon.h | ||
remote_driver.c | ||
remote_driver.h | ||
remote_protocol.x | ||
test_libvirtd.aug.in | ||
virt-guest-shutdown.target.in | ||
virtproxyd.service.in |