VMware

This Question is Possibly Answered

1 "correct" answer available (10 pts) 2 "helpful" answers available (6 pts)
1 2 3 Previous Next 31 Replies Last post: Nov 5, 2009 1:09 AM by J1mbo  

new ESXi install: random lockups / hangs / freezing posted: Oct 20, 2009 7:49 AM

Click to view some guy's profile Enthusiast 32 posts since
Oct 13, 2007
All,

I recently moved to ESXi in hope of curing a long time freeze-up issue with Server 2. Alas, the problem is worse with ESXi despite brand new hardware. I'm hard-rebooting the host (with the reset button) twice a day now instead of every week or two on Server 2.


My hardware config:


  • Gigabyte EP45T-DS3R mainboard with the Intel ICH10R chipset

  • genuine Intel e1000 nic: PRO/1000 MT Dual Port (I've disabled the on-board ethernet controllers)
  • Core 2 Duo Quad Core
  • 8GB of RAM

Despite the absence of the Core 2 Duo line from the HCL, I haven't found any posts yet that would lead me to believe I have a hardware problem. I'm wondering where to look next.


I'm running 2 Gentoo guests, 2 Centos guests, 1 Ubuntu guests, 2 XP guests and 1 W2K guest. Aside from the Ubuntu guest, all of them were converted over from bare metal (vastly differing hardware) to VMWare Server 1.0. They were then run under Server 2 for a time before being converted to my new ESXi host last week. None of the guest machines see very high utilization, they are mostly idle. The performance screens in VCenter indicate I'm not using much of the available resources.


Where do I go from here? Should I replace the hardware? Is there any chance one of the guests is using an op-code that the hypervisor is choking on? If so, how do I tell which guest is the culprit?


Any help would be appreciated...I'm at my wit's end.

Click to view DSTAVERT's profile Virtuoso 2,418 posts since
Nov 30, 2003
The first thing would be to run memtest. Download from memtest.org.

Power supply issues?

Scan through logs if you can? Move the location of logs so that they are retained and easily retrieved. Create a directory in the datastore and use the VI client to point logs to theat directory.
Click to view DSTAVERT's profile Virtuoso 2,418 posts since
Nov 30, 2003
I am referring to the power supply.
The VM logs are already stored in the datastore. The HOST logs are stored in /var/logs which can't be accessed directly except from the unsupported console. You can use the VMA appliance to set up a scheduled retrieval. You can set up a remote syslog server. Or, you can move the location for logs to anywhere the host has access. If you create a folder in the datastore you can use the VI client to relocate the log storage to that folder. It makes it easy to download logs and in cases where the /var/log/ folder is cleared after a reboot you still have something to refer to. In the VI client under Configuration / Software /Advanced Settings Add the path to the syslog settings.
Click to view Mithris's profile Novice 6 posts since
Oct 21, 2009
Moved to new thread...
Click to view DSTAVERT's profile Virtuoso 2,418 posts since
Nov 30, 2003
Definitely run memtest just to rule out memory as an issue.
Click to view DSTAVERT's profile Virtuoso 2,418 posts since
Nov 30, 2003
Mithris
You need to create your own post. Copy what you wrote and start a new one. It will be confusing to both parties if the answers are mixed.
Click to view Rumple's profile Master 1,264 posts since
Jan 6, 2005
You are def hitting a hardware issue if you had windows installed and locked up and now esx and its locking up.

Run the manufactors diagnostics for hard drives

Check for new BIOS

Reset BIOS to failsafe defaults and then optimized and disable all hard like com, parallel, audio, etc that you can to free up IRQ's.

If you have another sata controller to temporarily try you could see if its the Intel storage controller causing the issues. I've had my system screwup because my array controller was knackered...

See if there is a firmware for that controller.

Click to view J1mbo's profile Expert 565 posts since
May 20, 2009
Also assuming it's a server of some description, check through the system BIOS for the IPMI and any other diagnostic event logs - may show something helpful.


Please award points to any useful answer.

Click to view Mithris's profile Novice 6 posts since
Oct 21, 2009
I suspect the motherboard. I did a quick search and noticed several people having issues with that mobo and the ICH10/P45 Express chipset.
http://communities.vmware.com/message/1038234;jsessionid=47B7186CDAEB353AF7832220AE6442E8

To clarify, it is the hypervisor itself that is locking up, not just VMs correct?

VMware Developer

SDKs, APIs, Videos, Learn and much more in the Developer community.

Learn More

Developer Sample Code

Increase your developer productivity with VMware API sample code.

Learn More

VMworld Sessions & Labs

Online access to the latest VMworld Sessions & Labs and online services.

Learn more

Purchase PSO Credits Online

Purchase credits to redeem training and consulting services online.

Buy Now

Community Hardware Software

View reported configurations or report your own.

Learn More

VMware vSphere

Come witness the next giant leap in virtualization.

Register Today

Communities