OS X unstable after latest Parallels update

Ever since upgrading to 3188 I've experienced a rash of system crashes in OS X. In all prior builds, including beta builds, I've never experienced system-wide crashes while using Parallels. I often use two VMs simulaneously, both Win XP SP2 environments. I've been able to reproduce a system crash consistently whenever I do the following:

Open both Win XP VMs (512 MB Ram, shared folder enabled, no CDROM, no Floppy, no USB devices)
Login to corp VPN on one VM
Use other VM to Remote Desktop into server on my local LAN
Use Server in Remote session to startup Acronis Management Console for Backups.
Entire system crashes.

I've also experienced another crash in 3188 with both VMs open (one VPN'ed other not). But this time it was while using Safari in OS X to browse a website, so it may not be Parallels related. I'm not sure what the offending website had because I opened it in a background tab. However I've never experienced so many crashes until I upgraded to 3188. It has been the only change to my system in weeks, and I've made no changes to my daily workflow.

I haven't tried downgrading yet, I wanted to check to see if anyone else was experiencing anything similar.

Cheers,
Rob.

 

To clarify, I am not using MS Remote Desktop Client on OS X. I've found that is the easiest way to bring down OS X. I am using RDC inside the WinXP VM, which I have never had issues with in prior builds.

 

Haven't experienced less stability with the latest builds... Have you tried repairing your permissions and/or cleaning out your caches with a good utility such as Onyx?

 

And again the issue seems somehow related to memory as the crashes seem to be random. Can you please try running full memtest on your system? This will at least let us understand if it's hardware problem or not.

Additionally, your panic.log file will be very useful. To find it,
1. Go to Applications->Utilities->System Profiler
2. Expand Software group and select Logs.
3. Find panic.log file in the right pane. Attach it here. It may contain some useful technical info about the crash. It doesn't contain any private information.

 

Culprit found => IPv6 and VMWare Fusion

It may not be completely Fusion's fault, but after looking at the panic log and seeing panics all related to either networking or vmnet, I took a look at VMWare's Fusion board. It appears that there's been an issue with IPv6 and Fusion causing kernel panics. Strange thing is I've never experienced these issues before upgrading to 3188 in Parallels. The Fusion board isolated the issue to mounting/unmounting AFP and SMB volumes with IPv6 enabled on the Intel Mini and MBP (there might be others but those were the two I saw). The VMWare rep seemed confident that beta 2 would resolve that issue. It doesn't because that's what I have running here. Keep in mind that I was not running any Fusion VMs when these kernel panics occured. However, I cannot say with certainty that I had not run one at some point during my OS X session (IOW there may have been Fusion code in memory, though not active)

So I disabled IPv6 and tried to duplicate the kernel panic in Parallels as described above, and SUCCESS! No kernel panic! I'll be posting my finding to the Fusion board as well.

FWIW, here's my panic log:

panic.log:

Description: Panic (system crashes) log
Size: 11.41 KB
Last Modified: 3/28/07 1:04 AM
Location: /Library/Logs/panic.log
Recent Contents: ...
0x3657b9d8 : 0x233e82 (0x5208004 0x2 0x48785100 0x7bac804)
0x3657bb18 : 0x23b1bd (0x48785100 0x0 0x0 0x52241c8)
0x3657bc28 : 0x239783 (0x5224228 0x1 0x1 0x500a8c0)
0x3657be08 : 0x22e364 (0x48785100 0x14 0x3657be38 0x35c6aa)
0x3657be48 : 0x22fdc5 (0x48785100 0x14 0x6 0x0)
0x3657bf58 : 0x21d53a (0x48785100 0x48785100 0x44507c 0x1a3010)
0x3657bf98 : 0x203df7 (0x5208004 0x48785100 0x48785134 0x1)
0x3657bfc8 : 0x19ac1c (0x0 0x0 0x19e0b5 0x4c3c540) Backtrace terminated-invalid frame pointer 0x0
Kernel loadable modules in backtrace (with dependencies):
com.vmware.kext.vmnet(1.0.0d1)@0x62955000

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


*********

Fri Mar 23 23:16:30 2007
panic(cpu 0 caller 0x0035D913): freeing free mbuf
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x36483b68 : 0x128d08 (0x3cb134 0x36483b8c 0x131de5 0x0)
0x36483ba8 : 0x35d913 (0x3eb914 0x4b29870 0x36483be8 0x19a209)
0x36483be8 : 0x36301b (0x48230d00 0x297 0x36483c28 0x23cc66)
0x36483c28 : 0x239015 (0x51e11f8 0x1ef0 0x1 0x500a8c0)
0x36483e08 : 0x22e364 (0x483b8900 0x14 0x36483e38 0x35c6aa)
0x36483e48 : 0x22fdc5 (0x483b8900 0x14 0x6 0x0)
0x36483f58 : 0x21d53a (0x483b8900 0x483b8900 0x44507c 0x1a3010)
0x36483f98 : 0x203df7 (0x518f604 0x483b8900 0x483b8934 0x1)
0x36483fc8 : 0x19ac1c (0x0 0x0 0x19e0b5 0x54f0d08) Backtrace terminated-invalid frame pointer 0x0

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


