@simonp I'm not sure which one as I can see 2 config.tom file. 1st is under "/root/.config/xo-server/" config.toml.txt 2nd is under "/opt/xo/xo-server/" config.toml2.txt Both config.toml attached. Thank you. Best regards, Azren

@florent Thanks, if there is something I need to do to coalesce the vdis to avoid disaster, that would be good to understand. I had been thinking it was just an XO issue that would not affect running vms and their vdis.

@olivierlambert Fun fact -lah is short for lazy ass human AI is coming... [image: 1761837446934-feb6ff1a-7269-4c37-84b8-8ed1d64c3d68-image.png]

If XO from sources, double check you are fully up to date in the first place. You maybe used an outdated V2V code that wasn't asking for the template, causing the issue you experience now.

Then reboot than broken host and in the meantime, re-issue the power reset command from the master.