Original Problem:
- ESX 4.1 host - running on Sun blade ... status shows as "disconnected" in vCenter.
- Several VM's on "disconnected" ESX host are still ping'able and working fine.
- ESX is technically still running ok as are the VM'son "disconnected" status. I suspect this is why VMotion doesn't kick in.
- All ESX 4.1 hosts are on Sun blades and use shared storage (not a problem, just some backgroung for ya')
My Solution:
- RDP'd to VM's on "disconnected" host. Powered them down.
- SSH to working ESX 4.1 host on residing on different/working blade
- Ran vmware-cmd -s register command against VMX file to register powered off VM's onto working ESX host.
- No errors after running command and VM's now appear on "working" ESX 4.1 host/blade.
Resulting issue:
I inadvertantly failed to power off 1 of the VM's prior to registering the VMX file on the new/working ESX host. The subject VM now appears as "invalid" in vCenter and will not power on (don't recall the exact error). Is there something I can do to recover the "invalid" VM?
Thanks,