• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Strange ESXi 4.1 error

X

XOR != OR

[H]F Junkie
Joined
Jun 17, 2003
Messages
11,547
I've been trying to troubleshoot this issue for the past several weeks and I'm coming up with nothing. I've got a couple esxi boxes out there with windows guests. Normally, during an updating process windows will reboot. However, every now and then in this environment the guest will simply shutdown.

I've googled around but haven't had much luck finding anything related to this, but I'm hoping someone here has run into this problem before.
 
ESXi doesn't know what your guest is doing..so he won't shut them down after a patch. I'd post over in an OS forum and see.
 
NetJunkie said:
ESXi doesn't know what your guest is doing..so he won't shut them down after a patch. I'd post over in an OS forum and see.
Click to expand...
I have a set of servers that are on physical hardware that are patched on the same schedule, no issues. None of them shutdown instead of rebooting. This is a behavior I've only seen in an ESXi environment. Further, it's not always the same servers that have the issue. That's what leads me to believe this is an ESXi issue.

Windows makes certain calls to the underlying "hardware" to initiate the reboot. I believe that this call is being interpreted incorrectly by esxi, but I'm not sure how to gather such evidence.
 
Check your HA settings, make sure your monitoring threshold isn't too low. If a bunch of boxes are rebooting at the same time, it may take a little while for them all to come back up based on disk activity and VMware might not get heartbeats from them even though they're powered on. Try setting it to disabled and see if you have the same issue.
 
ND40oz said:
Check your HA settings, make sure your monitoring threshold isn't too low. If a bunch of boxes are rebooting at the same time, it may take a little while for them all to come back up based on disk activity and VMware might not get heartbeats from them even though they're powered on. Try setting it to disabled and see if you have the same issue.
Click to expand...
This^
 
You must log in or register to reply here.
Back
Top