VM Disk Not Migrating due to Backup Running

Danp

Check the VM's Advanced tab to see if this option is enabled --

allySalami

@Danp I don't have that option in the Advanced Tab.

Danp

@allySalami I'm not sure how that could be. You checked the VM's Advanced tab, correct? Are you running XOA or XO from sources? What is your current version / commit?

allySalami

@Danp I'm using version 8.3

acebmxer

@allySalami

click on About in XO...

allySalami

@acebmxer!!

acebmxer

@allySalami

Let someone else comfirm but think you are way out of date on xo. Might be best to deploy a new one.

allySalami

@acebmxer Yeah, I definitely believe this is not the latest version, but I was told it was kept like that for a reason. Can't quite remember what the reasoning is, as this is for another company who utilizes xoa.

But, would running this command ' xe vm-reset-powerstate uuid=<VM_UUID> --force ' reboot the vm?

Danp

That XOA version was released over 5 years ago. You really should share these kind of details in advance to avoid nonproductive exchanges. I recommend that you revisit the reason that they are "stuck" on this old version.

In current releases of XOA, you can resolve the issue by running a successful backup job that includes the affected VM.

To manually resolve the issue, you need to clear the left over keys in the blocked-operation parameter. For example, this will clear these keys for a VM with UUID be0a9812-fd14-be75-e2fa-40c31ce8875c --

vm_uuid=be0a9812-fd14-be75-e2fa-40c31ce8875c
xe vm-param-remove uuid=$vm_uuid param-name=blocked-operations param-key=migrate_send
xe vm-param-remove uuid=$vm_uuid param-name=blocked-operations param-key=pool_migrate

olivierlambert

I think we got a new record here

XO 5.73 was indeed released in July 2022: https://xen-orchestra.com/blog/xen-orchestra-5-73/

Danp

@olivierlambert It's even older than that.

https://github.com/vatesfr/xen-orchestra/blob/master/CHANGELOG.v5.md#5540-2020-12-29

https://xen-orchestra.com/blog/xen-orchestra-5-54/