Thursday, May 19, 2011

ESX/ESXi 4.x Unable to connect to MKS, error connecting /bin/vmx process

Issue: Unable to open the console for the VM and you are also not able to ping the VM in many cases.
Resolution: Create a new VM with custom option with the same configuration but without any virtual disks. Attach the existing the disks of the problematic VM in the proper order.
Note: Make sure the problematic VM is powered off.
Issue mostly seems to be with the Linux VMs.
Why? :- vmx file is corrupt.
Refer:- http://communities.vmware.com/message/1424538


Monday, May 16, 2011

ESX/ESXi 4.1 Unable to install windows 2008 r2 sp1 since the windows is unable to find the installation disk (missing drivers)

Issue: When tried to install the windows 2008 r2 sp1 on an ESX/ESXi 4.x host it failed to find/see the disk due since it did not have the proper drivers to see the VMware virtual disks.
note: the scsi adapter selected was lsi sas controller. Tried to inject the vmscsi drivers from the floppy image but they were not recognized as the proper drivers. [http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1005208]

Resolution: There are 2 different windows 2008 R2 SP1 images of different size but with the same build number. The correct working iso is of 3.02 gb and the one which does not work is of 2.6gb.
working iso from msdn/technet:
File Name: en_windows_server_2008_r2_standard_enterprise_datacenter_and_web_with_sp1_x64_dvd_617601.iso
Date Published (UTC): 2/16/2011 8:43:27 AM     Last Updated (UTC): 2/23/2011 11:46:34 AM
SHA1: D3FD7BF85EE1D5BDD72DE5B2C69A7B470733CD0A     ISO/CRC: 6D1E1430

Tuesday, May 10, 2011

VMs unable to ping the host (ESXi/ESX 4.1) after upgrading from 4.0 U1

Background: The upgrade of the esxi 4.ou1 to esxi 4.1 has been made on 2 hosts of the cluster and after that some VMs in the host esxi 4.1 cannot ping the host and some VMs in the same host can ping the host but otherwise every other network communication between VMs to VMs and hosts to hosts is proper.
What worked : Remove the nics from the VM in the VM settings and add them back after a reboot.
What did not work: updating the proper ip information in /etc/hosts and /etc/sysconfig/network
restarting the management agents.

Wednesday, May 4, 2011

A general system error occurred: failed to start migration pre-copy. Error 0xbad004b. Connection reset by peer

Issue: The vmotino migration of a powered on VM fails at 10% with the error "
a general system error occurred failed to start migration pre-copy. Error 0xbad004b. Connection reset by peer
"
Resolution : Change the ip address of the vmotion port of the source and/or the destination host.
Reason: The ip address assigned to the source or the destination vMotion port is being used by another client/server/host in the network [OR] The same ip address has been assigned to the vmotion port of the host and another machine/server/host.