Starting a virtual machine crashes Mac Pro (new Intel tower)

F

faddante

Bit poster
I just bought a new Mac Pro (Intel tower) this morning. I installed Parallels (I tried both the 1848 build and the latest beta)... The installation went fine, I was able to create the virtual machine just fine... However, as soon as I go to "Power On" the virtual machine for the first time, it crashes my computer (I get the translucent grey Apple screen that locks up my computer and says that I need to reboot my computer). Every once and a while, it won't crash my computer, but I will get a Parallels error dialogue that says "Unable to connect to hypervision".

I tried uninstalling, rebooting, reinstalling and I still consistently have the same problem.

I looked in the console and here is the error in the panic.log:

*********

Wed Aug 9 16:38:36 2006
panic(cpu 2 caller 0x001A4115): Unresolved kernel trap (CPU 2, Type 27=Unknown), registers:
CR0: 0x80010033, CR2: 0x2d338000, CR3: 0x00fc5000, CR4: 0x000006e0
EAX: 0x0000000a, EBX: 0x6d626572, ECX: 0x00000000, EDX: 0x00e4d618
CR2: 0x2d338000, EBP: 0x14cb3b18, ESI: 0x6d616769, EDI: 0x63216e75
EFL: 0x00000246, EIP: 0x2c434fb1, CS: 0x00000008, DS: 0x2d330010

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x14cb3908 : 0x128cdb (0x3c99c4 0x14cb392c 0x131cdf 0x0)
0x14cb3948 : 0x1a4115 (0x3cf6c0 0x2 0x1b 0x3c8e48)
0x14cb3a58 : 0x19ad14 (0x14cb3a70 0x14cb0048 0x14cb0010 0x190010)
0x14cb3b18 : 0x2c171fea (0x3c93218 0x0 0x3c93204 0x199103)
0x14cb3bd8 : 0x2c1722e9 (0x3c93204 0x14cb3ec8 0x18 0x0)
0x14cb3d58 : 0x2c17058a (0x3c93204 0xc0185401 0x14cb3ec8 0x3794888)
0x14cb3d78 : 0x1f00f7 (0xa000000 0xc0185401 0x14cb3ec8 0x81)
0x14cb3db8 : 0x1e7045 (0x14cb3de0 0x297 0x14cb3e18 0x1d09ee)
0x14cb3e18 : 0x1deee9 (0x3d80d68 0xc0185401 0x14cb3ec8 0x81)
0x14cb3e68 : 0x3305b4 (0x3addf10 0xc0185401 0x14cb3ec8 0x3a273e8)
0x14cb3e98 : 0x34e881 (0x3addf10 0xc0185401 0x14cb3ec8 0x3a273e8)
0x14cb3f68 : 0x378f9c (0x3a273e8 0x3a2a940 0x3a2a984 0x0)
0x14cb3fc8 : 0x19b0ee (0x3bee680 0x0 0x19e0b5 0x31c002c) No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xbfffe128
Kernel loadable modules in backtrace (with dependencies):
com.parallels.kext.vmmain(2.2)@0x2c16f000

Kernel version:
Darwin Kernel Version 8.7.2: Tue Jul 25 23:09:54 PDT 2006; root:xnu-792.10.96.obj~3/RELEASE_I386


I am hoping someone can help me with this... I really need to get this working on my computer, I use Windows just as much as I use Mac OS.

Thanks!
 
Sort by date Sort by votes
A little more feedback.

(1) I downloaded the beta and it simply doesn't work, regardless of what nvram settings I put. I reverted to the retail, and I have no problems except on restart. With the MTU set to 1024 (in Windows, not in OS X), I have no *Internet* issues (it's kicking ass), though LAN access is still a little iffy. No website loaded with the MTU at 1500. Still though, I swear, I have a longer uptime and a shorter boot time in Parallels than I ever did on one of my old Dells.

(2) People who expect this to work already are dilusional. Whatever this problem is, it's a relatively low-level (ie. closer to the hardware) problem and probably will require some changes that, while they might be fixed simply in the code, might have effects on others parts of the code, so I'm sure there are a lot of d and alpha stages to come. Having said that, they shouldn't be surprised when people feel a little upset when it doesn't work out of the box on what's supposed to be the killer mac.
 
Last edited:
Upvote 0 Downvote
I think it's an entirely valid point that the Parallels folks ought to be more explicit on their web site about the Mac Pro issues. But my gosh, people, this kind of thing is a bit over the top:
I got my Mac Pro last week and Parallels Desktop hoping to finish an important project over the weekend.
Click to expand...
The idea of buying a Mac Pro to finish an important project over the weekend? Uh-uh. That's more than a bit imprudent.

The Mac Pro is a brand new piece of hardware with significant differences (specifically, 64-bit support). Nobody should expect any software to run successfully on it right out of the gate. You should be looking for affirmative confirmation of Mac Pro compatability for any software you consider critical to your workflow, not just the absence of reported issues.

Again, without a doubt the Parallels folks ought to have a prominent message on the front page of their web site. But frankly, anyone who is that anxious to get the newest hardware up and running is asking for trouble. The reason you're not going to find a big outcry in the press, and the reason you won't in the future, is that frankly the injustice here isn't severe.
 