*********

Sun Mar 25 20:00:07 2007
panic(cpu 0 caller 0x001A429B): Unresolved kernel trap (CPU 0, Type 14=page fault), registers:
CR0: 0x8001003b, CR2: 0xf95dc30d, CR3: 0x00e58000, CR4: 0x000006e0
EAX: 0xf95dc301, EBX: 0x051737b0, ECX: 0x48335f00, EDX: 0x465b57a0
CR2: 0xf95dc30d, EBP: 0x36513c28, ESI: 0x34a8c0b0, EDI: 0x00000000
EFL: 0x00010282, EIP: 0x0035afd5, CS: 0x00000008, DS: 0x48550010

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x36513a28 : 0x128d08 (0x3cb134 0x36513a4c 0x131de5 0x0)
0x36513a68 : 0x1a429b (0x3d0e4c 0x0 0xe 0x3d0670)
0x36513b78 : 0x19ada4 (0x36513b90 0xc0a8000b 0xc0a80004 0xc0000d3d)
0x36513c28 : 0x9fc7a9 (0xf95dc301 0x297 0x36513c78 0x35dae2)
0x36513ce8 : 0x9ff4fc (0x34a8c000 0x48568d00 0x853 0x1)
0x36513e98 : 0x9f8785 (0x34a8c000 0x4bf4580 0x40000000 0x0)
0x36513f08 : 0x39a463 (0x34a8c000 0x4bf4580 0x1 0x4acec14)
0x36513f58 : 0x399635 (0x4bf4580 0x0 0x36513f78 0x4b0038)
0x36513f88 : 0x39936b (0x4c03940 0x18 0x0 0xffffffff)
0x36513fc8 : 0x19ac1c (0x4c03940 0x0 0x19e0b5 0x55b6200) Backtrace terminated-invalid frame pointer 0x0
Kernel loadable modules in backtrace (with dependencies):
com.apple.iokit.AppleYukon(1.0.11b2)@0x9f2000
dependency: com.apple.iokit.IONetworkingFamily(1.5.1)@0x714000
dependency: com.apple.iokit.IOPCIFamily(2.2)@0x582000
dependency: com.apple.iokit.IOACPIFamily(1.2.0)@0x67a000

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


*********

Tue Mar 27 10:39:32 2007
panic(cpu 0 caller 0x0035C30A): mbuf address out of range 0x63654720
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x36533db8 : 0x128d08 (0x3cb134 0x36533ddc 0x131de5 0x0)
0x36533df8 : 0x35c30a (0x3eb8f4 0x63654720 0x487fdb00 0x35cc50)
0x36533e18 : 0x35c6aa (0x4872d400 0x1 0x36533e48 0x48908700)
0x36533e38 : 0x631bafef (0x4872d400 0x0 0x36533e68 0x0)
0x36533e78 : 0x631bc6b3 (0x54eb838 0x4872d400 0x36533ee8 0x134b11)
0x36533f08 : 0x631bca0e (0x48166100 0x0 0x0 0x48b0d000)
0x36533f48 : 0x203bd7 (0x5547900 0x5112204 0x2 0x36533fa4)
0x36533f98 : 0x203dba (0x5112204 0x48166100 0x48b0d000 0x1)
0x36533fc8 : 0x19ac1c (0x0 0x0 0x19e0b5 0x6117c80) Backtrace terminated-invalid frame pointer 0x0
Kernel loadable modules in backtrace (with dependencies):
com.vmware.kext.vmnet(1.0.0d1)@0x631b9000

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


*********

