🎉🎉🎉

@encryptblockr
Yes, and I documented the process I used a while back here: https://xcp-ng.org/forum/topic/6821/cloud-init-success

I just use the stock cloud image .ova file as my base image. for Ubuntu templates. I use the noble (24.04) image in quite a few instances from my template with success.

Your post mentions cloud-init is not working - some tips to try troubleshooting, when the new VM is provisioned, (assuming you are able to login) I usually run "cloud-init status --wait" and when that completes I run "cloud-init status --long" for a summary of the state. Then you can grep for WARNING in /var/log/cloud-init.log for clues.

If you weren't able to login to the VM - make sure your cloud-init config has the userid's, passwords and SSH keys you will need for login. See the example I posted here, since those are what I use in my lab or some variation.

Feel free to share any troubleshooting steps you have taken, and I will help any way I can. I have setup hundreds of VM's from templates using cloud-init so I have seen many of the challenges it brings.

Thanks, passing the compliment to our teams! 👍

@dj423
Second occurrence of kernel BUG error:

[237621.042604] BUG: unable to handle page fault for address: ffff9bd9bc6c9840 [237621.049589] #PF: supervisor read access in kernel mode [237621.055044] #PF: error_code(0x0000) - not-present page

I am seeing some strange errors on the host (X1), for storage devices that no longer exist on the host. e.g.:

[331863.198883] print_req_error: I/O error, dev tde, sector 74842904 [332612.663953] block tdd: sector-size: 512/512 capacity: 178257920 [332612.711329] block tde: sector-size: 512/512 capacity: 251658240 [333679.019750] print_req_error: 86 callbacks suppressed [333679.019750] print_req_error: I/O error, dev tdd, sector 74924032

The storage devs on host:

tdc 254:2 0 85G 0 disk tda 254:0 0 120G 0 disk tdf 254:5 0 32G 0 disk

Any idea why I would see I/O errors for storage devices that are no longer on the host? I only see this on one VM on this host, all others are fine.

@olivierlambert
Got it, sorry I glossed right over the updates. Ran the updates and everything is green with success. Thanks for taking the time to answer my noob questions!

We are aware aobut it. This is a Debian package bug that will be directly fixed in the next XOA we'll generate (this year, with Debian 12)

@VGerris said in Cloud-init success:

@dj423 thank you, that is really helpful!
I also found : https://cloudinit.readthedocs.io/en/latest/reference/examples.html

Yes the docs are a huge help when crafting big nuanced config scripts. The lead maintainer Chad Smith gave me some pro-tips as well and was a huge help for me when I was learning that stuff. Yes I agree, Xcp-ng rocks!!

Best of luck!

Yes, this one 🙂