Runnig VM shows as stopped in wrong pool

olivierlambert

I suppose you disconnect/reconnect the pool in Settings/server of Xen Orchestra? (or restart xo-server already)

shorian

olivierlambert

This VM is obviously somewhere, do you have any duplicate in xe vm-list output?

I find it really weird it's not duplicated, you should see it via xl list at least Is there any other host?

shorian

It's listed in XO as being halted on Host1 without any disks but (correctly) doesn't show on Host1 under xe list, meanwhile it's listed (correctly) in Host2 xe list as running on there.

Have tried from XO on different boxes (Host1, Host2 and also on a different host) but all report exactly as above - halted on Host1 with no disks.

Have restarted toolstack on Host1 and Host2, have rebooted Host1 and Host2, have rebooted VM from ssh (daren't do it from within XO in case it doesn't come up, similarly dare not stop it from ssh and then try to start it from XO), have tried migrating within XO but does not work, have tried booting from XO (despite it already running) but it does not work.

In summary - in reality it is running on Host2 just fine; xe list is reporting correctly but XO is not.

olivierlambert

Wait, host1 and host2 are on 2 different pools?

shorian

Correct

olivierlambert

So just to check, if you disconnect the host 1 pool in Xen Orchestra, do you see the VM appearing suddenly? If it's a duplicate, it should do the trick (if not, leave host 1 disconnected and restart xo-server to be sure, don't forget to force refresh your browser)

shorian

Ah, you genius. Yes, disconnecting Host1/Pool1 does indeed have the VM magically appear. So there must be a duplicate on Host1 that 'shields' XO from seeing it - only the dup doesn't show in XO. Will check via CLI - I have enough now to find the issue.

Thank you!!

olivierlambert

That's exactly the issue. So there's something in Host1 still returning the UUID that's also on host2. Find it, remove it and this will solve your problem.

shorian

Solved.

Thank you - superb deduction skills

olivierlambert

You still had the XAPI object in host1? Feel free to provide more details so the community can also enjoy the solution

shorian

Correct - through the CLI one could see that the old VM that had been migrated from Host1 to Host2 was still showing under Host1, whilst the migrated copy was showing as running on Host2. Once the Host1 remnant of the migration was removed that cleared things and XO correctly reported the VM as running on Host2 with its disks attached.

TLDR - There were no other conflicts beyond what appeared through XO to be the only version sitting halted on Host1, but through the CLI one could see the halted copy on Host1 and the running copy on Host2. Somehow the running version did not show in XO until the remnant was removed.

Thanks for your help @olivierlambert