VMware Cloud Community
Tomek24VMWARE
Contributor
Contributor

vSphere Update 2 - VM power off/restart faild

Hi All,

I'm testing new Update 2 on ESXi, and vCenter 4 Update 2

When VM have very high load

vcpu and memory on VM then I can't power off or restart VM. Then VM stop

responding.

I have Server R710 2x Intel X5680 3,33 Ghz 96 GB RAM.

VM: Debian Lenny 5.0.4 with stress sofrware

I'm trying power off or reboot VM in vCenter 4 U2 on ESXi 4 U2.

Result:

VM couldn't stop and I can't killing process in console RCLI

Trick & Tips from <!-- m -->[http://kb.vmware.com/kb/1014165]

Not

working.

Any sugestion?

When vSphere Client is directly connect to ESXi or vCenter result is

this same.

I Think this is bug in Hypervisor, because I can't

kill process on ESXi.

Tom

0 Kudos
4 Replies
Tomek24VMWARE
Contributor
Contributor

I testing this case on vSphere 4 Update 1 and I have this same results VM can't power off, progress stop on 95%

In console:

~ # ps ax|grep v0

46065 vmm0:v047

46066 vmm1:v047

46068 vmm0:v046

46069 vmm1:v046

46083 46064 mks:v047 /bin/vmx

46084 46064 vcpu-0:v047 /bin/vmx

46087 46064 vcpu-1:v047 /bin/vmx

46093 46067 mks:v046 /bin/vmx

46094 46067 vcpu-0:v046 /bin/vmx

46095 46067 vcpu-1:v046 /bin/vmx

46607 vmm0:v048

46608 vmm1:v048

46609 46606 mks:v048 /bin/vmx

46610 46606 vcpu-0:v048 /bin/vmx

46611 46606 vcpu-1:v048 /bin/vmx

47115 vmm0:v045

47116 vmm1:v045

47124 47114 mks:v045 /bin/vmx

47125 47114 vcpu-0:v045 /bin/vmx

47126 47114 vcpu-1:v045 /bin/vmx

47129 vmm0:v044

47130 vmm1:v044

47164 vmm0:v043

47165 vmm1:v043

47271 vmm0:v042

47272 vmm1:v042

47278 vmm0:v041

47279 vmm1:v041

47285 vmm0:v040

47286 vmm1:v040

47294 vmm0:v039

47295 vmm1:v039

47296 47293 mks:v039 /bin/vmx

47298 47293 vcpu-0:v039 /bin/vmx

47299 47293 vcpu-1:v039 /bin/vmx

47302 vmm0:v038

47303 vmm1:v038

47304 47301 mks:v038 /bin/vmx

47305 47301 vcpu-0:v038 /bin/vmx

47307 47301 vcpu-1:v038 /bin/vmx

47354 vmm0:v037

47355 vmm1:v037

47356 47353 mks:v037 /bin/vmx

47357 47353 vcpu-0:v037 /bin/vmx

47358 47353 vcpu-1:v037 /bin/vmx

47361 vmm0:v036

47362 vmm1:v036

47363 47360 mks:v036 /bin/vmx

47364 47360 vcpu-0:v036 /bin/vmx

47365 47360 vcpu-1:v036 /bin/vmx

47368 vmm0:v035

47369 vmm1:v035

47375 vmm0:v034

47376 vmm1:v034

47599 vmm0:v020

47606 47538 mks:v020 /bin/vmx

47607 47538 vcpu-0:v020 /bin/vmx

47622 vmm0:v019

47623 47621 mks:v019 /bin/vmx

47624 47621 vcpu-0:v019 /bin/vmx

47627 vmm0:v018

47628 47626 mks:v018 /bin/vmx

47629 47626 vcpu-0:v018 /bin/vmx

47632 vmm0:v017

47633 47631 mks:v017 /bin/vmx

47634 47631 vcpu-0:v017 /bin/vmx

I can't kill proces.

Technical

support can handle anything?

Tom

0 Kudos
KamilAzmer
Hot Shot
Hot Shot

Restart your management agents will cancelled all the tasks. Power off your VM one by one.. don't did all in one time.

If still can't, you use CLI, vmware-cmd &lt;path.vmx&gt; getstate ( to see the vm status ) if still on, type vmware-cmd &lt;path.vmx&gt; stop soft ( if still on then change soft to hard ). then getstate again.

Otherwise, you can kill by PID, ps -auwx | grep vmx, type kill -INT PID and kill -9 PID

Have a nice day!

@ -- visit my blog at http://www.azmer.my -- @ virtue your mind @ KamilAzmer
0 Kudos
DSTAVERT
Immortal
Immortal

>

Technical support can handle anything?

If you have a current support contract I would contact support. From the image it looks like you have an unresponsive Host.

I would caution against killing processes on the ESXi host. It can cause the host to be unstable and potentially result in data loss.

-- David -- VMware Communities Moderator
0 Kudos
Tomek24VMWARE
Contributor
Contributor

Hi ,

I didn't have support contract because this is lab enviroment. I'm testing this software before software purchasing for production.</span>

tried these methods already. But this is not the solution to my problems and this solution not work for me.</span>


<span class="medium_text">vSphere allows to power off many virtual machines at the same time. Even as a one VM power off the effect is the same. Smiley Sad


<span class="short_text">This problem may be caused by the new X5680 processor?

<span class="medium_text">I do not know what to do, restart the host is not a solution for me. Execution command vmware-cmd or kill it is not the solution.

Please help</span>

</div>

0 Kudos