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
Works great for me, but...can't install Tools

The new release works fine on my Mac Pro (one of the first shipped, purchase 8/10/06 with the original release of 10.4.7). Have not updated the firmware yet.

I started from a new virtual HD container and installed an nLite'd version of XP Home SP2. No problems. Internet works seamlessly. Did have to put the machine to sleep to enable VTx but that's well known.

I have not tried my PocketPC or SmartPhone yet but I suspect based on what other people say they won't work.

My current problem is that Parallels Tools will not install. I select it from the menu and things churn for a moment but nothing ever happens in Windows. If I then go back to the menu it says "cancel tools installation" whcih I select but also does nothing.

Is this a known problem? I'd like to get the smooth video and mouse to work.

Of course at this point everyone is happy just to have the thing boot on the Mac Pro. I really am excited because I don't want to deal with BootCamp.

jason
 
Upvote 0 Downvote
Keyboard @ and # characters not mapped properly

Andrew,

I updated to the new build but I see that the problem I reported, keyboard keys @ and # not mapped properly, is still not fixed.

Any ideas when that will be fixed?

Thanks
 
Upvote 0 Downvote
Make the update obvious?

I purchased a hard copy today, build 1848.2 (June 26, 2006) and ran the upgrade search. I was told the SW was up to date. Then I ran into the kernel panic problem on my Mac Pro.

If there is a update that provides a fix, it should be available throught the update menu. This has cost me a couple of hours so far. Thanks a bundle.
 
Upvote 0 Downvote
Make sure you have any firewall or anti-visur programs turned off on your VM. ZoneAlarm was stalling my Tools installation, which proceeded once I turned it off.
 
Upvote 0 Downvote
Andrew @ Parallels said:
Check this topic please http://forum.parallels.com/thread4487.html.
Click to expand...
Andrew,

I have the same problem as reported in this thread (cannot perform Tools installation) and the thread you listed does not directly address the problem or I cannot find any relevant information.

Please provide a more specific link and not the start of a thread with hundreds of posts.

Even better how about just stating either of the following:

1. We know about the problem, we are addressing it and we hope to have a fix by ????

2. We don't know about the problem and have no idea when it will be fixed

3. Forgetaboutit (just like my long ago reported @ and # keyboard problem)

Which is it?
 
Upvote 0 Downvote
Let me add my tuppence....

If you have an Nvidia 7300 card in your Mac Pro, Apple ships buggy display drivers...there is currently some tug-of-war going on betwen Apple and Nvidia to get this fixed, but Nvidia says that until they test and release a new driver, the only thing you can do is leave only the first 2GB of RAM enabled and run OSX in legacy (i.e., 32-bit) mode. Apparently, Nvidia's drivers aren't '64-bit clean' yet....

Long story short, this is not a Parallels problem per se.....
 
Upvote 0 Downvote
Dracula,
Unfortunately, a lot of the problems we're experiencing with Parallels are symptomatic of Apple -- their port of OSX to Intel Core is incredibly buggy.....Parallels is a very resource-intensive application, so it stresses OSX and the hardware in ways most apps don't. The Parallels team is doing a decent job working with what they've had dropped in their laps, which is a half-baked implementation from Apple...
 
Upvote 0 Downvote
You must log in or register to reply here.
Back
Top