Add host process results in incorrect libvirtd settings for Ubuntu VERSION="24.04.1 LTS (Noble Numbat)" #9864
-
ISSUE TYPE
COMPONENT NAME
CLOUDSTACK VERSION
CONFIGURATIONAdvanced networking OS / ENVIRONMENTPRETTY_NAME="Ubuntu 24.04.1 LTS" SUMMARYWhen adding a kvm host to Cloudstack, the agent configuration automatically adds the option libvirtd_opts='-l' to /etc/default/libvirtd. This creates failures for live migrations between cluster hosts. Documentation here https://docs.cloudstack.apache.org/en/latest/installguide/hypervisor/kvm.html is correct, stating that Ubuntu 20.04 and newer should use the option LIBVIRTD_ARGS="--listen". STEPS TO REPRODUCESimply adding a host via the web interface will do this at least when the host os version is Ubuntu 24.04.1 LTS.
EXPECTED RESULTS
ACTUAL RESULTSAgent configuration process automatically adds the option libvirtd_opts='-l' to /etc/default/libvirtd when the os version is newer than 20.04.
|
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 1 reply
-
Thanks for opening your first issue here! Be sure to follow the issue template! |
Beta Was this translation helpful? Give feedback.
-
If network/bridges have already been configured, ACS will not configure the host again. The automatic configuration on kvm host is out of date, it does not work on some new distributions, due to libvirtd/netplan/nmcli etc. |
Beta Was this translation helpful? Give feedback.
-
Is there a way to disable the automatic configuration during host provisioning? |
Beta Was this translation helpful? Give feedback.
-
@ffslcschools |
Beta Was this translation helpful? Give feedback.
-
After using LIBVIRTD_ARGS=‘--listen’ option on Ubuntu22, libvirtd does not start. After running |
Beta Was this translation helpful? Give feedback.
After using LIBVIRTD_ARGS=‘--listen’ option on Ubuntu22, libvirtd does not start. After running
systemctl mask libvirtd.socket libvirtd-ro.socket libvirtd-admin.socket libvirtd-tls.socket libvirtd-tcp.socket
libvirtd can be started.