VMware vSphere FAQ Summary (II)

Issue 1: 32-bit Windows 2003 in vSphere 4.1 Shuts Down at Irregular Intervals and Cannot Log In Again

Failure Phenomenon:

The customer’s X86 Windows 2003 VM system shuts down at irregular intervals during use. The shutdown time is uncertain, ranging from a few hours to a few days, and the shutdown moment resembles a physical machine power failure. After shutting down, the VM can be turned on again, but as soon as the account number and password are entered, it shuts down immediately, even in safe mode. Other X64 VM systems have no problems.

Solution:

After two months of painstaking efforts, ruling out causes such as network viruses, physical hardware issues, and system version incompatibilities, continuous analysis of ESXi and host logs revealed log entries similar to the following:

Sep 07 01:45:03.709: mks| SOCKET 10 (91) recv error 104: Connection reset by peer
Sep 07 01:45:03.709: mks| SOCKET 10 (91) destroying VNC backend on socket error: 1
Sep 07 03:26:42.676: vmx| Vix: [10666095 mainDispatch.c:907]: VMAutomation_PowerOff: Powering off. (VM Powering off)

Through the 400 long-term maneuvering, I discovered that this is a bug found at the end of July, by entering commands under the ESXi host:

/etc/init.d/sfcbd-watchdog stop 
chkconfig sfcbd-watchdog off
chkconfig sfcbd off

The problem was solved, but the plugin and monitoring status on the VC failed, went to the official website to download the latest patch, installed it, and everything was OK.

Issue 2: VM (Windows 2003) Mouse Moves Slowly or Is Misplaced After Maximizing Full Screen

Solution:

1. Check whether VMware Tools is installed.

2. Ensure that hardware acceleration is enabled in the system (full).

3. Adjust the virtual machine resolution to 800×600.

4. Open the console, navigate to the menu bar above > View > and remove the checkmark from “Automatic Matching Window.”

5. Verify that the graphics card driver in the virtual machine is VMware SVGA II.

In most cases, if points 1, 2, and 3 are satisfied, the problem can usually be resolved. If fulfilling all five points still doesn’t work, further action might be limited. This assumes that other factors such as high CPU or memory usage and storage read/write delays have been ruled out.

VMware vSphere sequel 2 is out and will continue to come out after that. Stay tuned !!!!

Leave a Reply

Your email address will not be published. Required fields are marked *