Migrating Powered Off VM Results In VDI_CBT_ENABLED Failure Error
-
I'm a little lost on this one, and feel like maybe I'm missing something (went back through some previous blogs posts about CBT but didn't see anything related to this and the error doesn't appear on any google searches).
In my lab, I have a VM I am trying to migrate while powered off and it's giving me the below error whenever I do it.
}, "start": 1762284957343, "status": "failure", "updatedAt": 1762284960438, "end": 1762284960438, "result": { "code": "VDI_CBT_ENABLED",Any clue what this means? CBT is actually NOT enabled for this particular VDI either.
My XO is on the latest commit (58f02), hosts are all on 8.3 but don't have the most recent patches yet.
-
@planedrop does your VM have a snapshot ?
-
It is possibly active on a snapshot of this VM?
-
@olivierlambert Yes, it does. I should've noticed that, woops.
Is it not possible to migrate a VM with any snapshots at all or?
-
I don't think so. The easiest thing to do is to remove the snapshot.
-
@olivierlambert OK this makes sense.
Though it does bring up 2 thoughts:
- If backups require a snapshot to exist, how would one migrate a VM that has any associated backups?
- I think the error should be more descriptive than the CBT error I mentioned above
Thanks for the help here!
-
No, backup doesn't require anything to exist on your XCP-ng host, you can always restore or backup regardless the snapshot.
-
@olivierlambert right that makes sense. More so what I meant is, if you have a VM you want to migrate to another host, but that VM has a backup job (and therefore at least one snapshot since the backup jobs require there to be a snapshot at all times), then you can't migrate that VM.
So seems to me like backups and VM migration abilities sort of conflict with each other.
Or maybe there's something I'm misunderstanding here.
-
Doing a storage migration will change the VDI UUID in any case, so it won't be able to do a delta/incremental anyway
