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

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!
 
No Love Here

Just upgraded and also did a "clean" install, Kernel panic each time. Doh!


----------------
Machine Name: Mac Pro
Machine Model: MacPro1,1
Processor Name: Dual-Core Intel Xeon
Processor Speed: 2.66 GHz
Number Of Processors: 2
Total Number Of Cores: 4
L2 Cache (per processor): 4 MB
Memory: 2 GB
 
I posted in another thread.. but so far.. knock on wood.. things seem to be working except for a few small quirks(like having to put the system to sleep to get vtx enabled and tinkering with the mtu size).. but otherwise.. so far so good..no kernel panics yet..(KNOCKING really HARD on wood ;))
 
I would like to say thank you to the team at parallels for this release.

I stand corrected this was not just marketing eze, they really came through.

It seems to work on a stock mac pro 2.66 with 1 gb of ram except for the absolutely terrible tcp/ip speed issue. Its so slow that I think using it to look at web sites we produce in IE is next to impossible.

Hopefully the team comes through again with a quick fix for the stack.

Thansk again Parallels!
 
enyim said:
well, host only is not working as the "Parallels guest adapter" disappeared from the Network prefs.

I tried to recreate it, but it did not help.

Strangely, I have a Parallels Adapter in the "from" dropdown at the iternet sharing prefs, while in the checkboxlist got an "en2" only.

moreover the parallels DHCP server does not seem to be assigning IP address to my windows instance, because i have an Ip address assigned by my router in woindows. (192.168.x.x vs parallels' 10.0.10.x)

if i assign a manual IP address from the range set in the paralles' prefs, at least te packets are travellnig (tracert for example), but DNS is not working.

so back to bridged networking and the "MTU tricks" every time I restart.

i hope the next build will be better.

Select "en2". That's what I did, and it works beautifully—and at full speed.
 
firebird2k said:
I posted in another thread.. but so far.. knock on wood.. things seem to be working except for a few small quirks(like having to put the system to sleep to get vtx enabled and tinkering with the mtu size).. but otherwise.. so far so good..no kernel panics yet..(KNOCKING really HARD on wood ;))

Things seem to be working well for me also. I've been using the standard / jumbo network packet toggle to enable fast TCP/IP.

Tell me about enabling VT-x support...

Mike
 
drbrog said:
I am unable to connect to the Internet and "en2" is not listed under Bridged Ethernet. Any suggestions? :confused: :confused:


try going into system setting and then sharing then click on internet. In the share your connection from click ethernet adapter and then click share your computer to click whatever box your ethernet cabvle is plugged into then start sharing button. I had to un click bridged ethernet parallels and this option worked perfectly for me.
 
eodchop said:
try going into system setting and then sharing then click on internet. In the share your connection from click ethernet adapter and then click share your computer to click whatever box your ethernet cabvle is plugged into then start sharing button. I had to un click bridged ethernet parallels and this option worked perfectly for me.

I went to System Preferences- Sharing- Internet. Under Parallels Host-Guest Adapter, I have turned on my live Built-In Ethernet and started Internet sharing. Then in Parallels, under network adapter, I clicked Host-Only networking. When I start up XP Home, no connection to Internet.

Is this the correct configuation you used?
Thanks
 
drbrog said:
I went to System Preferences- Sharing- Internet. Under Parallels Host-Guest Adapter, I have turned on my live Built-In Ethernet and started Internet sharing. Then in Parallels, under network adapter, I clicked Host-Only networking. When I start up XP Home, no connection to Internet.

Is this the correct configuation you used?
Thanks
Mine is share your connection from built in ethernet adapter

to pc using ethernet adapter. (bottom box)


and host only networking in parallels
 
Working fine on 2 GByte 2.66 GHz Mac Pro here. Switched back to non-legacy mode, launched my existing Ubuntu, Win 98se, Fedora VMs with no problems. Created a new one for kicks, just to make sure that bit works - no problem. I don't have any issues with TCP/IP (bridged mode), and I haven't had a VTX issue either, presumably because I'm too skinflint to get XP, and am only using 98se on the Windoze side.

