I tried it on a lab host (XCP-ng 8.3, xapi 26.1.16): calling VM.pool_migrate on a halted VM gives me your error, VM_BAD_POWER_STATE with running, halted, so the two values are the state XAPI wanted and the one it found. On the XO side, a migration inside the same pool with no SR or network mapping goes straight to VM.pool_migrate without checking the power state first: https://github.com/vatesfr/xen-orchestra/blob/b59c8f3d20954aa1d72e92c1e8f2db635d74fcba/packages/xo-server/src/xapi/index.mjs#L942-L981. So a stopped VM in that batch would give this, which fits what you remember. I haven't tried the batch migrate from the UI itself though, so I don't know if the UI is supposed to filter halted VMs out before that. It's a good concrete example for the feedback post anyway, XO could just say "this VM is halted" instead of passing XAPI's raw code through.

Ping @Team-XO-Backend

While I was updating all the pools, a micro-update for 5 packages was released again. They come out every week now. Same issue with basic migration. Now it impossible.

Ok, my syntax is oudated. resize_rootfs: true growpart: mode: auto devices: ['/dev/xvda3'] ignore_growroot_disabled: false runcmd: - pvresize /dev/xvda3 - lvextend -r -l +100%FREE /dev/ubuntu-vg/ubuntu-lv || true this one works. final_message. doesn't support any macro like %(uptime) %(UPTIME)

@Danp damned, i forget about this button) Now it works, thanks.

i found that whole pool is not alive enough. Can't reboot or mirgate anything. Have issue only with this 1 pool. Is it safe to reboot hosts? https://paste.vates.tech/?7e565d3abe23fd11#7JcQbjRguFpNfw281asxdmb2Zrd7GKXpuE17iDtwt3KG

@pierrebrunet fixed now, thanks.

how come you get the mac address ? I'm using NetBox Community v4.3.7-Docker-3.3.0 with latest XOA ps : little bug, if you COPY a VM, the netbox plugin will throw an error 400 i guess, for duplicate IP address I just have to change one bit of the mac address of copied VM and the netbox sync will be OK so it checks the mac address... but do not sync it in my netbox

@olivierlambert You got it, I'll do that. Thank you.

This page is being improved as we speak It shouldn't be in "Future improvements" because it's here

@DustinB I advise you not to decide for others what they should do. I'm tired.

@olivierlambert for what concern backup, I think you should ping @florent for XO-5...

@olivierlambert Just to be sure. Thanks.

No worries, always good to have feedback

@olivierlambert as i say, now it works. So nvm)

@Razor_648 While I was writing my previous message, I have been reminded that there are also issues with LVHDoISCSI SR and CBT, you should disable CBT on your backup job and on all VDI on the SR. It might help with the issue.

@olivierlambert we are thinking about implementing a relationnal DB in the future. Maybe it could offer to stock snapshots as "archived"... I don't know for now. I understand that it could be risky to delete old snapshots, and maybe the responsability of setting the snaspshots retention can be an ACL subject... There are plenty of avenues of work on this topic, and more generally on the retention of information about objects, tasks, and other actions. It's a real in-depth topic.

Thanks for fixing this!