@Pilow well you seem to have a nice setup, I am looking forward to more pictures! I wish I could share ours, but im not allowed to

@olivierlambert StartOS lists a 64GB minimum disk size, so i gave it 65GB to be safe. They have a hardware scanner tool on the iso you can boot into, and it does show the 65GB drive. It seems though that somehow the way the drive is presented to the iso installer it does not like and wont give me the option to select it. [image: 1760717638040-8bd48019-b6b2-456d-ab4a-d0a86aa0b016-image.png] https://docs.start9.com/0.3.4.x/diy/diy-x86 here is their install guide https://docs.start9.com/0.3.5.x/flashing-guides/os-x86 here is the github with iso files. i tried the x86 and x86nofree iso files. https://github.com/Start9Labs/start-os/releases/tag/v0.3.5.1 i also saw a post about people having issues with display drivers when installing, so i tried unchecking the VGA option in the Advanced vm options and no change i also tried booting with uefi and with bios and no change here are my advanced VM settings [image: 1760718315195-a8e40ee0-f10b-4032-bfde-7574a79d3e93-image.png] thanks

@dinhngtu Hopefully before the next updates to xcpng. Rolling pool update moves all VM's.... Does this bug clear itself after a VM reboot? Or has the tools to be reinstalled? Is it only cosmetic or does it affect the running VM? Havne't tried this myself and as we have moved all VM's to these new tools I'd like to be aware of what I can expect.

@olivierlambert kindly this project will be a cpa office, i dont think refurb is good idea,?

@olivierlambert Agreed. Thanks, still, for pinging them again. Today being Friday, I'll be in the lab for a bit, troubleshooting other issues unrelated to Xen Orchestra. Would be nice to work on this as well. No worries, though, I'll sit tight and exercise patience.

@Danp @DustinB @ph7 This host does not run any VMs, just used for CR I've increased the dom0 ram to 4GB with no more alarms. [image: 1760735454438-14d145a4-ed5f-40c9-9d97-f9fa5da99023-image.png]

@HolgiB said in Better / more flexible way to add and edit CloudInit templates in XO ?: All this Terraform / Open Tofu stuff is nice but I guess generating VMs via Cloud Init and XO will be the entry level for everyone before trying out a much bigger infrastructure as code solution, right ? Starting to use Terraform is not a big step, and it's how I manage even a small setup with < 20 VMs, though not everything can be managed that way, for example SRs cannot currently be created through terraform, so XO is still needed too. those init files often are technically correct but still fail for some strange reason I agree, debugging cloud-init is not a fun task. I don't know if it is an approach you could take, but in my case I keep my cloud-init extremely simple. It only sets up networking and a single fixed user account with an SSH key. Then other tooling, for example Ansible, takes over from there to configure the VM.

@probain Thank you!