@bvitnik said in Custom config / cloud-init: https://docs.xcp-ng.org/guides/create-use-custom-xcpng-ubuntu-templates/ I noticed in the documentation, they put "password:" for user password creation. what is working for me : plain_text_passwd: 'myverysecureplaintextpassword' more secure, use a SHA 512 encrypted password, but with : passwd: QChUQYy14yOv_encrypted_password_mgnEFL6TRPIsJ/4 make it encrypted with # mkpasswd --method=SHA-512

@Bill.Oliver obvioulsy, licensing. If you are planning to put Microsoft VMs, beware of licensing with multisockets by hosts, you have to cover them all. By default, you should cover 16 cores with 1 Microsoft Windows Server Standard to get 2 VMs licensed. If you get two sockets, you have to double the licensing (and add 2 packs core to attain your cores coverage...) All licensing based on cores make you think twice when planning CPUs... If you want to, you can go DATACENTER edition, but you still have to cover all the cores...

Starting from Other install media with BIOS (not uefi) is the only combo that is working with Terraform

xe pool-enable-tls-verification Was exactly what I needed, thanks! Worked after that.

@Joe_dev I have a MF unit with similar igpu. I was not able to get it working under any virtualization platform. There is something about amd igpu that makes passing it hard. I believe some have had it working under proxmox with custom kernel and video bios. I never bothered trying all that out so i just gave up on the unit.

Hi @jshiells, Sorry for not answering earlier, Pierre wasn't working during the past weeks. I'll soon investigate on how the load balancer interacts with backups.

Hello, Thanks for your work ! We have some hypervisors of tests at Gladhost, we can use them with pleasure to test your work on xcp-ng 8.3 ! Best regards