mirror of
https://gitlab.com/libvirt/libvirt.git
synced 2024-08-05 08:23:48 +00:00
c69915ccaf
Local socket connections were outright disabled because there was no "server" part in the URI. However, given how requirements and usage scenarios are evolving, some management apps might need the source libvirt daemon to connect to the destination daemon over a UNIX socket for peer2peer migration. Since we cannot know where the socket leads (whether the same daemon or not) let's decide that based on whether the socket path is non-standard, or rather explicitly specified in the URI. Checking non-standard path would require to ask the daemon for configuration and the only misuse that it would prevent would be a pretty weird one. And that's not worth it. The assumption is that whenever someone uses explicit UNIX socket paths in the URI for migration they better know what they are doing. Partially resolves: https://bugzilla.redhat.com/1638889 Signed-off-by: Martin Kletzander <mkletzan@redhat.com> Reviewed-by: Jiri Denemark <jdenemar@redhat.com> |
||
|---|---|---|
| .. | ||
| index.rst | ||
| libvirtd.rst | ||
| meson.build | ||
| virsh.rst | ||
| virt-admin.rst | ||
| virt-host-validate.rst | ||
| virt-login-shell.rst | ||
| virt-pki-validate.rst | ||
| virt-qemu-run.rst | ||
| virt-sanlock-cleanup.rst | ||
| virt-xml-validate.rst | ||
| virtlockd.rst | ||
| virtlogd.rst | ||