ESXi 4 VM hangs at 95% restart and failed to kill -9


I'm having problem with my Windows Server 2003 x86 VM, in the middle of installing IIS server, What I did is that i insert the CD into the ESXi host and then from
my VSphere client I point to use the host CD-ROM drive and it hangs,

What I've done:
1. Force restart the VM and it stuck in 95% of restart process.
2. in the SSL console of ESXi: services.sh restart
3. re-register the VM from datastore view into the VCenter (with the same name VMWS05) and it hangs with Status "In Progress", after 20+ minutes it came with the following error:
      An error occurred while communicating with the remote host.
   and the VM is not registered in the VCenter still.
4. tried to kill the process like the following but still stuck ?
      ~ # ps -ef | grep vmws05
      3854821 14064 Worker#0:Win2003x86_vmws05 /bin/vmx
      14071      vmm0:Win2003x86_vmws05
      ~ # kill -9 14071
      ash: cannot kill pid 14071: No such process
      ~ # ps -ef | grep vmws05
      3854821 14064 Worker#0:Win2003x86_vmws05 /bin/vmx
      14071      vmm0:Win2003x86_vmws05
      ~ # kill -9 14064
      ash: cannot kill pid 14064: No such process
      ~ # kill -9 3854821
      ash: cannot kill pid 3854821: No such process
      ~ # ps -ef | grep vmws05
      3854821 14064 Worker#0:Win2003x86_vmws05 /bin/vmx
      14071      vmm0:Win2003x86_vmws05

any kind of help would be greatly appreciated.

Note:
VMware ESXi 4.0.0 build 244038
VMwre VCenter Server 4.0.0 build 208111

Thanks.
LVL 1
jjozAsked:
Who is Participating?
 
jjozAuthor Commented:
sadly this is fixed by restarting the server.

editing the VMX file to release the .vswp also failed with no result as well.
0
 
jjozAuthor Commented:
the process still stuck there, i've also issued vm-support -X 14071 -d0 -w /vmfs/volumes/MD3000i_VMFS1/Win2003x86_vmws05 command but still the VM is stuck there :-|

~ # ps -auxwww | grep vmws05
ps: invalid option -- a
ps: unknown option ?
ps: invalid option -- x
ps: unknown option ?
ps: invalid option -- w
ps: unknown option ?
ps: invalid option -- w
ps: unknown option ?
ps: invalid option -- w
ps: unknown option ?
3854821 14064 Worker#0:Win2003x86_vmws05 /bin/vmx
~ # kill -hup 14064
ash: cannot kill pid 14064: No such process
~ # kill -hup 3854821
ash: cannot kill pid 3854821: No such process
~ #

Open in new window

0
 
jakethecatukCommented:
If the VM can't be killed off, then the only choice you've got is to bounce the server or restart all the services.
0
Network Scalability - Handle Complex Environments

Monitor your entire network from a single platform. Free 30 Day Trial Now!

 
jjozAuthor Commented:
Until now I'm still struggling with re-adding the VM back into the VMware VCenter 4,

I've created a custom VM with the same name and just add the VMDK into my new VM it returns: Unable to access file  since it is locked.

Any idea please ?
~ # ps -g | grep vmws05
3854821 14064 Worker#0:Win2003x86_vmws0514064 14064 /bin/vmx
14071 vmm0:Win2003x86_vmws05

~ # kill -9 14064
ash: cannot kill pid 14064: No such process

Open in new window

0
 
jjozAuthor Commented:
@Jake, I've done the services.sh restart command, the last resort is to put the host into maintenance mode.
0
 
jakethecatukCommented:
Can you edit the settings on the original VM?  If you can, disconnect the CD-ROM and see if that helps.

Failing that, it's maintenance mode jjoz (looking on the bright side, if you in NSW, the working day has passed so the effect on users should be a bit less.
0
 
S00007359Cloud Engineering OfficerCommented:
can you replicate the same issue by using an iso image os and see if the result is otherwise?
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.