Update Host LXC Installation page of Installation Guide

[daviftorres]

By deploying a new LXC compute cluster to add to my CloudStack deployment I found a documentation not exactly not up-to-date.

At the beginning, on the Prepare the Operating System, i made it consistent with the other hypervisor's instructions. Then, I made a few changes to the speech to avoid duplications with the KVM installation and referred to it at the steps Install and Configure libvirt and Configure the Security Policies.

In my deployment on Ubuntu 24.04 LTS, I had to install libvirt-daemon-driver-lxc to solve an issue when restarted libvirtd after applying the required changes.

Note: there is issue reported in apache/cloudstack#8109 that prevents LXC instances to get created but do not affect the instructions improvements.

---

📚 Documentation preview 📚: https://cloudstack-documentation--528.org.readthedocs.build/en/528/

[daviftorres]

Notes to the reviewer:

It might look like I did many small changes. In fact, I copied the block from the KVM section to the LXC section that in the past was equal but over time was only updated on the KVM page and the LXC page was lagging behind.

Then, I also removed some of the repetition that was very specific and added a note to look at the KVM page since the LXC required the same KVM instructions to be able to run its System VMs.

Sorry if it looks like too much or confusing but the diff from GitHub is not doing a good job to understand the changes.

And feel free to suggest or making any changes your self if you feel like so.

[daviftorres]

Hey @nvazquez , do you think you can help me with this PR? For some reason, no reviewer was automatically assigned to it loke the other ones.

Sorry for pinging you directly but I have no key contact for this repo.

Regards,

[daviftorres]

hey @DaanHoogland , do you know why this PR did not get assigned to a reviewer since I converted from "draft" to "ready for review"?

[DaanHoogland]

hey @DaanHoogland , do you know why this PR did not get assigned to a reviewer since I converted from "draft" to "ready for review"?

PRs don’t automatically get assigned reviewers. Though some people have a business interest in the project all work is on voluntary basis. In general you’ll have to request a reviewer directly to look at your PR. Let me have a look.

[DaanHoogland]

@nvazquez , any glaring errors?

[nvazquez]

@blueorangutan docbuild

[blueorangutan]

@nvazquez a Jenkins job has been kicked to build the document. I'll keep you posted as I make progress.

[blueorangutan]

QA-Doc build preview: https://qa.cloudstack.cloud/builds/docs-build/pr/528. (QA-JID 405)

[nvazquez]

Hi @daviftorres sorry for the delay - I will review your PR soon

[nvazquez]

Thanks @daviftorres - LGTM

[DaanHoogland]

@daviftorres , can you confirm that the method you descibe actually works? i.e. have you tested it (cc @nvazquez )

[davift]

The GitHub diff might look like I made a lot of changes, but it's mostly just updating the code with the KVM hypervisor deployment content, which the LXC deployment depends on.

To answer your questions @DaanHoogland: there's still a bug (apache/cloudstack#8109) that prevents deploying LXC instances through CloudStack.

That said, I was able to deploy LXC instances directly on the hypervisor via CLI, so the setup process for LXC is working.