RC: Lockups after sleep or network location change continue

I am still experiencing my 2 favourite freezes/lockups with the release candidate.

- After the MBP sleeps with Win XP running Parallels is locked up with the spinning color wheel.

- If I change network locations in MacOS from a wired only setup to a wireless only setup WinXP will freeze. If I try to stop it by quitting Parallels or using the "Power Off Virtual Machine" Parallels will lock up with the spinning color wheel.

In either case I need to Force Quit Parallels.

 

I just noticed this myself. Whenever I change Location, Parallels (XP SP2 guest) hangs - the entrire app, it needs to be terminated with Force Quit.

I am using Host-only networking, and made sure that the settings of the Parallels Host-Guest adapter are identical in all Locations. I have a fixed IP address for the Host-Guest adapter as well as for the XP Guest. I have internet sharing enabled for the en2 adapter.

I however don't have this problem (neither with beta6 nor RC1) - it comes fine out of sleep.

Edit: Oops - just now after playing a bit with Location change to verify the above, Parallels crashed the entire machine after I closed the lid of the MBP. I had to hard reset it.

The crash log reports (let me know if you need the entire log):

...
0x24eabea8 : 0x3439a5 (0x4b57ac0 0xc0045408 0x24eabed8 0x3f827d0)
0x24eabf78 : 0x36da40 (0x3f827d0 0x373ef3c 0x373ef80 0x0)
0x24eabfd8 : 0x197f03 (0x37ef030 0x37ef030 0x24eabbdc 0x24eabb4c) Backtrace continues...
Kernel loadable modules in backtrace (with dependencies):
com.parallels.kext.hypervisor(2.1)@0x697000
...

 

Some more pattern data (but from beta 6)

Sorry in case this is already improved in RC1 over beta6 (but the report of the original poster suggests that not). I'm using beta6 at this time rather than RC1 because of the keyboard mapping and global key handling issues.

The pattern (for me) seems to be that changing Location locks up Parallels (spinning beach ball of death), so I have to force quit it. I can then start Parallels again (without rebooting the Mac), and it works fine, including network.
But the next time the Mac is put to sleep, it will completely crash with a kernel panic while going to sleep. I've seen this now three times in exactly the same sequence.

The kernel panic data (this time in full) seems to be identical as well:

panic(cpu 0 caller 0x0019C9EF): Unresolved kernel trap (CPU 0, Type 13=general protection), registers:
CR0: 0x8001003b, CR2: 0x000e0000, CR3: 0x00da1000, CR4: 0x000026e0
EAX: 0x000006e0, EBX: 0x00000000, ECX: 0x00000001, EDX: 0x03da6a04
ESP: 0x24e13c0c, EBP: 0x24e13c48, ESI: 0x00000000, EDI: 0x00000202
EFL: 0x00010006, EIP: 0x0069b1b3, CS: 0x00000014, DS: 0x24e1001c

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x24e13ad8 : 0x128b5e (0x3bbf84 0x24e13afc 0x131bbc 0x0)
0x24e13b18 : 0x19c9ef (0x3c13b4 0x0 0xd 0x3c1158)
0x24e13bc8 : 0x197b8d (0x24e13bdc 0x24e13c48 0x69b1b3 0x3b10048)
0x24e13bd4 : 0x69b1b3 (0x3b10048 0x390001c 0x1c 0x24e1001c)
0x24e13c48 : 0x698915 (0x0 0x24e13d24 0x6d142b 0x38c6c40)
0x24e13cf8 : 0x69b0c9 (0x69b109 0x0 0x3ae14e 0x38c9c00)
0x24e13d18 : 0x69b1fe (0x3ba4be0 0x24e13d54 0x6cfd33 0x38c6b80)
0x24e13d38 : 0x699952 (0x3b48070 0x24e13d64 0x3834100 0x37ecf40)
0x24e13d68 : 0x698567 (0x0 0xc0045408 0x24e13ed8 0x3738940)
0x24e13d88 : 0x1e3d72 (0xb000000 0xc0045408 0x24e13ed8 0x81)
0x24e13dc8 : 0x1dac2e (0x24e13df0 0x297 0x24e13e28 0x1c4423)
0x24e13e28 : 0x1d29c3 (0x49fff78 0xc0045408 0x24e13ed8 0x81)
0x24e13e78 : 0x3255fb (0x456bcb0 0xc0045408 0x24e13ed8 0x390b1f4)
0x24e13ea8 : 0x3439a5 (0x456bcb0 0xc0045408 0x24e13ed8 0x390b1f4)
0x24e13f78 : 0x36da40 (0x390b1f4 0x433e40c 0x433e450 0x0)
0x24e13fd8 : 0x197f03 (0x43604f8 0x43604f8 0x24e13bdc 0x24e13b4c) Backtrace continues...
Kernel loadable modules in backtrace (with dependencies):
com.parallels.kext.hypervisor(2.1)@0x697000

Kernel version:
Darwin Kernel Version 8.6.2: Thu Apr 13 18:48:29 PDT 2006; root:xnu-792.9.59.obj~1/RELEASE_I386

Model: MacBookPro1,2, BootROM MBP12.0061.B00, 2 processors, Intel Core Duo, 2.16 GHz, 2 GB
Graphics: ATI Radeon X1600, ATY,RadeonX1600, PCIe, 256 MB
Memory Module: DIMM0/BANK 0, 1 GB, DDR2 SDRAM, 667 MHz
Memory Module: DIMM1/BANK 1, 1 GB, DDR2 SDRAM, 667 MHz
AirPort: spairport_wireless_card_type_airport_extreme (0x168C, 0x86), 0.1.20
Bluetooth: Version 1.7.4f16, 2 service, 0 devices, 1 incoming serial ports
Network Service: Built-in Ethernet, Ethernet, en0
Network Service: AirPort, AirPort, en1
Network Service: Parallels Host-Guest Adapter, Ethernet, en2
Serial ATA Device: ST9120821AS, 111.79 GB
Parallel ATA Device: MATSHITADVD-R UJ-846
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

 

RC2: still Lockups/crashes after Network Location change

I'm now using RC2 (which is really a great improvement over RC1 ).

But still, changing the Network Location causes Mac OS to crash.

The picture has changed a bit however: in RC2 I can switch the Location without an immediate crash - but when the Mac (MBP 17") is put to sleep later (even hours of successful VM network operation later!), it invariably causes Mac OS to crash somehow. The crash type has changed a bit as well - while I always got a kernel panic in Beta 6, it now simply rebooted the Mac when I chose "Sleep" from the menu. No message, no Kernel panic dump.

I am using Host-Only networking with fixed IP in VM (and fixed IP in a 10.x/16 network for the en2 adapter, manually set in System Preferences for each Location's instance of the Parallels adapter, and internet sharing turned on for en2).

 

I have the same issue. PDM will freeze with the XP screen saver displayed. It seems to happen after sleeping. But, not always in conjuction with changing network locations. I have to force quit PDM twice. For some reason, the first force quit never takes. After the second force quit, I restart PDM and it works fine. I am using RC2 on a MacBook Pro.