Have tried multiple times to get Mac VMware v3 VMs opened/converted/imported. - have deleted all snapshots, otherwise there is nothing weird about the VM configurations (using 2 GB files) - One of the VMs is XP SP3, the other is W7Pro. - Both failed to have their OSs identified during the conversion process. (error msg - failed to detect operating system) - Both fail to convert after selecting "yes" after the OS unrecognized error. (error msg - Failed to convert the virtual machine.) - Tried to use transporter to import VMs directly... would not enable when shown under Virtual Machines in the external device selection box, but would enable them when "show all" filter criteria is used.... When I select the VM and click open, I get a "This path does not exist." error msg. This was attempted both over the network with a shared drive and with a directly attached HD. I purchased the upgrade for v6 after being told that there would not be any problems with using VMware Mac v3 VMs... they were suppose to be finally supported... what gives? Please also tell me why my tickets priorities (yes, because I never got an ack back... the updates seem to time out) were changed to Sev4 when this is a Sev1 issue as there is no work around, tickets 1031930, 31, 32
Hi, Ron Please create a problem report. I need a log files to detect source of problem. External storage migration copies physically migrated Parallels VM's. Parallels Transporter doesn't support third party VM conversion any more. Your ticket will be performed. Please wait awhile. Thanks
I was able to use transporter via the network to transfer from the VMware VM directly to my Mac laptop running P6. I was able to import the 64 bit W7 Pro VMware VM into P6, but networking isn't working on the P6 VM... I'm still looking into that. The XP VM is still being "configured".. albeit it appears to be hung about 25% completed. It's a 56GB VM, so I will let it churn for a while longer. The P6 documentation is full of references to both importing VMware VMs directly or using transporter to do so. If you really no longer support 3rd party VMs in transporter, which I really find hard to believe. you might want to change all your marketing and technical documentation to reflect that. As soon as the XP VM "configuration" completes, I 'll generate a tech dump... which I already did, but didn't get the dump report number before it was sent off (getting an email confirmation with the number would be really helpful)... was captured during the ticket generation process and didn't append the dump report number in the process... would be nice if it did. Thx, -Ron
Problem report 6981645 for the looping during the VM configuration process after transporter based import, 1st step (of 4). I see regular waves of disk read activity with hardly any write activity...never gets past step 1.... this is on the XP Pro VM set to 4 GB RAM and 4 CPUs.
