Fusion 1.1 final panics OS X 10.4.10 (8R4049)

[edwingo]

I upgraded to Fusion 1.1 Final and now I'm getting a kernel panic when I start a virtual machine. It looks similar to http://communities.vmware.com/thread/109344?tstart=0&start=17. I would have thought that the final release would have the fix that was in the patch to RC1 in it. Any ideas?

panic.log is:

*********
Wed Nov 14 14:42:37 2007
panic(cpu 0 caller 0x001A4A55): Unresolved kernel trap (CPU 0, Type 14=page fault), registers:
CR0: 0x80010033, CR2: 0x00000040, CR3: 0x013ac000, CR4: 0x000006e0
EAX: 0x00000040, EBX: 0x0418b000, ECX: 0x04970000, EDX: 0x000007a0
CR2: 0x00000040, EBP: 0x257c3cc8, ESI: 0x046e6800, EDI: 0x00010000
EFL: 0x00010202, EIP: 0x54350e5a, CS: 0x00000008, DS: 0x00460010
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x257c3a88 : 0x128d08 (0x3cc0ec 0x257c3aac 0x131de5 0x0)
0x257c3ac8 : 0x1a4a55 (0x3d2524 0x0 0xe 0x3d1d48)
0x257c3bd8 : 0x19aeb4 (0x257c3bf0 0x10001 0x4181544 0x0)
0x257c3cc8 : 0x54350fec (0x46e6800 0x418b000 0x3f81d80 0x3be36c)
0x257c3cf8 : 0x5435116b (0x46e6800 0x3f81d80 0x0 0x3bd59000)
0x257c3d28 : 0x3b2505 (0x46e6800 0x3f8a180 0x78 0x3bef8f)
0x257c3d78 : 0x18a8a4 (0x46e6800 0x48eaa00 0x78 0x4729ac8)
0x257c3db8 : 0x12b4c3 (0x4b2d598 0x4729aa4 0x257c3df8 0x11e042)
0x257c3df8 : 0x124b17 (0x4b2d500 0x3ece8f0 0x496a708 0x0)
0x257c3f08 : 0x195a42 (0x257c3f44 0x0 0x0 0x0)
0x257c3fc8 : 0x19b32e (0x49fe000 0x0 0x19e0b5 0x49ffa40) No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xb0182788
Kernel loadable modules in backtrace (with dependencies):
com.vmware.kext.vmioplug(1.1)@0x5434e000
dependency: com.apple.iokit.IOHIDFamily(1.4.11)@0x5ab000
dependency: com.apple.iokit.IOUSBFamily(2.7.7)@0x58a000
Kernel version:
Darwin Kernel Version 8.10.3: Wed Jun 27 23:29:36 PDT 2007; root:xnu-792.23.3~1/RELEASE_I386
*********

[gomanjorge]

edwingo

OS X 10.4.11 has been released on Software Update.

http://docs.info.apple.com/article.html?artnum=306297

Among the modifications included you can find:

"Improves reliability when running VMWARE's Fusion"

I haven't found any more details.

Maybe you could try updating to 10.4.11

Good Luck!

[edwingo]

I tried the Mac OS X update but it did not help. The new panic.log file is:

