Can't convert existing image

[balexandre]

My company gave me an existing VM disk that it's used for their Acedemy.

I wanto to have that in my mac using VMWare Fusion, but something is wrong.

I Start by create a new Image, selected to use an existing Virtual Disk, and selected where to put the image selecting the first option to copy content, it did copy all but at the end I got just a disabled view of the UI.

And I can't do anything on this screen... What can I do?

This is the VM of my company:

And I do this:

1 - http://cl.ly/7u2w

2 - http://cl.ly/7uqm

3 - http://cl.ly/7uzv

but after it do the entire copy, I always get this:

http://cl.ly/7vli

😞

What am I doing wrong? What can I do to convert the existing image into a VMWare image? Thank you.

---

Using:

- MacBook Pro pre-unibody with OSX 10.6.8: http://cl.ly/7uqB

- Fusion 3.1.3: http://cl.ly/7w2S

[WoodyZ]

What product was the source Virtual Machine originally created with?  If it is a VMware Virtual Machine then all you need to do it execute the .vmx configuration file and you should not need to create another Virtual Machine in order to use it.

Other then that if you want help with the newly create Virtual Machine that is giving you an error then to help figure out what is what the best way to provide comprehensive diagnostic information is to use the "Collect Support Information" command from the VMware Fusion (menu bar) > Help > Collect Support Information and then attach the .tgz file it created on your Desktop to a reply post.

[balexandre]

I can't open it. The File > Open, gives me no file that I can open:

It's a VMware image, you can see the VMware Player in the disk root to be installed.

P.S. File attached

[WoodyZ · Accepted solution]

I don't know why, there was no information on the Virtual Machine in the .tgz file however in the vmware-vmfusion.log it said "VM creation failed: There is no space left on the device" so have a look at that.

Also was there a .vmx configuration file with the original Virtual Machine?

Also pictures of the files without seeing the file size and date/time stamp along with their names would be much more helpfully when trying to troubleshoot.

[balexandre]

I think I got what was wrong ...

It says that the image is 36Gb (in the VMware screen) but I was using a 30Gb partition, because I was using the file lenght the VM size (26Gb).

Here is the sizes:

Though it is weird that I can't simple open the VMware image directly and had to go with creating a new one using the .vmdk (VM DisK file).

Thank you for the prompt help!

[WoodyZ]

Though it is weird that I can't simple open the VMware image directly and had to go with creating a new one using the .vmdk (VM DisK file).

You need to have the .vmx configuration file in order to open a .vmdk as a running Virtual Machine.

Based on the size of the "Windows 7 x32-cl3.vmdk" and your choice to "Make a separate copy of the virtual disk" and only having 2.76 GB free on the "Snow Leopard on SSD" volume or 11.62 GB free on the "Snow Leopard on HDD" volume I'd have to say that is why the vmware-vmfusion.log said "VM creation failed: There is no space left on the device".