Kernel panic when upgrading my VM HD to v.3.0 in Mac OS X 10.4.10

I'm a registered user of the full version of Parallels Desktop v.3, in the process of upgrading from v.2.5. When the program attempted to update my virtual machine's hard drive just now so it would be compatible with v.3, it caused a kernel panic. I am running Mac OS X 10.4.10, which I installed via the standalone combo updater this morning without incident -- well, except for this. :^/

I rebooted my MacBook Pro and relaunched Parallels Desktop 3.0 just now, and it said it could not start because my VM was unreadable. Ouch.

Thank goodness I had a full backup of the VM, which I am restoring now.

Is the VM HD upgrade process incompatible with Mac OS X 10.4.10? I realize it's brand new, but if anyone at Parallels or elsewhere can shed any light on this situation, I'd be grateful.

Thanks,
Eric.

The text of the kernel panic log is below:

panic(cpu 0 caller 0x001A4A55): Unresolved kernel trap (CPU 0, Type 27=Unknown), registers:
CR0: 0x80010033, CR2: 0x41280000, CR3: 0x01888000, CR4: 0x000006e0
EAX: 0x0000000a, EBX: 0x6d626572, ECX: 0x00000000, EDX: 0x01076e00
CR2: 0x41280000, EBP: 0x25fcbb18, ESI: 0x6d616769, EDI: 0x63216e75
EFL: 0x00000246, EIP: 0x4013c8f1, CS: 0x00000008, DS: 0x41280010

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x25fcb908 : 0x128d08 (0x3cc0a4 0x25fcb92c 0x131de5 0x0)
0x25fcb948 : 0x1a4a55 (0x3d24b8 0x0 0x1b 0x3cb56c)
0x25fcba58 : 0x19aeb4 (0x25fcba70 0x25fc0048 0x25fc0010 0x190010)
0x25fcbb18 : 0x3df6eb86 (0x59cec18 0x0 0x59cec04 0x16d)
0x25fcbbd8 : 0x3df6f2de (0x59cec04 0x25fcbeb8 0x18 0x0)
0x25fcbd38 : 0x3df6b959 (0x59cec04 0xc0185401 0x25fcbeb8 0x6)
0x25fcbd68 : 0x1f1668 (0xd000000 0xc0185401 0x25fcbeb8 0x81)
0x25fcbda8 : 0x1e84a2 (0x25fcbdd0 0x297 0x25fcbe08 0x50b75dc)
0x25fcbe08 : 0x1e02a3 (0x56549cc 0xc0185401 0x25fcbeb8 0x81)
0x25fcbe58 : 0x332ac8 (0x5831cb0 0xc0185401 0x25fcbeb8 0x50b75dc)
0x25fcbe88 : 0x350e24 (0x5831cb0 0xc0185401 0x25fcbeb8 0x50b75dc)
0x25fcbf58 : 0x37ad83 (0x50b75dc 0x545bbf0 0x545bc34 0x0)
0x25fcbfc8 : 0x19b28e (0x52130a0 0x0 0x10 0x0) No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xbfffdf88
Kernel loadable modules in backtrace (with dependencies):
com.parallels.kext.vmmain(2.2)@0x3df6a000

Kernel version:
Darwin Kernel Version 8.10.1: Wed May 23 16:33:00 PDT 2007; root:xnu-792.22.5~1/RELEASE_I386

