requesting docbuild

Your request had been received, i'll go and build the documentation and check the output log for errors.

This shouldn't take long.

Build finished. You can review it at: https://acs-www.shapeblue.com/docs/WIP-PROOFING/pr192//

Build Log Output:

No log errors found to report.//

@Hudratronium that's no true, you need to mask the services to get old behaviour. We've fixed that in cloudstack-agent I think, @shwstppr @davidjumani - can you confirm?

On Ubuntu we've to do this to then get libvirtd listen on tcp/ssl port:

systemctl mask libvirtd.socket libvirtd-ro.socket libvirtd-admin.socket libvirtd-tls.socket libvirtd-tcp.socket
systemctl restart libvirtd

@Hudratronium that's no true, you need to mask the services to get old behaviour. We've fixed that in cloudstack-agent I think, @shwstppr @davidjumani - can you confirm?

On Ubuntu we've to do this to then get libvirtd listen on tcp/ssl port:

systemctl mask libvirtd.socket libvirtd-ro.socket libvirtd-admin.socket libvirtd-tls.socket libvirtd-tcp.socket
systemctl restart libvirtd

Hi @rhtyd

At that time i raised an issue that, as far as i got this, is fixed for release 4.15.1
apache/cloudstack#4754

On Ubuntu - as fas as i understood @shwstppr , that was already part of the configuration script.

It might be an idea, as this topic is quiet crucial, that for the offical guides some of the developers add some content to the documentation.
From an user point of view, the kvm-installation in the docs inherits an manual configuration of libvirt (as well as SELinux / AppArmor).
As far as i got during the last months, this is all done automatically during the cloudstack-agent installation.
So it might be good to restructure the whole side and give some additonal input which configurtation is done already?

@Hudratronium yes that's correct. This is fixed for 4.15.1 in apache/cloudstack#4756 and therefore I think the doc changes are not necessary, this PR can be closed. What do you think?

@rhtyd
okay, will do so :-)