Did the three hosts in my lab pool, nothing blew up so I guess that's good. Just nfs storage with a few windows VMs and a Debian 13 for XO from sources.
I think everything is now an efi boot, but no secure boot machines.
@hitechhillbilly I'd say this is normal if you are low on RAM and you are doing a live VDI migration. XCP-ng requires some amount of free RAM on the host to be able to live migrate the VDI. The larger the VDI, the more RAM is needed but exact sizing is unknown to me. I've encountered this error numerous times so I consider it common.
The way around this is to shutdown the VM and then migrate the VDI. RAM requirements in that case are much much lower.
@vaewyn There is an emergency transition to new master xe command. Also, make sure all your hosts are properly time syncronized to each other or there can be pool issues.
Try first:
xe pool-designate-new-master host-uuid=<new-master-uuid>
If that fails, you will need to run on the slave server:
xe pool-emergency-transition-to-master
@MathieuRA
Hi,
That's the wired thing, no error in logs...
But I found why : I have "profile" scope in my OIDC configuration for a while, it seems to broke SSO in last version. Without it, it works.
Thank you
