@hoberion This should be fixed since XO 5.48 (xo-web 5.61.1) @hoberion said in notifications: @pdonias said in notifications: Hi @hoberion, what version are you using? xo-server 5.60.0 xo-server 5.60.0 was shipped with XO 5.47. Could you update your XOA and confirm that it fixes it? It should happen once more after the update and then it shouldn't happen any more.

Check dmesg in the VM

Hi! I suppose you mean XOA? And yes, you can, until we have a UUID bind per XOA.

ok, could remove the vm by using the command xe vm-reset-powerstate uuid=******* --force, then I could remove the host