rootnomad commented on PR #14153: URL: https://github.com/apache/cloudstack/pull/14153#issuecomment-6473425340
> a smoke test run would not prove anything here as the ansible example he gave is in place. Would be nice if someone else could test it. Good call @DaanHoogland, did exactly that on a Debian 12 (bookworm) KVM host without the ansible workaround. On stock Debian systemd, libvirtd.service runs `ExecStart=/usr/sbin/libvirtd $LIBVIRTD_ARGS` sourced from /etc/default/libvirtd, with libvirtd.socket masked. So only LIBVIRTD_ARGS takes effect and libvirtd_opts is ignored by systemd. - Before the fix (old code sets `libvirtd_opts='-l'` only): libvirtd starts with empty args and does not listen, nothing on the migration port. - After the fix (adds `LIBVIRTD_ARGS="--listen"`): libvirtd listens. These hosts have listen_tls=1, so it binds 16514 rather than 16509, but it's the same mechanism. Host restored afterwards. So on a Debian/Ubuntu host without that ansible workaround, this is the line that actually gets libvirtd listening for live migration. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
