vCenter

 View Only
  • 1.  dumb luck - vmotion leaves a vm in no-mans-land, help!

    Posted May 04, 2007 08:20 PM

    Hi,

    got a weird one. I've got a host to decommission (ESX1) and used vmotion to happily shift several VM's to ESX2. BUT one of the VM's sits up at 35% and when I go to investigate, oh no ESX2 is dead, turns out to be fan(s) failure and I can't now get the unit to clear POST because it's a Proliant and knows it has an insufficient cooling solution and halts.

    But the VM is not accessible in any way, VC shows it @ 35%, cancel job is greyed out. Thought about rebooting ESX1 but I cant as there is a production VM there.

    I thought the VM would just come back to the sender in this situation

    Is there a command I can use to recover/reverse out this VM back to ESX1???

    thanks!



  • 2.  RE: dumb luck - vmotion leaves a vm in no-mans-land, help!

    Posted May 04, 2007 08:28 PM

    Have you tried to restart the management agent: service mgmt-vmware restart



  • 3.  RE: dumb luck - vmotion leaves a vm in no-mans-land, help!

    Posted May 04, 2007 08:52 PM

    thanks Dave for replying so quick! don't need to use but I will stash that cmd.

    turns out it was a bit of a rathole and it was "back" running on ESX1 after all.

    I just found out someone has disabled that specific guest's W2K3 MSRDP access. I managed to throw it a registry change via WMI to enable again.

    Useful lesson tho, you can't rely on VC to tell you the score really:

    VC tells me the situation is possibly grim, I can't console into the VM from VC, I try and fail to ping it (f/w blocked, understandable) couldn't MSRDP into it (the co. policy is to allow but someone fiddled!!grrr!). I discover dead host and assume worst and VM is out in space somewhere...but ESX behaved as it should have. If it had been Exchange or something hot running in the VM I'd have copped it sooner as my phone would have not caught fire :smileyhappy:

    thanks

    M



  • 4.  RE: dumb luck - vmotion leaves a vm in no-mans-land, help!

    Posted May 04, 2007 09:48 PM

    there is a knock-on!



  • 5.  RE: dumb luck - vmotion leaves a vm in no-mans-land, help!

    Posted May 04, 2007 09:55 PM

    I just got the failed host back on, but VC has the vm still sitting there @ 35% so I cant try to vmotion out again using the gui.

    So restart the VC service and retry the VI client which now looks good, at least I can use the dialog to try the vmotion again BUT it fails!!! and gives the following error -

    A general system error occured: failed to write VMotion dest (vim.fault.AlreadyExists)

    BUT

    just because not sure what to try next, I tried a second time and IT WORKS! hooray! but would love to understand what I have just done...