With one day left on my trial key, that was a close run thing, but I guess Parallels can have my $80 now :)
 
Mac Pro Networking

Although I can get bridged networking to work on a Mac Pro (after the usual limting the RAM to 2000 from the actual 6 GB, etc), I found that depsite toggling the MTU, I had the best performance when the MAC ID used by Paralles matched the real MAC ID of the Mac Pro - which means that the Mac Pro canot access the internet from a browser at the same time due to the conflict. BUT - the Mac Pro has TWO ethernet ports. In the Mac System Config, I made sure that the normal ethernet ports is listed first (by dragging). I attached a new ethernet cable to the otherwise unused port and attached it the my router. I then duplicated the settings and configured Parallels to use this ehternet port, rather than the original one. Still need to toggle the MTU, etc., but now no conflict. Was able to go to several otherwise unavailable webs ites using complex ActiveX, JAVA and secure tunnels without a problem.

I am not sure if this is all really necessary. Any suggestions?

By the way, GoToMyPC within Parallels works from an offsite PC and lets you control the Parallels VM, but it actually crashes the Mac system when you log off!

Major bugs:

1. Memory limitation unaccepatble - spent too much on 6 GB of RAM to turn if off. Will use Bootcamp if I have to reboot.

2. Toggling MTU is an old problem with Parallels predating the Mac Pro. Again, too many hoops to make this all worthwhile.

3. VTx issues persist. Less frequent when I turn off sleep for the Mac. But I still occassionaly get. One more performance hit.

:eek:
 
Last edited:
A little acknowledgement

Okay, so yes, people in this thread were getting borderline violent asking for Parallels to release a version which works on the MacPro, so they do the best that they can and release something. Now all of those people aer accusing them of rushing it and not testing properly. Kinda funny.

Anyways, I wouldn't mind an update from someone offical at least acknowledging that they are some serious issues and they they expect a new verison released in a few days.

We all know they are doing the best they can. So keep up the good work and I look forward to virtualization on my MacPro sans Kernel Panics.

:D
 
How about letting us know?

I have 4GB of RAM on my Mac Pro, and like everybody else, I can't make Parallels work. Last night, after adjusting the maxmem in Terminal to 3400, Parallels let me install all of the Windows XP files, then - you guess it - Kernel Panic once again. When the computer rebooted, the copied files had disappeared, so I gave up.

While I don't want to become violent about this in any way, how about a little word from PARALLELS? "We're working on making Mac Pro with more than 3.5 GB of memory work with Parallels. Be patient.", or "We know we can never make it work, just give up". I've wasted many hours trying to make an application I've paid for work without results and more crashes than with Mac Os 7 in one day! A little bit of information would be nice.
 
Try setting maxmen to 2000 rather than 3400. I have 6 GB of Ram on my 3.0 Quad. NO kernal panics. Only freeze was when I tried running accessing my Parallel VM via GoToMyPC remote softwar from another computer . Otherwise, no problem with crashes. Just falky network conections, VTx errors, etc.
 
Yes, i also got almost thru the whole WIN-install, rebooted and then a kernel panic. Tried this twice. It seems that when PD/WIN want to access the CD/DVD-drive i get i kernel panic, each time. The trix is to take out the DVD-disc as soon as u can to get to the next step but in the end you will get a kernel-panic and all files are lost.

MacPro 3Ghz/3Gb RAM.

Thx.
 
Update

Folks, incase you haven't seen there is update posted at: http://parallelsvirtualization.blogspot.com/

The part I was interested in was this:

"If you updated your build and tried to launch Parallels Desktop from the original shortcut icon your placed in your dock or on the desktop, you will not be able to load Parallels Desktop properly.

You MUST either run this beta build of Parallels Desktop directly from your Applications folder, or delete the original shortcut on your desktop/dock and replace it with the newer one that appeared in the Parallels Application Folder. Parallels Desktop is located at Macintosh HD -> Applications -> Parallels -> Parallels Desktop."​

I'm at work and haven't tried this... Anyone have any luck not getting Panic's using this solution?
 
Back
Top