*********
Wed Nov 14 16:56:05 2007
panic(cpu 0 caller 0x001A49CB): Unresolved kernel trap (CPU 0, Type 14=page fault), registers:
CR0: 0x80010033, CR2: 0x00000040, CR3: 0x01307000, CR4: 0x000006e0
EAX: 0x00000040, EBX: 0x040f8c00, ECX: 0x04770800, EDX: 0x000007a0
CR2: 0x00000040, EBP: 0x258d3cc8, ESI: 0x0464c800, EDI: 0x00010000
EFL: 0x00010202, EIP: 0x3b7c6e5a, CS: 0x00000008, DS: 0x00460010
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x258d3a88 : 0x128d0d (0x3cc65c 0x258d3aac 0x131f95 0x0)
0x258d3ac8 : 0x1a49cb (0x3d2a94 0x0 0xe 0x3d22b8)
0x258d3bd8 : 0x19b3a4 (0x258d3bf0 0x10001 0x40e7284 0x0)
0x258d3cc8 : 0x3b7c6fec (0x464c800 0x40f8c00 0x43c2f40 0x3be8dc)
0x258d3cf8 : 0x3b7c716b (0x464c800 0x43c2f40 0x0 0x3b570000)
0x258d3d28 : 0x3b2a75 (0x464c800 0x43d9f80 0x78 0x3bf4ff)
0x258d3d78 : 0x18aacf (0x464c800 0x49eb100 0x78 0x4d33dc8)
0x258d3db8 : 0x12b4ee (0x44f5398 0x4d33da4 0x258d3df8 0x11e042)
0x258d3df8 : 0x124b17 (0x44f5300 0x3e2a188 0x4657f34 0x0)
0x258d3f08 : 0x195f2e (0x258d3f44 0x0 0x0 0x0)
0x258d3fc8 : 0x19b81e (0x4955300 0x0 0x10 0x4955300) No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xb0182788
Kernel loadable modules in backtrace (with dependencies):
com.vmware.kext.vmioplug(1.1)@0x3b7c4000
dependency: com.apple.iokit.IOHIDFamily(1.4.13)@0x557000
dependency: com.apple.iokit.IOUSBFamily(2.7.7)@0x536000
Kernel version:
Darwin Kernel Version 8.11.1: Wed Oct 10 18:23:28 PDT 2007; root:xnu-792.25.20~1/RELEASE_I386
*********

Can I use the patched vmware-vmx and vmware-vmx-debug files with Fusion 1.1 Final or does it only work with 1.1 RC1?

-Edwin

[edwingo]

At one time I had something working, but I cannot seem to revert to the same state :-(. Fusion still causes a kernel panic. I uninstalled Fusion 1.1 Final and reinstalled Fusion 1.1 RC1 and applied the patch described in http://communities.vmware.com/thread/109344?tstart=0&start=17. However, my MacBook Pro is at Mac OS X 10.4.11 (8S2167). Is there a way to revert to the previous version of OS X? Any suggestions?

The latest panic.log is:

*********
Wed Nov 14 18:20:16 2007
panic(cpu 1 caller 0x001A49CB): Unresolved kernel trap (CPU 1, Type 14=page fault), registers:
CR0: 0x80010033, CR2: 0x00000040, CR3: 0x01307000, CR4: 0x000006e0
EAX: 0x00000040, EBX: 0x0412dc00, ECX: 0x04865000, EDX: 0x000007a0
CR2: 0x00000040, EBP: 0x2573bcc8, ESI: 0x04672a00, EDI: 0x00010000
EFL: 0x00010202, EIP: 0x54fdfe5a, CS: 0x00000008, DS: 0x00460010
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x2573ba88 : 0x128d0d (0x3cc65c 0x2573baac 0x131f95 0x0)
0x2573bac8 : 0x1a49cb (0x3d2a94 0x1 0xe 0x3d22b8)
0x2573bbd8 : 0x19b3a4 (0x2573bbf0 0x10001 0x411a104 0x0)
0x2573bcc8 : 0x54fdffec (0x4672a00 0x412dc00 0x43b5e40 0x3be8dc)
0x2573bcf8 : 0x54fe016b (0x4672a00 0x43b5e40 0x0 0x3bb1d000)
0x2573bd28 : 0x3b2a75 (0x4672a00 0x4283300 0x78 0x3bf4ff)
0x2573bd78 : 0x18aacf (0x4672a00 0x47da100 0x78 0x4c5f5c8)
0x2573bdb8 : 0x12b4ee (0x4664498 0x4c5f5a4 0x2573bdf8 0x11e042)
0x2573bdf8 : 0x124b17 (0x4664400 0x3e29d68 0x1a357d0 0x0)
0x2573bf08 : 0x195f2e (0x2573bf44 0x0 0x0 0x0)
0x2573bfc8 : 0x19b81e (0x4902c80 0x1 0x19e0b5 0x4902c80) No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xb0182788
Kernel loadable modules in backtrace (with dependencies):
com.vmware.kext.vmioplug(1.1fc1)@0x54fdd000
dependency: com.apple.iokit.IOHIDFamily(1.4.13)@0x557000
dependency: com.apple.iokit.IOUSBFamily(2.7.7)@0x536000
Kernel version:
Darwin Kernel Version 8.11.1: Wed Oct 10 18:23:28 PDT 2007; root:xnu-792.25.20~1/RELEASE_I386
*********

-Edwin

[HPReg]

edwingo,

Yes, what you hit seems to be another flavor of the same problem.

"Can I use the patched vmware-vmx and vmware-vmx-debug files with Fusion 1.1": doing so will not help. The code which is in these patched binaries is the code that was shipped in the final Fusion 1.1. So you are already running this code.

Let's do 2 things:

1) I want to gather info about your system

