VMware virtual machine appears to be effecting the host as well.

I am experiencing an strange issue in which a resident VM seems to be crashing the whole host at least once a day.  This VM is the only VM on any host at any given time.  The symptoms are, the VM will become unresponsive, then eventually the host will as well.  If you issue a restart command to the host from Vcenter, nothing happens.  If you do the same from the console in front of the physical host, it still does not restart.  I have to force shut down the computer.  This behavior continues to occur when I move the VM to another host and data store.

This VM was working fine for the longest time, but it now starting to have these issues.  

Any ideas as to what maybe causing this behavior or where to start looking?
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
details of the VM please, e.g. it's specifications, also Host specifications, and build of ESXi.

we can then start looking at configurations.

e.g. if I set a VM to 32GB, 8 vCPU with a host of 32GB, and 8 cores, I can also cause host issues! Easily done!
CnicNVAuthor Commented:
The VM is a Windows 7 Pro 64bit OS.  It is setup with 2 VCPUs ,14 GB of RAM and a 200 GB VMDK.  It is running on VM version 8, with VM Tools 8384 (I had upgraded this to the newest version 5.5u3 supported).  

It is the only VM on this host.  The Host is a Dell Vostro 430, and which has the following specs.  An i7 8 core CPU, 16 GB of RAM and a single 500 GB 7200RPM SATA data store.

Note that before it was on a host with the exact same configuration, with the exception that it has two separate data stores with the same capacity and specs.  

This VM never had any issues before.  It wasn't until I upgraded the hosts version of ESXI from 5.1 to 5.5u3 (lol I also opened them up and blasted them out with compress air).  Note, that I have done this upgrade to yet another host with the exact same specs (a Vostro) and the resident VMs on this host, both windows server 2008 R2 SP1 have not had any issues.  In this case both of these VMs share the same 500 GB data store and combined use 13 GB of the host 16 GB or RAM, and it has an i5 instead of an i7.

Last week I was looking at the log browser, the VMKernel and VMKWarning ones for SMART errors and the only ones I was seeing were temperature threshold ones.  Something like threshold 34 (which is supposed to be the worst).  But I noticed other (non critical) hosts which were running fine were giving the same warnings but with numbers in the 100 range or 20s, so I thought, maybe this is a non issue (or servers "crying wolf").  

So this morning.  I reboot shut down the frozen VM and I get the following attached error.  Which is new BTW, I had not seen this before when I followed the same process last week...

LOL, I have no idea. But I am guessing this means the other hosts that are reporting the same SMART temp thresholds will fail soon?

Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Well the host is not supported for VMware vSphere 5.5 U3, it's not on the HCL.

You have a single SATA disk, and datastore, so therefore IOPS will be very low, and performance will be shocking.

13GB out of 16GB RAM is very close, to causing performance issues.

Multiple issues, caused with a disk with errors, will cause the VM/Host to stop.

Your disks are failing, I'm not sure why you are using ESXi, for a single Windows VM, you would be better using the Windows on bare metal, at least then it can use all of the resources.

So if you host has failing, disks, your VMs will not be very happy or respond well.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
CnicNVAuthor Commented:
Seems reasonable.  

I ended up restoring the VM from a backup to the other host that it used to reside on and it has not had any stability issues for a couple of days now.  To test the host that it was just on, I migrated a different VM to it and it too has been running fine for the past couple of days.  So I have no idea, but one of our developers has reduced the work load on the original problem VM so its probably related to that and the resource over provisioning of that VM.

Thanks for your help.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.