Last edited:
Upvote 0 Downvote
I am having a slightly different problem.

I had Paralles (retail version) installed on a 2.0ghz Macbook with Windows XP home and it was running just fine.

I just bought a new MacPRO (2.66 dual with 2gig Apple memory)..
I used the Apple Migration utility to bring everything over from the Macbook to the MacPRO,
including the full Paralles, windows installation.

When I try to launch paralles, I get an error saying that it could not start as it could not find a necessary driver.

I assume that is due to the fact that it may not have the video drivers etc for the Mac Pro, but
in anycase, it will not start up at all, other than the immediate error message.

The good news is that, under these circumstances, it cannot crash or casue a Kernel panic.

Some of you have been able to get it runing in some fashion however.
Does that imply that the necssary drivers are there for the MacPRO on the retail version?

And if that is true, does anyone have an explanation for the situation that I am seeing on my system?

I have not seen this particular issue discussed in these threads

Thank you,
Harley
 
Upvote 0 Downvote
The Migration Assistant doesn't migrate kernel extensions. Parallels installs kernel extensions. They're the drivers that the application says it can't find. You need to install Parallels directly on the Mac Pro. Then, you'll have the same set of problems as everyone else on that machine.
 
Upvote 0 Downvote
Again, my point was only regarding the lack of a warning about the incompatibility which would spare Mac Pro customers a lot of trouble and frustration.

I didn't buy a Mac Pro "to finish a project over the weekend" obviously. The story is a bit longer but this is not really relevant here. I finished the project on another machine.
 
Upvote 0 Downvote
My apologies if I caused any offense. It's just that I have been through this before and this time I am much more optimistic for a timely fix.

I bought the first-generation G5 and needed Virtual PC, which wasn't compatible. It was months before VPC was compatible with my G5. On the other hand, I bought a first-generation Mac Pro to replace the G5 and it's been 2 days since I got it, but already there is at least a "workaround" for lack of Parallels support on Mac Pros.

Regardless, the problem should be fixed soon and this will all be a bad memory. :p
 
Upvote 0 Downvote
Toggling MTUs vs setting Windows registries

marcmec said:
What's the advantage to that? By changing the windows registry, it's a one-time adjustment. Otherwise you have to toggle the MTU setting in OS X each time you boot a VM. What am I missing?
Click to expand...

Simple answer: The registry fix will cause other unpredictible problems.

Nerdy answer: Fragmentation is an important part of the TCP/IP protocol. It allows us to send packets over different mediums that contains differnet MTUs. While most networks won't have a problem with 1024 (as suggested in one post) there will be a few that do. With multiple routes to the same destination, sometimes a site will work and other time it will not.
 
Upvote 0 Downvote
This is a status?

"Development team is working on Mac Pro support and fix will be available in upcoming public build. Stay tuned."

And that build has an ETA of.....

1.) today
2.) tomorrow
3.) next week
4.) next month
5.) before VMWare comes out with their beta
6.) Sometime in 2007

We know we can't hold you to an exact date... but can't you give us some better idea?
 
Upvote 0 Downvote
Another kernel panic error...

I suspeneded my VM, restarted the Mac, came back to Parallels, restarted the suspended VM and got the grey screen of death.

I'm running Parallels on a 3ghz Mac Pro, 2G RAM with the nvram setting suggested in this forum. Just in case this is useful to the team....
 
Last edited:
Upvote 0 Downvote
NVRAM Fix + MTU Toggle = working parallels for me.

It doesn't work after every OTHER reboot, but no big deal. No kernal panics or hypervisor errors. I'm eagerly awaiting a real update, but this is good enough for now!
 
Upvote 0 Downvote
Thank YOU!!!!

Andrew @ Parallels said:
My unofficial estimation is somethere around 3 and 4.
Click to expand...

Look, I can live with "we don't have an answer, but we think within a couple of weeks" is a hell of a lot better than "Stay Tuned".


Part of the reason that my house is now PC free is you guys, because litterally, all I need this for is VPN to work... and after having myself and a couple of other key players defect to MAC, I can say, we are now working on that issue and plan (unofficially) to have it resolved sometime between 4 and 5.....
 
Upvote 0 Downvote
Andrew @ Parallels said:
We will make an announcement and send direct mail once we have build which support MacPro. Don't worry - you will be notified immedeately.
Click to expand...

:rolleyes:

Andrew... based on your phrasing of you comments... is it my imagination or are you from the UK?

lol

again, thank you for the update. I'm going to go try to make the workaround work...

Some advice... don't be HAL + 1 (big blue...) and don't be the like the folks up in the seatac area... you know, 1 fixpack away from having it right.

Be upfront.... we can all sleep better that way....

:p
 
Upvote 0 Downvote
This is great news

Hi,

Okay so a couple of weeks then. This is great news since I couldn't use Parallels properly on my Mac Pro anyway until Crucial get their RAM sorted which is also going to be a couple of weeks.

Hopefully my mid Sept we should be sorted RAM and Parallels wise.

And then we can bug you guys about the suspend functionality in Solaris :)

regards
Steve
 
Upvote 0 Downvote
You must log in or register to reply here.
Back
Top