@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!

I thought I would share some success with cloud-init. I know it has been a pain for others to get working. Please disregard if this is old news.

Just for fun, I wanted to see if I could just use the stock/prebuilt Ubuntu 22.04-LTS cloud ready images I have used in production. Almost like magic it worked fantastic. I expected hours of pain and debugging like others have had to suffer. However to it took me about 2 minutes to spin up a fully configured Ubuntu VM with all my PKI keys, users, updates, packages, configs, etc.

So here is what I did, just in case this is helpful for any other noobies like myself getting acquainted with XO and using cloud-init.

So I used the prebuilt cloud image for Ubuntu found here: https://cloud-images.ubuntu.com/jammy/current/

Step 1:
I selected the "jammy-server-cloudimg-amd64.ova" stock file for vmware/virtual box and downloaded.

Step 2:
Then in XO, I imported the file as a VM - import - VM.

Step 3:
Then I went into settings, and created a new cloud config with my usual user, ssh, packages, and other custom settings as I normally use in the lab for testing prior to rolling into production. I just copy/pasted my full config, and saved it.

Step 4:
Then I converted the cloud image VM I imported in step 2 into a template.

Step 5:
Then I created a fresh VM, using this new template, making sure to select my cloud-init config by checking the "Custom config" selection under Install settings.

Step 6:
Then I opened the console to watch for FAIL errors. Everything looked good. Then I logged in with my ansible account configured in the cloud-init. Then I tested from my ansible control node, and logged in. I inspected /var/log/cloud-init.log for any errors, and finally I ran "cloud-init query userdata" to see how it rendered the config settings. Everything works as it should.

Next I will try the cloud-init config with jinja2 template directives and see if the jinja engine works as well, so I can use one config for all distros I will be using. Then test network config settings. Then test on Centos, Rocky, RHEL cloud-ready images and report back if I run into any snags on those.

@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!

@Andrew

Got it.
Yes the hosts are running 8.2.1. I will run an update on the XO VM and see if that remedies the errors.

Thanks!

I keep getting this error "Error: Lock file is already being held" when I run a full backup job, or delta backup for VM's. If I move the backups to another location, and clean out the directory for VM backups then run the jobs they run fine. But the next day they fail, until I delete or relocate the previous backups. The backups are stored on an SMB share, VM disks are on shared NFS storage SR in a 3 host pool. Other backups run fine for meta and XO-configs, only get the error on VM backup jobs. I have deleted and re-created the backup jobs, and made sure there are no file access issues to the share.

I am on XO from sources, version 5.107.5, (xo-web: 5.109.0) commit 4f31b, with version 8.2 hosts.

Anyone seen this issue, or know any tips to troubleshoot?
Thanks!

@andyhhp
Can we migrate VM's over to another pool with the different CPU type?
Thank you

Is it ok to mix hosts with Intel and Ryzen CPU in the same pool, or does that even matter? As pertaining to migrating VM instances between them? Thinking of refreshing my hosts to more modern CPU/RAM - but I don't want to induce issues of compatibility.
Thank you

Re: trying to use netdata in XOA and I get

If anyone runs into this error, what fixed mine was going into the xoa vm, and issuing:

sudo su -
chown root:netdata -R /usr/share/netdata

Hope it helps others.

I thought I would share some success with cloud-init. I know it has been a pain for others to get working. Please disregard if this is old news.

Just for fun, I wanted to see if I could just use the stock/prebuilt Ubuntu 22.04-LTS cloud ready images I have used in production. Almost like magic it worked fantastic. I expected hours of pain and debugging like others have had to suffer. However to it took me about 2 minutes to spin up a fully configured Ubuntu VM with all my PKI keys, users, updates, packages, configs, etc.

So here is what I did, just in case this is helpful for any other noobies like myself getting acquainted with XO and using cloud-init.

So I used the prebuilt cloud image for Ubuntu found here: https://cloud-images.ubuntu.com/jammy/current/

Step 1:
I selected the "jammy-server-cloudimg-amd64.ova" stock file for vmware/virtual box and downloaded.

Step 2:
Then in XO, I imported the file as a VM - import - VM.

Step 3:
Then I went into settings, and created a new cloud config with my usual user, ssh, packages, and other custom settings as I normally use in the lab for testing prior to rolling into production. I just copy/pasted my full config, and saved it.

Step 4:
Then I converted the cloud image VM I imported in step 2 into a template.

Step 5:
Then I created a fresh VM, using this new template, making sure to select my cloud-init config by checking the "Custom config" selection under Install settings.

Step 6:
Then I opened the console to watch for FAIL errors. Everything looked good. Then I logged in with my ansible account configured in the cloud-init. Then I tested from my ansible control node, and logged in. I inspected /var/log/cloud-init.log for any errors, and finally I ran "cloud-init query userdata" to see how it rendered the config settings. Everything works as it should.

Next I will try the cloud-init config with jinja2 template directives and see if the jinja engine works as well, so I can use one config for all distros I will be using. Then test network config settings. Then test on Centos, Rocky, RHEL cloud-ready images and report back if I run into any snags on those.

@olivierlambert
Is that the same as "Auto power on"? I will give that a try.
Thank you!

Hello,

I think I must be doing something wrong. Pretty new to the xcp-ng stack, I have a single host xcp-ng 8.2 with xoa 5.80. Everything is running great on this first host, but I notice when I have rebooted the host the xoa instance does not start up, or sometimes it starts, but I could not connect. I have addressed it static, and with dhcp, thinking the dynamic address was messing with me.

What is the correct way to shut the pool/host down? I have been in xoa and selected stop host, and I have run shutdown -r now on the command line. I get it right back by reloading xoa from the main page on my host, but I would think it should just boot up like the other vm's. I swapped out a suspect disk in the machine thinking it was corrupting the disk, but no change. I have also noticed the plugins are now only xoa and telemetry.

Thank you!