Trying to figure out if what I have is a known problem, I have read some of the other posts about kernel panics but this stuff is always a mystery to me. Last night I finally downloaded the upgrade from 1.0 to 1.1 and during my first session I had a kernel panic. I was doing anything particularly interesting. After upgrading, I booted up my Home Edition of Windows XP (up to date and current) and every thing seemed to be fine. I upgraded the vmware tools with no problems. I ran a work program which uses .NET Framework version 2.0 that does secure access to a remote site with no problems. I closed that program and ran a AutoHotKey script to do some typing using an alternate keyboard layout I use to touch type (http://colemak.com/AutoHotKey). I have been using that script since beta without any problems and things seemed okay. I was running a program called Human Japanese for at least ten minutes with no apparent problems and that I have run on 1.0 with no problems before this. I was simply reading at the time kernel panic occurred forcing me to reboot and repair the boot partition. I have used VMWare Fusion since the first beta and this is the first time I have had such a bad crash. I am afraid to use this now if I can't find out exactly why this happened. Really regretting upgrading now. 1.0 was working just fine on OS X 10.4.11 . If this is obvious and known and some of this fix on another thread will work I would love to confirm that. Thanks in advance.
Mon Nov 26 02:27:30 2007 crashdump: crashdump invoked as panicdump
Mon Nov 26 02:35:22 2007 crashdump: crashdump started
2007-11-26 02:35:22.422 crashdump thread_read_stack: stack appears to be in inconsistent state to trace. Truncating stack.
Mon Nov 26 02:27:30 2007
panic(cpu 0 caller 0x001A49CB): Unresolved kernel trap (CPU 0, Type 14=page fault), registers:
CR0: 0x80010033, CR2: 0x00000040, CR3: 0x017a2000, CR4: 0x000006e0
EAX: 0x00000040, EBX: 0x03678400, ECX: 0x042af800, EDX: 0x000007a0
CR2: 0x00000040, EBP: 0x190b3cb8, ESI: 0x05db2100, EDI: 0x00000000
EFL: 0x00010246, EIP: 0x33fdee64, CS: 0x00000008, DS: 0x190b0010
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x190b3ac8 : 0x128d0d (0x3cc65c 0x190b3aec 0x131f95 0x0)
0x190b3b08 : 0x1a49cb (0x3d2a94 0x0 0xe 0x3d22b8)
0x190b3c18 : 0x19b3a4 (0x190b3c28 0x534c340 0xe 0x3670048)
0x190b3cb8 : 0x33fdef6d (0x5db2100 0x3678400 0x534c340 0x190b3cdc)
0x190b3cf8 : 0x33fdf1c9 (0x5db2100 0x561c1c0 0x0 0x31235000)
0x190b3d28 : 0x3b2a75 (0x5db2100 0x5cf0a00 0x53 0x3bf4ff)
0x190b3d78 : 0x18aacf (0x5db2100 0x5ae2f00 0x53 0x54f80c8)
0x190b3db8 : 0x12b4ee (0x4fb1c98 0x54f80a4 0x190b3df8 0x11e042)
0x190b3df8 : 0x124b17 (0x4fb1c00 0x34f8760 0x5a37584 0x0)
0x190b3f08 : 0x195f2e (0x190b3f44 0x0 0x0 0x0)
0x190b3fc8 : 0x19b81e (0x486d33c 0x0 0x19e0b5 0x486d33c) No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xb0182748
Kernel loadable modules in backtrace (with dependencies):
Darwin Kernel Version 8.11.1: Wed Oct 10 18:23:28 PDT 2007; root:xnu-792.25.20~1/RELEASE_I386
I saw that solution and it seems to work around whatever the problem is by making the Caps Lock unusable and the layout I favor uses that as a backspace delete key making it much more useful. If that hack is what I have to do to avoid a kernel panic I will do it, but it's certainly not a long term solution.
Caps lock should still be usable, we just won't synchronize state between guest and host (e.g. the guest might have capslock on, but the host might not). I'm not sure how it'll interact with your remapped keys (I doubt it'll matter), but definitely try it.