Knowledge Base

When using VMware ESXi 4.1, you may experience one or more of these symptoms:

• Unable to connect to the MKS
• Unable to power on virtual machines
• Powering on virtual machines reports some virtual machines in an invalid state
• Power state of the virtual machine is reported incorrectly in the vCenter Server/ESX inventory
• If you restart hostd, virtual machines that were previously not in an invalid state may appear as invalid
• When a virtual machine is in an invalid state, you see these errors:
  
  vmx| VmdbPipeStreamsOvlError: write failed, draining reads
  vmx| VmdbPipeStreamsOvlError: Couldn't initiate write
  vmx| Redirecting stdin/stdout/stderr to /dev/null.
  vmx| SOCKET 1 (91) send error 12: Cannot allocate memory
  vmx| Vix: [177936 mainDispatch.c:2472]: VMAutomation: Connection Error (1) on connection 0.
  vmx| SOCKET 1 (91) send error 12: Cannot allocate memory -> not able to create socket,no mem available.
  mks| SOCKET 2 (92) recv error 104: Connection reset by peer
  mks| SOCKET 2 (92) destroying VNC backend on socket error: 1
  
  
• The messages log contains entries similar to:
  
  
  • sfcb-CIMXML-Processor[9857708]: SendMsg sending to 7 9857708-9 Bad file descriptor
    sfcb-CIMXML-Processor[9857708]: spSendMsg sending to 7 9857708-9 Bad file descriptor
    sfcb-CIMXML-Processor[9857708]: --- spSendReq/spSendMsg failed to send on 7 (-1)
    root: sfcbd-watchdog:Restarting SFCB! Log a bug!!!
    root: sfcbd-watchdog:stopping sfcbd
    root: sfcbd Stopping sfcbd
    root: sfcbd-watchdog:starting sfcbd
    root: sfcbd Starting sfcbd
    sfcb-sfcb[9849840]: --- Using /etc/sfcb/sfcb.cfg
    
    
  • FoundryVMDirectlyOpenSocketToVMX: Failed to create socket pair.
    
    
• The hostd logs may report this error when you try to power on the virtual machine:
  
  Cannot connect to /var/run/vmware/root_0/1299674323658606_59831734/testAutomation-fd: File not found
  
  
• vMotion fails intermittently at a random percentage
• Connecting to the remote console via the vSphere Client fails with the error:
  
  Unable to connect to the MKS: There is no VMware process running for config file
  
  
• Unable to retrieve any files from the datastore via Datastore Browser
• Copying a file using the datastore browser gives the error:
  
  Failed to log into NFC server
  
  
• The vm-support diagnostic information gathering utility is unresponsive
• The Health Status tab may not load correctly
• Powering on a virtual machine fails at 95% with the error:
  
  A general system error occurred: Cannot connect to the virtual machine