Mount CDROM in ESXi Shell 5.0,5.1,5.5

I needed to mount a CDROM drive in order to grab older NIC drivers for my Motherboard. It has 2 Intel 82573L Gigabit Ethernet Controllers onboard. VMware stopped support for these as of ESXi 5.0. This requires using esxcli software install vib commands in order to roll back the VMware driver bootbank to an older VIB for the Intel e1000e NIC driver. Given that my system has two onboard NICs and no room for expansion, I cannot mount anything over the network to grab the drivers. A chicken and egg scenario. CDROM it is!

This worked for me on ESXi 5.5. I remember doing it in the past with 5.1 as well.

To find the device reference of your CDROM:

esxcfg-mpath -l

Example output:

ide.vmhba0-ide.0:0-mpx.vmhba0:C0:T0:L0
Runtime Name: vmhba0:C0:T0:L0
Device: mpx.vmhba0:C0:T0:L0
Device Display Name: Local TEAC CD-ROM (mpx.vmhba0:C0:T0:L0)
Adapter: vmhba0 Channel: 0 Target: 0 LUN: 0
Adapter Identifier: ide.vmhba0
Target Identifier: ide.0:0
Plugin: NMP
State: active
Transport: ide

Load the iso9660 module with this command:

vmkload_mod iso9660

Mount the CDROM using the device determined earlier with esxcfg-mpath -l:

# /sbin/vsish -e set /vmkModules/iso9660/mount mpx.vmhba0:C0:T0:L0

The CDROM will be mounted under /vmfs/volumes/ [CDROM Label] /

Original Article : VMware Communities 1692327     and http://www.justinedmands.com/?q=node/45

VMWare ESX Source Code Leaked On The Internet

Another big source code leak, this time VMWare ESX, software which I’m sure most of the readers here have used at some point (I know I have). There was a time back in 2006 when VMWare Rootkits seemed like they might be the next big thing, but nothing much ever came out of it. VMware [...] The post VMWare ESX Source Code Leaked On The...

Read the full post at darknet.org.uk

ESXi 3.5 and SSH

vmware

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.

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.

Using vimsh

egg

List information about a VM
vimsh -n -e “vmsvc/getallvms”

See a summary of the current host configuration
vimsh -n -e “hostsvc/hostsummary”

Enter maintence mode
vimsh -n -e /hostsvc/maintenance_mode_enter

Exit maintence mode
vimsh -n -e /hostsvc/maintenance_mode_exit