Wed Mar 28 01:04:38 2007
panic(cpu 0 caller 0x0035C30A): mbuf address out of range 0x8b919665
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x363b3db8 : 0x128d08 (0x3cb134 0x363b3ddc 0x131de5 0x0)
0x363b3df8 : 0x35c30a (0x3eb8f4 0x8b919665 0x48570800 0x35cc50)
0x363b3e18 : 0x35c6aa (0x482d7900 0x1 0x363b3e48 0x482c7a00)
0x363b3e38 : 0x6345dfef (0x482d7900 0x0 0x363b3e68 0x0)
0x363b3e78 : 0x6345f6b3 (0x592b038 0x482d7900 0x363b3ee8 0x134b11)
0x363b3f08 : 0x6345fa0e (0x489f7400 0x0 0x0 0x48452000)
0x363b3f48 : 0x203bd7 (0x5957500 0x5594c04 0x2 0x363b3fa4)
0x363b3f98 : 0x203dba (0x5594c04 0x489f7400 0x48452000 0x1)
0x363b3fc8 : 0x19ac1c (0x0 0x0 0x19e0b5 0x4c2a160) Backtrace terminated-invalid frame pointer 0x0
Kernel loadable modules in backtrace (with dependencies):
com.vmware.kext.vmnet(1.0.0d1)@0x6345c000

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


*********

 

Huh. Fusion and Parallels don't play nice. Wonder if they designed that...

 

Build 3188 - Kernel Panic

I've recently updated my Parallels to Build 3188 and it's worked great. However, I have just received a kernel panic error, "Unresolved kernel trap (CPU 1, Type 27=Unknown)" on my MacBookPro running OS X, 10.4.9.
MacBookPro, Core2Duo, 2 GB RAM

Open apps:
Firefox 2.0.0.1
Stickies
McAfee running in background
Parallels starts loading...<ERROR!>

Followed instructions for panic.log:

panic(cpu 1 caller 0x001A429B): Unresolved kernel trap (CPU 1, Type 27=Unknown), registers:
CR0: 0x80010033, CR2: 0x3f9b6000, CR3: 0x00e5f000, CR4: 0x000006e0
EAX: 0x00000001, EBX: 0x6d626572, ECX: 0x00000000, EDX: 0x00000000
CR2: 0x3f9b6000, EBP: 0x251c3978, ESI: 0x6d616769, EDI: 0x63216e75
EFL: 0x00000246, EIP: 0x3b5b07b2, CS: 0x00000008, DS: 0x042d0010

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x251c36e8 : 0x128d08 (0x3cb134 0x251c370c 0x131de5 0x0)
0x251c3728 : 0x1a429b (0x3d0e4c 0x1 0x1b 0x3ca5fc)
0x251c3838 : 0x19ada4 (0x251c3850 0x3b6392c1 0xffffffff 0x10)
0x251c3978 : 0x3b5afce9 (0x3b117000 0x3ec4804 0x3818404 0x251c3eb8)
0x251c3aa8 : 0x9acdc7 (0x3b117000 0x0 0x0 0x9ab244)
0x251c3b18 : 0x9ad054 (0x3818404 0x251c3eb8 0x200000 0x199193)
0x251c3bd8 : 0x9ad862 (0x3818404 0x251c3eb8 0x18 0x0)
0x251c3d38 : 0x9aa8c7 (0x3818404 0xc0185401 0x251c3eb8 0x19e23a)
0x251c3d68 : 0x1f05d7 (0xd000000 0xc0185401 0x251c3eb8 0x81)
0x251c3da8 : 0x1e7411 (0x251c3dd0 0x297 0x251c3e08 0x40e31f4)
0x251c3e08 : 0x1df212 (0x43ad738 0xc0185401 0x251c3eb8 0x81)
0x251c3e58 : 0x331c4c (0x4232450 0xc0185401 0x251c3eb8 0x40e31f4)
0x251c3e88 : 0x34ffa8 (0x4232450 0xc0185401 0x251c3eb8 0x40e31f4)
0x251c3f58 : 0x379e23 (0x40e31f4 0x419d5f8 0x419d63c 0x0)
0x251c3fc8 : 0x19b17e (0x4101000 0x0 0x19e0b5 0x393b820) No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xbfffe038
Kernel loadable modules in backtrace (with dependencies):
com.parallels.kext.vmmain(2.2)@0x9a9000

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: 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: AirPort Extreme, 1.0.47
Bluetooth: Version 1.7.14f14, 2 service, 0 devices, 1 incoming serial ports
Network Service: Built-in Ethernet, Ethernet, en0
Network Service: Parallels Host-Guest, Ethernet, en3
Network Service: Parallels NAT, Ethernet, en4
Serial ATA Device: Hitachi HTS541616J9SA00, 149.05 GB
Parallel ATA Device: HL-DT-ST DVDRW GWA4080MA
USB Device: Built-in iSight, Micron, Up to 480 Mb/sec, 500 mA
USB Device: Bluetooth HCI, Up to 12 Mb/sec, 500 mA
USB Device: IR Receiver, Apple Computer, 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: Optical USB Mouse, Logitech, Up to 1.5 Mb/sec, 500 mA


Error has not repeated and system works fine now. Just thought I'd let you know that it happened and am hoping you can tell me why. Thanks. rdinsd