VMware: Install Intel ET 82575 and 82576 drivers on ESX 4 vSphere

Update: Drivers are included in vSphere 4.1.

Download the ISO with drivers from HERE.

Burn to a CD and insert in the drive. Logon to the console as root and mount:
mount /dev/cdrom /mnt
Browse to /mnt and find the file “INT-intel-lad-ddk-igb-”

Install the driver:
esxupdate --bundle=INT-intel-lad-ddk-igb- update

VMware – Linux: OS cannot mount /dev/sd* after a virtual machine is converted – Waiting for device /dev/sd* to appear… not found – fall back

This happened when I created a SLES 11 VM with VMware Workstation and then moved to to ESX for production. Problem was that VMware Workstation used LSILogic SCSI drives to emulate my disks, but for some reason it wasn’t made clear to ESX by VMware Converter during conversion.

To fix this browse to your datastore and download your guest’s configuration file <vmname>.vmx to your desktop (or use your root access and open it in vi through ssh). Open it with a text editor and add the following line above your SCSI devices:
scsi0.virtualDev = "lsilogic"

So the whole SCSI device section should look like this:
scsi0.present = "true"
scsi0.sharedBus = "none"
scsi0.virtualDev = "lsilogic"
scsi0:0.present = "true"
scsi0:0.fileName = "disk1.vmdk"
scsi0:0.deviceType = "scsi-hardDisk"
scsi0:1.present = "true"
scsi0:1.fileName = "disk2.vmdk"
scsi0:1.deviceType = "scsi-hardDisk"

Copy the config back to your datastore and start guest OS. You will be asked to confirm changes during post – answer yes to changes.

Disclaimer: Make sure you have a backup before making any change.

Linux: Cannot turn on a virtual machine after unclean shutdown – failed to lock the file error VMware Server

I don’t recall the exact error message, but sometime after an unclean shutdown your virtual machines will not start with an error that contains “unable to unlock file”. To resolve the issue simply navigate to the directory where your virtual machine resides, and delete all files with .WRITELOCK and .lck extension.That should remove the lock and make your VM’s accessible. If that didn’t help, go ahead and delete all files EXCEPT .vmdk AND .vmx EXTENSIONS. That should definitely do the trick.

You can actually delete the .vmx files as well but in order to have VMware recreate them you will have to start the “new virtual machine wizard” and use the .vmdk as your disk file. Instead of creating a disk you use an existing.

VMware ESX and ESXi – tips and tricks

To clear connection history in VIC go to regedit and delete the line “RecentConnections” from HKEY_CURRENT_USER\Software\VMware\VMware Infrastructure Client\Preferences.

To allow root access to logon through ssh in ESX:

Logon to console as root
Edit sshd_config: nano /etc/ssh/sshd_config and change “PermitRootLogin” from “no” to “yes”
Restart ssh: service sshd restart

To allow root access to logon through ssh in ESXi:

Open console and press Alt+F1
Type "unsupported" and enter root password to log on
Open inetd.conf in vi: vi /etc/inetd.conf
Find the line that starts with #ssh, uncomment, save and close the file, and then restart services on your ESXi server: /sbin/services.sh restart

To allow non-root access to logon through ssh in ESXi:

Log on to console: press Alt-F1 (or through root ssh)
Edit inetd.conf: vi /etc/inetd.conf
Find this line: "ssh stream tcp nowait root /sbin/dropbearmulti dropbear ++min=0,swap,group=shell -i" and add -w to the end. Save and close the file.
Create the new users and home directory: useradd -d /home/username -P username