VMWare: Update Standalone ESXi 5.0 to 5.1 Using a Depot Zip File

1) Download the depot file; at the time of writing the latest update is as follows and can be found here.

VMware-ESXi-5.1.0-799733-depot.zip
File size:298M
File type: zip
Release Date:2012-09-10
Build Number:799733

2) Upload the file to your datastore, in this example the file was uploaded to  “myDatastore”

3) Enable SSH on your ESXi host and on the command line, enter the following, using an absolute path to your depot file:

~ # esxcli software profile install -d /vmfs/volumes/myDatastore/VMware-ESXi-5.1.0-799733-depot.zip -p ESXi-5.1.0-799733-standard
 

4) Reboot, done!

VMWare: Enable SSH Daemon on ESXi 3.5

Taken from the vm-help.com website:

ESXi 3.5 does ship with the ability to run SSH, but this is disabled by default (and is not supported). If you just need to access the console of ESXi, then you only need to perform steps 1 – 3.

1) At the console of the ESXi host, press ALT-F1 to access the console window.
2) Enter unsupported in the console and then press Enter. You will not see the text you type in.
3) If you typed in unsupported correctly, you will see the Tech Support Mode warning and a password prompt. Enter the password for the root login.
4) You should then see the prompt of ~ #. Edit the file inetd.conf (enter the command vi /etc/inetd.conf).
5) Find the line that begins with #ssh and remove the #. Then save the file. If you’re new to using vi, then move the cursor down to #ssh line and then press the Insert key. Move the cursor over one space and then hit backspace to delete the #. Then press ESC and type in :wq to save the file and exit vi. If you make a mistake, you can press the ESC key and then type it :q! to quit vi without saving the file.
6) Once you’ve closed the vi editor, run the command /sbin/services.sh restart to restart the management services. You’ll now be able to connect to the ESXi host with a SSH client.

Tip – with some applications like WinSCP, the default encryption cipher used is AES. If you change that to Blowfish you will likely see significantly faster transfers.

Update for ESXi 3.5 Update 2 – With Update 2 the service.sh command no longer restarts the inetd process which enables SSH access. You can either restart your host or run ps | grep inetd to determine the process ID for the inetd process. The output of the command will be something like 1299 1299 busybox      inetd, and the process ID is 1299. Then run kill -HUP <process_id> (kill -HUP 1299 in this example) and you’ll then be able to access the host via SSH.

You can also download an oem.tgz file which will enable SSH (and FTP). Copy the file to a datastore with the VI client and then to bootbank with the command cp /vmfs/volumes/<datastore>/oem.tgz /bootbank/oem.tgz and then reboot.

Windows: Error: There are no un-bridged host network adapters

After installing VMWare Workstation on a new machine I came across the above error which I’d never seen before – there were no currently-bridged adapters available to bind my virtual network to.

I believe the trigger was disabling the 2 automatically created virtual network adapters before I’d actually opened up a VM. The long and short of it os that the bridging kernel driver is not running, probably due to the fact that the vmware bridge protocol is not installed on the physical network adapter(s).

So:

  • Click on your network connections and choose “Open Network and Sharing Center”

Open Network and Sharing Center

  • Open the properties for your NIC and check whether youhave the VMWare Bridge protocol installed

          Click on the properties button . Is the bridge protocol installed?

  • If not, add the service and choose “VMware ridge Protocol” from the next dialogue box. If there are no services to install then it is likely that your install is corrupted and a reinstallation would be beneficial.

 

 

 

 

 

 

 

 

 

  • If you have just added the bridging protocol OR if you already had it installed but you couldn’t see bridging adapters underyour virtual network preferences, starting the vmnet bridging driver is the next step. Open a command window (if using Vista or 7 then you need to open a command window with administrator privileges) and type “net start vmnetbridge”:

Start the vmnetbridge kernel driver