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
Same problem on a new 20" IMac

I have this same problem on a new IMac and new version of Parallels. I'm interested in a solution, but from the looks of this thread, no progress has been made in a month. I don't think turning off processors or reducing speeds is much of a solution either. Frankly, I'm surprised the Apple store is even selling this.
 
Upvote 0 Downvote
Guys,

Internal build 1896.2 should work fine on all Mac Pro and iMac Core 2 Duo with 2G RAM or less. There are still issues with more than 2G RAM - it could work and it could not - but no more kernel panics anyway. We are working hard on supporting more than 2G RAM and will deliver solution soon. As temporarily workaround you can use maxmem 2048 boot option.

Internal build 1896.2 can be downloaded from here - http://download.parallels.com/RC/Parallels-Desktop-1896.2-Mac.dmg. We apologise for inconvinience.
 
Upvote 0 Downvote
Andrew @ Parallels said:
Guys,

Internal build 1896.2 should work fine on all Mac Pro and iMac Core 2 Duo with 2G RAM or less. There are still issues with more than 2G RAM - it could work and it could not - but no more kernel panics anyway. We are working hard on supporting more than 2G RAM and will deliver solution soon. As temporarily workaround you can use maxmem 2048 boot option.

Internal build 1896.2 can be downloaded from here - http://download.parallels.com/RC/Parallels-Desktop-1896.2-Mac.dmg. We apologise for inconvinience.
Click to expand...
1896.2 isn't working any better for me on my Mac Pro (2.66 + 3GB of RAM).

With 1896.2 installed, I no longer see kernel panics, but instead, after some period of use, my Mac locks up completely, requiring a power down. To install XP required 3 attempts, as this problem occured in my first 2 attempts. Once the install completed, it seems every attempt to run the VM will lock up my mac within 10 minutes, requiring powering down and rebooting.

As my mac has > 2G RAM, i have spc ified the maxmem 2048 boot option. Any other thoughts or suggestions?
 
Upvote 0 Downvote
Andrew @ Parallels said:
ctebo,

Does it work for you with restricted memory maxmem=2048?
Click to expand...
Andrew,

Sorry for not being clear about the memory settings... The problems I described above with 1896.2 are occuring when maxmem=2048 is being applied. I have not even tried without the maxmem=2048.

Some additional info that might be helpful with this.... I've noticed that just before parallels locks my machine up, one of my cpus goes to 100% utilization in activity monitor, and stays there. It seems to sit at 100% cpu for perhaps 10 to 20 seconds prior to locking the whole machine.
 
Upvote 0 Downvote
Andrew—

I'm having a similar problem. When I try to launch the VM, sometimes I get the beach ball and I can't either quit or force quit Parallels, although it doesn't always lock up my machine completely. In order to quit Parallels, I have to reboot (I've tried simply logging out and back in, but that doesn't work; it quits Parallels, all right, but if launch it and then try to start my VM, I immediately get the beach ball).

Other than that it runs beautifully—no kernel panics, networking is OK (I'm using host-only with Internet sharing), and shared folders work.
 
Upvote 0 Downvote
Everything has been working great with my 2.66Ghz / 2GB RAM Mac Pro.

XP Pro
CentOS 4.4
Fedora Core 5
RHEL 5 beta 1
Ubunto 6.06.1

I no longer have to do the network-shuffle (jumbo packets on / off) with 1896.2. I haven't really played with VT-x support.

Mike
 
Upvote 0 Downvote
I'm still getting the spinning beach ball with 1896.2, it starts during Windows loading after it has resized the screen, with the blue Windows welcome screen, sometimes get's a little further but not much.

I have maxmem=2047 set, I do have 6GB installed. If I set -legacy option, then it works fine.

Edited to add:
System Version: Mac OS X 10.4.7 (8K1079)
 
Last edited:
Upvote 0 Downvote
crash and burn

For what it's worth, build 1884 sends my Core Duo Intel iMac 1.83 GHz system into an immediate reboot when I launch an XP virtual machine.

Reinstalling build 1848 resolves the problem.
 
Upvote 0 Downvote
Just wanted to mention a related experience with Parallels Desktop for Mac (1848) and
the Cisco VPN 3000 client....

System is a new 2.33 GHz Intel Core 2 Duo, 2 GB 667 MHz DDR2 SDRAM,
24" iMac running Mac OS X 10.4.7. Install of Parallels tripped a KP which
put the system into an endless series of boot - KP - boot - KP. So, I safe booted,
uninstalled Parallels and then looked for culprits. Decided that since the panic
logs pointed a finger at com.cisco.nke.ipsec that I should try to deinstall
the Cisco VPN 3000 client. The Cisco supplied /usr/local/bin/vpn_uninstall
script triggered a KP when it tried to run

/System/Library/StartupItems/CiscoVPN/CiscoVPN stop

so I moved the CiscoVPN directory out of /S/L/SI, rebooted, and then successfully
ran /usr/local/bin/vpn_uninstall.

With the Cisco VPN out of the way, 1848 of Parallels Desktop for Mac installed nicely.
Now, to install Windows XP Pro. Guess I'll run the Cisco VPN under it until such time
that Cisco issues a VPN client which doesn't trigger kernel panics. And, I have no reason
to believe that Parallels was at fault here: judging by Google results, lots of folks have been
experience KPs with the Cisco VPN client (usually when shutting down their intel Mac).

Regards,
Dan
 
Last edited:
Upvote 0 Downvote
It works!

I'm pleased to say that with the new 1896.2 build, my 3GB 2.66GHz Mac Pro is successfully running my WinXP Pro virtual machine without issue, except for that outstanding Apple bug leaving VT-X turned off. Previously running with VT-X on after sleeping my Mac Pro, Parallels would kernel panic. Now that problem has gone away and I am running at full speed with max RAM.

Great job, Parallels! Now convince Apple to fix that bug. Why did they leave VT-X off by default in the first place?

EDIT:
I just noticed one weirdness. With Parallels running, my Cisco VPN won't start.

EDIT2:
It killed my Cisco VPN altogether. Now it won't run at all even after a reboot. I also had an oddity. I was upgrading the firmware on one of my Slingboxes within Windows when the keyboard stopped working inside Windows, though it worked fine in Mac OS. I shut down the VM and tried to launch it again. It failed with a "cannot access VM" error. Odd.

I restarted, slept the Mac, started up. Upgraded another Slingbox and shut down. This time it started back up just fine. I wonder now whether reinstalling VPN will fix it.
 
Last edited:
Upvote 0 Downvote
After this latest build my Remote Desktop software doesn't work either. Something else to go along with the Cisco VPN...

At least the build stops the kernel panics, but it just results in the spinning beachball of death everytime I try to run something.

Mac Pro 4GB.
 
Upvote 0 Downvote
I can confirm the bug posted above as well. Cisco VPN connects but RDP no longer works and several other networking apps will not work when Cisco VPN client is connected.

build 1898
MBP 17" 2GB
XP sp2


Bryan

Edit: Uninstalling/Reinstalling the Cisco VPN client fixed my problems.
 
Last edited:
Upvote 0 Downvote
You must log in or register to reply here.
Back
Top