First you need to obtain the vmdk files from the Soul Dev Team.
They are located here - > Link
Once you download everything you need, you will need to copy the unlocker files to the ESXi box.
Navigate to OS X 10.8 Mountain Lion Retail VMware Image\VMware Unlocker - Mac OS X Guest\VMware 8.x Series\VMware ESXi Unlocker
You need to copy the Unlocker.ESXi and the install.sh.
If you don't already have SSH enabled here is how you do it -> Link
Next SCP the files (replace x.x.x.x with your IP)
If you are using OS X
scp -v Unlocker.ESXi root@x.x.x.x:/tmp
scp -v install.sh root@x.x.x.x:/tmp
If you are using Windows I suggest you use putty(Link)
C:\Program Files (x86)\PuTTY>pscp.exe "Unlocker.ESXi" root@x.x.x.x:/tmp
Now SSH to the ESXi box.
Type: cd /tmp -> Enter
Type chmod 777 * -> Enter
Type ./install.sh -> Enter
Reboot
Run VMware converter (Link)
Boot up the vm and go through the installer
You need to remove the network adapter and add another one. This time it will pull a dhcp address.
You need to install the update fixer and then apply the latest patches. Now at this point vmware tools will install correctly.
Sources: Link
This is a places that post walk throughs, my thoughts, notes, and writes-ups. Although they worked for me, ***USE AT YOUR OWN RISK***!
Showing posts with label Vmware Converter. Show all posts
Showing posts with label Vmware Converter. Show all posts
Thursday, May 9, 2013
Thursday, March 14, 2013
VMware vCenter Converter Standalone: 400 Bad Request
I was trying to use vCenter Converter and kept getting this error when trying to log in. I then realized I was doing it wrong. I didn't need to login. This worked for me, but it may or may not work for you.
Launch vCenter Converter Standalone -> select "Connect to a Local Server"
Click "Convert Machine" -> Select your source
Click Next - > Select "VMware Infrastructure Virtual Machine" -> Browse to your file
Enter your ESX/ESXi server details -> Type in your username/password (Remember if your using active directory authentication its domain\username)
Click Next -> Type the name that you want it to show up as in vSphere -> Click Next
Choose your destination (which pool) -> Click Next
Edit any info of the Virtual Machine if you need to -> Click Next -> Verify everything -> Click Finish
Launch vCenter Converter Standalone -> select "Connect to a Local Server"
Click "Convert Machine" -> Select your source
Click Next - > Select "VMware Infrastructure Virtual Machine" -> Browse to your file
Enter your ESX/ESXi server details -> Type in your username/password (Remember if your using active directory authentication its domain\username)
Click Next -> Type the name that you want it to show up as in vSphere -> Click Next
Choose your destination (which pool) -> Click Next
Edit any info of the Virtual Machine if you need to -> Click Next -> Verify everything -> Click Finish
Labels:
VMware,
Vmware Converter
Monday, March 12, 2012
Module DevicePowerOn power on failed when starting a VM in ESX
I was getting an error message like this:
Module DevicePowerOn power on failed. Unable to create virtual SCSI device for scsi0:0,
I later found out that the image was being used in VMWare Player and needed to be converted first. In this instance you need to download VMWare Converter (Link) and connect to your ESX box. It will convert and then transfer it for you.
VMWare has another way of doing it. Its listed as the source below.
Source: Link
Module DevicePowerOn power on failed. Unable to create virtual SCSI device for scsi0:0,
I later found out that the image was being used in VMWare Player and needed to be converted first. In this instance you need to download VMWare Converter (Link) and connect to your ESX box. It will convert and then transfer it for you.
VMWare has another way of doing it. Its listed as the source below.
Source: Link
Labels:
ESXi,
VMware,
Vmware Converter,
Vmware Player,
Windows
Subscribe to:
Posts (Atom)