Thought I'd give the retina display support a whirl on the new MBP, but when I attempt to open a .vbox file, even a basic test one created with default parameters other than a .vhd instead of .vdi, and Parallels crashes hard. Just me? Tried reinstallation, but no go.
Same issue here with an early 2011 MBP. I have an old XP .vdi that I want to use in Virtualbox, but when opening it, the whole application disappears, crashes and on reload asks me to submit a crash report. Works fine in Virtualbox and it has been shutdown correctly, not suspended.
I mean, I was using in VirtualBox. Win7 created in Parallels 7 works wonderfully on the other hand, which is good news.
My .vbox is a Windows 7 install that works perfectly under VirtualBox, but won't open in Parallels. Like I said, even a basic .vbox file crashes when I try to load it with Parallels, so it seems like when parsing the .vbox file the app barfs, irrespective of the guest OS contents. I've sent the crash log via the app, but I'm not holding my breath. I guess I'll stick with Virtualbox for now, especially since my only reason for switching back to Parallels was to try the retina support, which apparently is still iffy. It's nice to have choices. Thanks for the reply.
I'm having the same issue with VMware Fusion and VMware Workstation VMs. When I try to open them, the converter should start, but instead Parallels Desktop just crashes. I have a new MBP retina with Mountain Lion and the latest Parallels Desktop.
I want my money back! I'll be going back to VirtualBox, since we get no answer from the Parallels support team...
Use a Windows desktop. Install Parallels Workstation trial. Open the VMware workstation/Fusion VM in Parallels. Parallels converts the VM to a pvm format. Copy it to your Mac and open it with Parallels Deskop.
Same issue here; also retina MBP. Was hoping Parallels would fix the vmware graphics driver issues and above all the 'retina problem' (that vmware insists on popping back to retina native res any chance it gets), but this is a show-stopper; not worth the trouble of rigging a physical windows box to be able to convert my existing infrastructure. Since Parallels has been pushing that they are retina-capable, I'm surprised they haven't commented on this problem. And there's no way for a trial download to get a support ticket ... which must cost them a lot of customers.
Happens to me with all VMDKs and NOT MBP Retina Plain vanilla MBP 2010. Tried two different VMDKs, no love. App completely bombs and comes back up with a "report a serious error message". So far I have tried: 1. Reinstalling 2. Verifying permissions on disk 3. Rebooting 4. Trying multiple different VMDKs Sad.
Looks like Parallels knows about the issue and has a workaround until they get a patch out. http://kb.parallels.com/en/114412 Hope this helps.
Right ! Just go to the 15098 build till it's fixed in the new update. We appreciate all your patience and cooperation