Problem with trial, importing Fusion, and getting support...

I am looking at switching from Fusion but want to try out the new version 5 first, even do some benchmarks for myself. The problem is that I get a Transporter error of "This virtual hard disk cannot be processed because something is wrong with it. Please contact Parallels support team for assistance.".

I would like to contact the support team but I am not willing to pay for a ticket to try out a product and yet there does not appear to be any other way to access the support team!

 

This error message could be caused by an inconsistency in filesystem of Fusion virtual machine.

Please, while in Fusion
1. Perform disk checking of all disks that are in the VM
2. Disk defragmentation will also help increase the probability of successful conversion

After it's done, shut down the guest gracefully and re-attempt the migration

 

Done that already and had no success. I also did a cleanup of the disk through fusion and had no success.

 

I am having the same exact issue and I am chatting with tech support at Parallels. I can't believe that I wasted $15 on the chat session. The first thing he asked me after I described my problem was..... "Have you downloaded the parallels desktop for your Mac"? I knew that I was IN TROUBLE!!!! Anyone know if the following steps provided resolved the migration issue?

 

Didn't work for me either. I am working on another solution as I type. I downloaded the transporter for windows and copied it to my guest windows xp OS. Fired up the agent and instructed transporter to migrate a computer, that being the guest OS. The migration completed and now I am copying that 24GB parallels image to my mac. When done, I will fire up parallels and point it to that file to see if it opens up correctly. I will keep you updated on the progress.

Scott

 

Interesting approach Scott. How did it go?

I wish Fusion would support Open Virtualization Format (OVF) and Parallels could import that. If they did though then it would make evaluating VirtualBox to easy and then we might all run off to an open source solution.

 

Scott,

I might have a way about this. VMWare has a converter for exporting.

http://downloads.vmware.com/d/details/converter401/dGhiZHRwaGJ0QGg=

From there Parallels might be able to do its thing.

 

OK, I am now up and running in parallels!!! Here is what I did to resolve this issue.

1. I fired up fusion and set my network settings to bridge mode instead of NAT. This way it will have it's own separate IP addy from my host (Mac) machine.

2. I downloaded the NEW transporter for windows, which includes transporter agent and opened it up on the VM

3. I opened up transporter on the Mac and I selected the option to import a "physical computer"

4. It automatically located the PC's (fusion vm) IP addy, I selected it, and hit next.

5. It started to do the import conversion on over to the parallels folder located in ~/Documents/Parallels

It took about an hour (depends on the size of your existing vm image) and I have been rocking ever since!

Let me know how things go for you!!!

 

I am up and running too...

Using the approach of creating a new VM in Fusion that accesses the existing Virtual Hard Drive from the problematic VM (this took about 2 minutes to create) I then used Parallels Transporter to access the new Fusion VM and do the conversion. Very simple and the only real performance hit was with Transporters time. The existing machine had a 30Gb hard drive file so it took while.

Now I am going to run the benchmarks that I ran on Fusion 3 and see what the results are for a comparison.

As a note, I am also going to try some benchmarks on VirtualBox (Open source VM) to see how it does.

 

swich2mac: did you download the transporter for v4 or v5? I'm looking for the v4 link but the download on their site only has v5 available.

 

Success via new Fusion VM

SchneiderIS: Thanks heaps mate!

I've had success with your method by creating a fresh VM within Fusion 3. What I learned...

My complication was two virtual disks. Creating a new Fusion VM with both drives didn't work, Transporter gave the same useless error.

So I created a fresh VM with only the C drive. Transporter accepted that.

Next I ran Transporter to migrate the E drive. Transporter accepted that.

Then I started Parallels, added the E drive, then booted the VM. Success!

 

SchneiderIS, swich2mac
please generate problem reports and tell me it's numbers.