Model: MacBookPro2,2, BootROM MBP22.00A5.B01, 2 processors, Intel Core 2 Duo, 2.33 GHz, 2 GB
Graphics: ATI Radeon X1600, ATY,RadeonX1600, PCIe, 256 MB
Memory Module: BANK 0/DIMM0, 1 GB, DDR2 SDRAM, 667 MHz
Memory Module: BANK 1/DIMM1, 1 GB, DDR2 SDRAM, 667 MHz
AirPort: spairport_wireless_card_type_airport_extreme (0x168C, 0x87), 1.1.8.5
Bluetooth: Version 1.9.0f8, 2 service, 1 devices, 1 incoming serial ports
Network Service: AirPort, AirPort, en1
Network Service: Parallels Host-Guest, Ethernet, en2
Network Service: Parallels NAT, Ethernet, en3
Serial ATA Device: Hitachi HTS541612J9SA00, 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: IR Receiver, Apple Computer, Inc., Up to 12 Mb/sec, 500 mA
USB Device: Bluetooth USB Host Controller, Apple, Inc., Up to 12 Mb/sec, 500 mA
USB Device: Apple Internal Keyboard / Trackpad, Apple Computer, Up to 12 Mb/sec, 500 mA
USB Device: Hub, Up to 12 Mb/sec, 500 mA
USB Device: Hub, Up to 12 Mb/sec, 500 mA
USB Device: Studio Display, Up to 1.5 Mb/sec, 500 mA
USB Device: Hub in Apple Pro Keyboard, Mitsumi Electric, Up to 12 Mb/sec, 500 mA
USB Device: Apple Optical USB Mouse, Mitsumi Electric, Up to 1.5 Mb/sec, 100 mA
USB Device: Apple Pro Keyboard, Mitsumi Electric, Up to 12 Mb/sec, 250 mA
USB Device: Telex USB microphone, Telex Communications, Inc., Up to 12 Mb/sec, 500 mA
FireWire Device: External HDD Button & Lights, WD, Up to 800 Mb/sec

 

It's not just you - I've been getting Kernel Panics all day as well after updating to 10.4.10.

However I already had been using 3.0 4128 for some time beforehand with only a few problems. I won't say none - it appears less stable than latter 2.5 builds. However I haven't seen anything like this before the system update.

I believe that some of the Parallels kernel extensions are conflicting with the new Apple kernel / extensions. I am in the process of uninstalling Parallels right now and reinstalling, following the process here: http://forum.parallels.com/thread11880.html

For me the problem usually beings to manifest with SystemUIServer running away, eventually causing all sorts of system instability and crashes, finally resulting in kernel panic.

Thu Jun 21 14:19:34 2007
panic(cpu 0 caller 0x00136744): stack_alloc: kernel_memory_allocate
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x2ec13f28 : 0x128d08 (0x3cc0a4 0x2ec13f4c 0x131de5 0x0)
0x2ec13f68 : 0x136744 (0x3cca34 0x2ec13f9c 0x4000 0x7fff)
0x2ec13fa8 : 0x13ae4f (0x3944d90 0x0 0x0 0x134b5e)
0x2ec13fc8 : 0x19ad2c (0x0 0x0 0x19e0b5 0x3949828) Backtrace terminated-invalid frame pointer 0x0

Kernel version:
Darwin Kernel Version 8.10.1: Wed May 23 16:33:00 PDT 2007; root:xnu-792.22.5~1/RELEASE_I386

 

Well, second time's the charm: I was able to get my Win XP HD to update, and I'm using it now with v.3. I still can't print anything but the simplest documents, though. It's especially frustrating because Virtual PC never had any problems printing, even going back to its earliest versions. (One of the few things it did well!)

I'm still leery, as I hadn't seen a kernel panic in years until today, but at least I can get some work done tomorrow. Curse DoubleClick and its PC-only web applications....

If those connected with Parallels learn anything more about 10.4.10 compatibility, I'd be grateful if they'd post it here.

 

The 10.4.10 update introduced problems for both Parallels and Fusion and has been discussed and is in now the KB and is a sticky note, too. Parallels is going to release a fix RSN (real soon now). Fusion's fix is already available. Expect leap frogging as Leopard gets closer - the applications will catch up, Leopard will leop ahead, applications will catch up again. Nothing new here, of course, but it sure is frustrating when it goes very many cycles.

Watch the News link above and for bulletins in the forums a level or two up from this one.