Monday, 16 May 2011

Creating a Portable P2V VMware Converter Machine

Scenario

You are tasked with going to a remote office location to carry out P2V conversions of a client's servers. There is no access to a VMware Virtual Centre from site, and the tools you can take are a laptop and removable storage device(s.) It is desired to get the customer up and running as quickly as possible in the hosting infrastructure after the P2Vs have been done, and original servers shut down.

A solution

With the following hardware:

64bit VT-enabled laptop (the Toshiba Tecra R10 will do the job)
4GB USB key
1TB eSATA external drive
*The Toshiba Tecra R10 also has an Intel 82567LM Gigabit Network Adapter - Gigabit Networking is a necessity (transfer rates over fast ethernet of max 750MB per minute or more realistically 250MB per minute, is far too slow for most purposes - better to plug a USB drive into the server being P2Vd)

It is possible to:

1) Install ESXi onto a 4GB USB stick, and run ESXi on the laptop
*Recommend keep ESXi on the evaluation license so can add to a vCenter on the eval license and storage vMotion imported servers across

2) The eSATA external drive can be presented as storage to the ESXi host running on the laptop
*Advantage of eSATA is that the performance is similar to a local SATA drive

3) Then the P2V is pointed to the ESXi host running on the laptop

The advantage of doing the P2V to the portable ESXi host as opposed to using the VMware Workstation option to do the P2V to a network share on removable storage, is that the images don't then need to be converted to work with vSphere when they have been uploaded to the hosting infrastructure, thus considerably saving time.

P2Vs to a locally connected USB drive or network share, not done to a VMware ESX(i) host / vCenter, either need their sparse disks converted using vmkfstools ( http://cosonok.blogspot.com/2010/08/using-vmware-vsphere-cli-to-convert.html ) or - if the provision thick option is used - need to be V2Vd to avoid getting file system corruption when later snapshot-ing the imported VM guest.


For google: Tips for VMware P2V to laptop usb network share

Wednesday, 11 May 2011

Installing HP NC365T (Intel 82580) Network Driver to VMware vSphere ESXi 4

Scenario:

Newly built VMware vSphere ESXi 4.1 host on HP ProLiant DL360 G7 hardware, fails to see the installed HP NC365T quad-port gigabit ethernet adapter

Walkthrough:

With VMware vSphere CLI (free download) already installed

1: Download the driver from VMware's website

Go to:


Or

Go to:

→ Datacenter Downloads VMware vSphere 4
→ Scroll down the webpage to Drivers & Tools

Expand Driver CDs and click on the Download button by -

VMware ESXi/ESXi 4.x Driver CD for Intel 82576 ,82580 and I350 Gigabit Ethernet Controller

- and follow the prompts to download the iso file.

2: Obtain the offline_bundle driver file from the iso

Three suggested ways to do this:

i: Use software like 7-Zip (free download) to extract file from iso (preferred method)
ii: Use software like daemon tools (free download) to mount the CD to client device
iii: Burn the iso and mount in the physical CD drive (least preferred method)

The desired file is called something like – INT-intel-lad-ddk-igb-3.0.18-offline_bundle-396986.zip
Place this in the “Program Files (x86)\VMware\VMware vSphere CLI\bin” folder

3: Put VMware host to be updated into maintenance mode

4: Use the VMware vSphere CLI installed on a client device (laptop or workstation) to install the drivers

With this command:

vihostupdate.pl --server HOST_IP_ADDRESS --username root --install --bundle NAME_OF_OFFLINE_BUNDLE

Example:


Note: If you stay connected to the ESXi host with the vSphere client you will see the Install and Check complete


5: Reboot the host

The End!


Credits: