Live Migration gone bad, Help!
-
So, I Migrated a vm from an old pool (Citrix Xen Server 7.1) to a new pool (XCP 8.1). It appears that the migration was successful but Xen Orchestra is showing the vm on the old pool with no disks and I can't shut it down or anything. And Xen Orchestra is not showing the vm in the new pool. But you can see it's disk in the new pool's SR. It's disk shows in the old pools SR also but not attached to a running VM. on Xen Orchestra I can't get to the console or anything of this VM.
On XCP-ng Center I am able to manage this VM as i'm only managing the new pool with XCP-ng. Help? Options? Best thing to do now?
-
First I'd check if a VM with the same UUID exists in the new pool, with its VDIs. Use command line for that as XO will get confused if the same VM exists in both pools (which can happen when cross-pool migration encounters an issue at the end of the migration, especially when migrated from an old XSpool). Disconnecting the old pool temporarily from XO may also be sufficient to allow XO to see it on the new pool (if it's actually duplicated).
-
so yeah it shows as running with same uuid on both pools with
xe vm-list power-state:runningbut I don't think it's really running on the old pool. as it's disk isn't even attached? and I can't get to the console.
-
I'd force-shutdown it on the old pool, check that everything is fine on the new pool, check that I have backups of the VM and then delete it from the old pool if all is right.
-
@stormi makes sense I just have other VMs in the old pool also so I can't really just pull the plug on all those hosts. The temp remove from XO did let me manage the migrated VM though, so thank you for the suggestion. It seems you are right though the issue is with the old pool now and I need to get rid of that VM.
-
@stormi I think this at least puts me in a good place to fix it with downtime window. so thank you! =).
-
@stormi so to be clear i can't force shutdown it on the old pool unless you know a way to. it tells me "internal error: Ojbect with type VM and id blahblah /cofnig does not exist in xenopsd (this is trying force shutdown with xen center, it also didn't work with xo).
-
Maybe a simple toolstack restart will solve it. There's also the option of trying
xe vm-reset-powerstateon the VM. -
@stormi OH MY! you're my hero, not sure why I didn't think of that! tool stack restart for the win!
-
@stormi so now I have to just figure out how to delete the ghost vm before i reconnect the pool to XO. in xen center I can't delete it for some reason .. guess i'll try cli (never deleted a vm like that before)
