Puppet, did however offer an OVF version of the same VM, however I was unable to import this VM into VCenter. Each time I tried I was greeted by an error that stated that the OVF would only work on Virtual Box. This was not an error that I had run into before, so I decided not to attempt to troubleshoot.
Back to the VMware issue. Note that I did not receive an error when importing the VM into Vcenter, rather I received a fatal error when attempting to start the VM. The specific error that I received is below.
Failed to open disk scsi0:0: Unsupported and/or invalid disk type 7. Did you forget to import the disk first?
The reason for this error, well virtual disks are not compatible between ESXi and hosted products like VMware Workstation or Vmware Player. However you can work around the issue by converting the disk into the appropriate format.
Below are the steps that you need to follow.
First create a directory on your remote Datastore to house the new virtual disk, and virtual machine that you will create. Then upload the vmdk disk file to a VCenter Datastore. Ignore the vmx configuration file and any other file expanded during the unzip file. You will not need these files.
-rw——- 1 root root 3972268032 Mar 1 03:07 disk.vmdk
Now convert the disk to the proper format using vmkfstools as shown below. The original name of the vmdk is disk.vmdk, however we will need to change the name of the file as part of the format process.
# vmkfstools -i disk.vmdk disk1.vmdk
Destination disk format: Thin
Cloning disk ‘disk1.vmdk’…
Clone: 100% done.
Now create a new Virtual machine using the custom wizard. Note that this VM based on 32bit Centos 6, so make sure that you choose this option from the drop down.
Note that you are not going to create a new disk for this virtual machine, rather you are going to choose “use existing disk” and point your VM to the disk file created in the step above.
Once you have competed the wizard, the VM will be created… you should not run into any errors. Next you need to power on the VM which should not give you any issues either. Open the console of the newly created VM and grab the DHCP assigned ip address of the system.
At this point, you should have no trouble ssh’ing into the new vm and running through the labs.