Can you please run this command in a Terminal, and send me the file

for_hpreg.tar.bz2 (look for it on your desktop) at

hpreg@you_know_the_company.com?

tar -C /System/Library/Extensions -cjf ~/Desktop/for_hpreg.tar.bz2 IOHIDFamily.kext

2) Please make sure that your Fusion 1.1 installation is unmodified. If needed, uninstall Fusion with its uninstaller in /Library/Application Support/VMware Fusion, then re-install it.

Try again. If the problem still happens, then restart Mac OS (very important), then put this line in the .vmx file of any VMs you want to run:

mks.keyboard.offset0.doNotLookup = TRUE

Then try again running that VM. The panic should not happen anymore (but your host will not always reflect the guest's Caps Lock state. You might not care if you don't use Caps Lock in the guest). Once I have received the info in #1, I might give you another line to put in your .vmx file, to restore the Caps Lock reflection functionality.

Thanks!

[edwingo]

Hey thanks! #2 fixed the kernel panic. Since I'm used to using old unix keyboards, I set the "caps lock" key to be a "control" key on my MacBook Pro, so this might be related to the problem. I've attached the output of #1 to this reply. I guess there is still a bug since users should not have to modify the vmx file but the workaround works for me. There was another problem with installing Solaris in 32-bit mode where I had to add "monitor_control.disable_longmode = 1" to the vmx file too. Hopefully, that's fixed. Thanks for your help.

[HPReg]

edwingo,

I look ed at #1 you attached, and it is bit-for-bit the same IOHIDFamily (version 1.4.13) I'm running here. So I don't understand why Fusion panics on your machine and not on mine

Anyway, I'm glad #2 was useful to you. The Caps Lock remapping should not have anything to do with this.

Wrt Solaris 32-bit, this is a Solaris bug not a Fusion bug. The exact same problem would happen if you tried to install Solaris 32-bit on a physical 64-bit box. But what you applied is a valid workaround. IIRC, you only need the workaround to install the OS though. After that, you can remove the workaround.

[ztomasi]

Hi HPReg,

after upgrading directly from Fusion 1.0 to 1.1 final I've got many kernel panic (see attached file) when I press Caps Lock key on my USB attached Logitech Keyboard.

• Host: MacBook Core Duo 2.0 ghz with MacOS 10.4.11

• Guest: Win XP Pro SP2

Do I have to put the line ks.keyboard.offset0.doNotLookup = TRUE in my VM.vms file?

Thanks in advance!

[admin]

Do I have to put the line ks.keyboard.offset0.doNotLookup = TRUE in my VM.vms file?

Yes, please try that.

[rcardona2k]

Your panic.log looks similar enough to the second one above to try the setting. Keep in mind the limitation Regis pointed out, but it would be useful to have another data point that .vmx file setting avoids the kernel panic.

[ztomasi]

Hi,

I've put the line in my VM.vms file, now all seems to be OK!

Thanks a lot!

[bgertzfield]

Hi folks,

The fix for this issue is now available in VMware Fusion 1.1.1, now available for free download:

http://www.vmware.com/download/fusion/

We disabled the keyboard LED synchronization code that was causing issues with some Logitech drivers.