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

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!

 

Exact same problem here. I'll post the log file if needed, but it looks a lot like the original poster's.

 

Mac reboots when installing Parallels

As a follow-up. I tried uninstalling again... Now I am seeing the same problems during installation.

Now, when I try to re-install it, when then progress bar gets about 90% of the way (something about "installation scripts"), my computer instantly reboots (no grey screen this time). It does it consistently.

Then when it reboots, about 5 seconds after I login, it automatically goes to the grey screen and forces me to reboot again.

The only way for me to stop it is to boot into safe mode (by holding down the shift key) and uninstalling Parallels. Then, I reboot my computer and everything is fine again.

 

Try installing the CHUD tools and disabling the second CPU (both cores of the second CPU). Maybe Parallels is freaking out about that. That is the only guess I have.

 

I'm not going to do the second CPU disable thing right now. At this point, I'm mostly interested in benchmarking. Long term, I'll want this to do the whole shebang and can probably wait for Parallels to fix whatever is wrong.

In the meantime, I'm happy to try any patches or other tips Parallels would like.

 

Good idea. I just tried disabling the second CPU, unfortunately, it didn't work. I still have the same problem. Thanks.

 

What OS version is on the Mac Pro? I'm willing to bet it is a special version of Tiger for 64-bit. I remember that there was a little app you could compile (gnu) that would tell you the word size in your kernel, but I seem to have lost it someplace.... Maybe it was only a linux thing...

Inserting a 32bit kernel extension into a 64-bit OS is not good.

 

Here is what it says in the System Profiler:

System Version: Mac OS X 10.4.7 (8K1079)
Kernel Version: Darwin 8.7.2

I looked on the Apple site and it looks like this is a build that was just released. However, it does not specify if it is a 64-bit kernel. However, I would imagine that it would make sense that it is, seeing as how it is a 64-bit machine.

 

Guys,

We are aware of this problem and working on it with a very high priority! The fix will be available soon - keep in touch.

 

How will you alert us to the patch?

Will you post here when a fix has been made? Or where?

Thanks for attending to this... we're all looking forward to using your software on these exciiting new machines!

 

We will update Beta build, will send direct mails and post announcement on forums. Stay tuned.

 

poor communication

Could you guys add this information to a FAQ or other page in the meantime? I burned much time trying to get this to work and happened to stumble upon this set of forums from the discussion groups on Mac Pros (it doesn't appear to be linked from any support page on www.parallels.com).

I opened a support ticket for this on Wednesday but haven't received a response.

 

We wait for an mail or a new posting.

Thanks.

 

Anyone having luck

Has anyone had luck getting this problem resolved yet?

 

Any eta on the fix for the mac pro? I am very interested in getting this working to demo for a new computer purchase for my company.

 

Guys,

We do work on Mac Pro support by PD. However, it will take us a short while to prepare and test the update.

For those who badly need to run PD on MP right now or want to experiment a bit, there is a workaround. Please treat it as unofficial (untested and unsupported) one, it is provided as is.

1. Open Applications->Utilities->Terminal
2. Run the following command:

Code:

sudo nvram boot-args="-legacy"

3. Reboot your Mac Pro.

This will switch your MacOS into legacy (32-bit) mode.

If it doesn't help and you still experience hypervisor problems or even kernel panics,

1. Open Applications->Utilities->Terminal
2. Run the following command:

Code:

sudo nvram boot-args="-legacy maxmem=2048"

3. Reboot your Mac Pro.

Please note, the 2048 value is empiric one. You may find greater values working for you - just experiment.

If you want to revert your Mac Pro back to original state, here's what you need to do:

1. Open Applications->Utilities->Terminal
2. Run the following command:

Code:

sudo nvram boot-args=""

3. Reboot your Mac Pro.

 

The first argument allowed me to at least start the VM. However, then when I installed XP, it wouldn't run.

I have not tried the other options yet, decided I rather wait for the real fix. I did get the error message about VT-X (sp?) being disabled in the BIOS.

T

 

In my case, the 1st argument allowed me to reinstall Parallels and start my saved VM... which then crashed soon afterwards (but did not Kernel Panic.) A 2nd time I still got a Kernel Panic.

Then I tried the 2nd argument, trying different values, I had no success. I kept getting the "hypervisor" error message.

I reverted back to my Mac Pro's original state after that, not wanting to mess anything up.

Thanks for trying, but unfortunately none of these workaround suggestions work on my Mac Pro. Here's hoping you can all figure it out!

 

Same issues here. The workaround didn't "work around". Any eta on a fix?

Thanks,

groovyjason

 

Didn't work for me either... My system crashed during install -- I tried both options. Then it continued to crash immediately on boot.

I needed to reboot my computer in safe mode and then do uninstall to get it to stop crashing on boot.