Kernel panic when using Parallels

Hey all, I recently installed Parallels on a 2.0GHz MacBook successfully. However, when I try to configure WinXP on it or if I click 'start virtual machine' (that green arrow button in the main Parallels window), I always get a kernel panic! Here's the info from the error report:

panic(cpu 1 caller 0x001A429B): Unresolved kernel trap (CPU 1, Type
6=invalid opcode), registers:
CR0: 0x8001003b, CR2: 0x22146034, CR3: 0x00d98000, CR4: 0x000026e0
EAX: 0x1404b588, EBX: 0x00001000, ECX: 0x033bf204, EDX: 0x00000000
CR2: 0x22146034, EBP: 0x1404b5a8, ESI: 0x033bf204, EDI: 0x00000001
EFL: 0x00010006, EIP: 0x006e64cb, CS: 0x00000008, DS: 0x1ed10010

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x1404b368 : 0x128d08 (0x3cb134 0x1404b38c 0x131de5 0x0)
0x1404b3a8 : 0x1a429b (0x3d0e4c 0x1 0x6 0x3d05e8)
0x1404b4b8 : 0x19ada4 (0x1404b4d0 0x1ed17000 0x1404b4e8 0x3bdeee)
0x1404b5a8 : 0x6e38d4 (0x0 0x2aa56c0 0x1404b5e8 0x6e4585)
0x1404b668 : 0x6e632b (0x6e6429 0x0 0x0 0x0)
0x1404b6b8 : 0x6e4742 (0x6e552f 0x0 0x1404b6f8 0x6e33a0)
0x1404b6d8 : 0x6e4830 (0x2b5c770 0x1404b714 0x1404b708 0x2c351f4)
0x1404b6f8 : 0x6e3413 (0x0 0x2 0x1404ba80 0x1404baa8)
0x1404b718 : 0x1f03ae (0xb000000 0x1 0x2000 0x2c351f4)
0x1404b788 : 0x1e41ab (0x1404b7b8 0x32ad4a4 0x1404b7e8 0x1cfadc)
0x1404b7e8 : 0x1de71d (0x32ad4a4 0x1 0x1404baa8 0x1404baa8)
0x1404b838 : 0x1df6ac (0x1404b954 0x1404b944 0x1404b854 0x1f796e)
0x1404b938 : 0x1cf952 (0x1404b954 0x1 0x0 0x0)
0x1404bac8 : 0x8da717 (0x8dd458 0x1 0x0 0x0)
0x1404bb08 : 0x8db6e8 (0x8dd458 0x1404bb44 0x14 0x2c351f4)
0x1404bb28 : 0x8da413 (0x3160584 0xd000000 0x3160584 0x1404bf48)
Backtrace continues...
Kernel loadable modules in backtrace (with dependencies):
com.parallels.kext.vmmain(2.2)@0x8d9000
com.parallels.kext.hypervisor(2.2)@0x6e2000

Kernel version:
Darwin Kernel Version 8.9.1: Thu Feb 22 20:55:00 PST 2007;
root:xnu-792.18.15~1/RELEASE_I386

Model: MacBook2,1, BootROM MB21.00A5.B00, 2 processors, Intel Core 2
Duo, 2 GHz, 1 GB
Graphics: Intel GMA 950, GMA 950, Built-In, spdisplays_integrated_vram
Memory Module: BANK 0/DIMM0, 512 MB, DDR2 SDRAM, 667 MHz
Memory Module: BANK 1/DIMM1, 512 MB, DDR2 SDRAM, 667 MHz
AirPort: AirPort Extreme, 1.0.47
Bluetooth: Version 1.7.14f14, 2 service, 1 devices, 1 incoming serial ports
Network Service: AirPort, AirPort, en1
Serial ATA Device: TOSHIBA MK1234GSX, 111.79 GB
Parallel ATA Device: MATSHITADVD-R UJ-857D
USB Device: Built-in iSight, Micron, Up to 480 Mb/sec, 500 mA
USB Device: Apple Internal Keyboard / Trackpad, Apple Computer, Up to
12 Mb/sec, 500 mA
USB Device: IR Receiver, Apple Computer, Inc., Up to 12 Mb/sec, 500 mA
USB Device: Bluetooth HCI, Up to 12 Mb/sec, 500 mA

Any ideas?

 

Bump! Anyone?

 

Did you recently apply the 10.4.9 upgrade.
If yes, did you upgrade via "System Preferences"?

ajm

 

Have you tried the usual Mac repair stuff (Repair Permissions, Repair Disk, delete caches, DiskWarrior, 10.4.9 Combo Updater)?

Also, which version of Parallels and which version of XP? How much free disk space?

David

 

I am encountering nearly the same issue, except my backtrace only shows the com.parallels.kext.vmmain module. My machine is also a MacBook Pro with an Intel Duo Core processor.

I installed the recent security update, via Software Update, I've checked and repaired permission and I still get the kernel panic.

How do I go about deleting caches? I can't see, however, how this would be the problem. The issue seems to be an incompatibility with the Parallels kernel modules and the kernel Apple supplied with the latest security update.

UPDATE

I just booted my Boot Camp installation from Parallels without a kernel panic, hurrah. I get the panic when trying to resume a suspended XP VM. Let me try rebooting the XP VM from scratch, i.e. deleting the suspended state (be back in a jiffy)... Bingo, that seems to have done the trick.

I wonder if the other guys who are getting kernel panics are also trying to restart suspended images? I guess that means this may be some sort of cache issue after all...

 

As far as I know, you can't suspend a Boot Camp VM from Parallels without ill effects, as you have experienced. This has been discussed several times on this forum, as a search will reveal.

David

 

Yasu, Applejack, etc. For this and other Mac maintenance, see <http://www.macattorney.com/ts.html>.

David

 

Fixed the issue with a software update, thanks all! Alas, but I am having another issue now.

 

If you specify which software update, it might help others solve similar problems.

David