VMware Communities
gglockner
Contributor
Contributor
Jump to solution

Kernel panics and support

First the technical issue: I am testing VMWare Fusion on an iMac with the following configuration:

Hardware Overview:

Machine Name: iMac

Machine Model: iMac5,1

Processor Name: Intel Core 2 Duo

Processor Speed: 2.16 GHz

Number Of Processors: 1

Total Number Of Cores: 2

L2 Cache (per processor): 4 MB

Memory: 2 GB

Bus Speed: 667 MHz

Boot ROM Version: IM51.0090.B03

SMC Version: 1.9f4

Serial Number: YD7020ETVUV

System Software Overview:

System Version: Mac OS X 10.4.9 (8P2137)

Kernel Version: Darwin 8.9.1

Boot Volume: Greg's HD

Computer Name: Gregory Glockner’s Computer

User Name: Gregory Glockner (greg)

I have some experience with VMWare Workstation and VMWare Server on Windows, though I am relatively new to Mac. When I first install VMWare Fusion build 41385, OS X would give a kernel panic before a Virtual Machine is loaded. I followed the advice on the discussion forum to disable IPv6, which helped for a while, but eventually OS X would give a kernel panic. What's even more troubling is that after the first kernel panic, the machine keeps causing kernel panics upon login to OS X. The only way to fix this is to boot into safe mode and uninstall VMWare Fusion.

Here is an example of the logs from the kernel panic.

\*********

Fri Mar 30 01:13:20 2007

panic(cpu 1 caller 0x0035C30A): mbuf address out of range 0x77202b20

Backtrace, Format - Frame : Return Address (4 potential args on stack)

0x25113bb8 : 0x128d08 (0x3cb134 0x25113bdc 0x131de5 0x0)

0x25113bf8 : 0x35c30a (0x3eb8f4 0x77202b20 0x0 0x34baba)

0x25113c18 : 0x35c6aa (0x36ef8100 0x3be4b7d4 0x6 0x4b76d00)

0x25113c38 : 0x3be447e3 (0x36ef8100 0x4b76d40 0x4b76d46 0x43)

0x25113c98 : 0x3be44058 (0x4b76d00 0x36ef8100 0x25113cbc 0x33683e)

0x25113cd8 : 0x3be44850 (0x4b66838 0x36ef8100 0x3360a1 0x33671d)

0x25113cf8 : 0x3360c6 (0x4b55900 0x36ef8100 0x0 0x36ef8100)

0x25113d38 : 0x361033 (0x3ec0ee8 0x0 0x36ef8100 0x0)

0x25113dd8 : 0x35342d (0x3ec0ee8 0x0 0x25113e9c 0x36ef8100)

0x25113e08 : 0x34f370 (0x4554bb0 0x25113e9c 0x490cf04 0x0)

0x25113ef8 : 0x34f604 (0x4a7c3e8 0x4554bb0 0x3 0x18014ae)

0x25113f58 : 0x379e23 (0x4a7c3e8 0x4a8e280 0x4a8e2c4 0x0)

0x25113fc8 : 0x19b17e (0x4a88d20 0x0 0x19e0b5 0x403ea2c) No mapping exists for frame pointer

Backtrace terminated-invalid frame pointer 0xbffff1e8

Kernel loadable modules in backtrace (with dependencies):

com.vmware.kext.vmnet(1.0.0d1)@0x3be42000

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 30 01:14:42 2007

panic(cpu 0 caller 0x001A429B): Unresolved kernel trap (CPU 0, Type 14=page fault), registers:

CR0: 0x8001003b, CR2: 0x370e7000, CR3: 0x00dcf000, CR4: 0x000006e0

EAX: 0x36e6f000, EBX: 0x36fada00, ECX: 0x00000200, EDX: 0x00001000

CR2: 0x370e7000, EBP: 0x252d3e58, ESI: 0x36e6f800, EDI: 0x370e7000

EFL: 0x00010206, EIP: 0x0019637c, CS: 0x00000008, DS: 0x03920010

Backtrace, Format - Frame : Return Address (4 potential args on stack)

0x252d3c08 : 0x128d08 (0x3cb134 0x252d3c2c 0x131de5 0x0)

0x252d3c48 : 0x1a429b (0x3d0e4c 0x0 0xe 0x3d0670)

0x252d3d58 : 0x19ada4 (0x252d3d70 0x3927d74 0x252d3db8 0x197c2c)

0x252d3e58 : 0x34b981 (0x36e04e00 0x1 0x4b0c9c 0x199ef1)

0x252d3e78 : 0x51921626 (0x36e04e00 0x1 0x252d3ee8 0x134b11)

0x252d3f08 : 0x51921a0e (0x36e04e00 0x0 0x0 0x36e6f000)

0x252d3f48 : 0x203bd7 (0x3e8ed80 0x4014804 0x2 0x252d3fa4)

0x252d3f98 : 0x203dba (0x4014804 0x36e04e00 0x36e6f000 0x1)

0x252d3fc8 : 0x19ac1c (0x0 0x0 0x19e0b5 0x3a81c80) Backtrace terminated-invalid frame pointer 0x0

Kernel loadable modules in backtrace (with dependencies):

com.vmware.kext.vmnet(1.0.0d1)@0x5191e000

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 30 01:16:13 2007

panic(cpu 0 caller 0x001A429B): Unresolved kernel trap (CPU 0, Type 14=page fault), registers:

CR0: 0x8001003b, CR2: 0x0000000c, CR3: 0x00dcf000, CR4: 0x000006e0

EAX: 0x00000000, EBX: 0x237e1000, ECX: 0x237e10b0, EDX: 0x00000000

CR2: 0x0000000c, EBP: 0x252abe98, ESI: 0x006ff692, EDI: 0x0000797d

EFL: 0x00010202, EIP: 0x009ff104, CS: 0x00000008, DS: 0x36f80010

Backtrace, Format - Frame : Return Address (4 potential args on stack)

0x252abaf8 : 0x128d08 (0x3cb134 0x252abb1c 0x131de5 0x0)

0x252abb38 : 0x1a429b (0x3d0e4c 0x0 0xe 0x3d0670)

0x252abc48 : 0x19ada4 (0x252abc60 0x206 0x0 0x36f8bc00)

0x252abe98 : 0x9f9785 (0x237e1000 0x3a61080 0x40000000 0x1a3010)

0x252abf08 : 0x39a463 (0x237e1000 0x3a61080 0x1 0x3920364)

0x252abf58 : 0x399635 (0x3a61080 0x3a523d8 0x252abf78 0x4b0038)

0x252abf88 : 0x39936b (0x3a1a7c0 0x1d2718 0x452bc4 0xffffffff)

0x252abfc8 : 0x19ac1c (0x3a1a7c0 0x0 0x19e0b5 0x3a8dae0) Backtrace terminated-invalid frame pointer 0x0

Kernel loadable modules in backtrace (with dependencies):

com.apple.iokit.AppleYukon(1.0.11b2)@0x9f3000

dependency: com.apple.iokit.IONetworkingFamily(1.5.1)@0x6f8000

dependency: com.apple.iokit.IOPCIFamily(2.2)@0x57f000

dependency: com.apple.iokit.IOACPIFamily(1.2.0)@0x672000

Kernel version:

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

\*********

Now for the rant: I have had NO success in resolving this issue. I tried to email fusion_support AT xxxxx and it bounced. I tried to post to this forum but no one bothered to reply. Now I'm posting as a question. You would think that SOMEONE would care about the fact that Fusion causes a kernel panic that makes the system unusable upon reboot. Sorry to rant about this but this is a serious issue. And it's a shame since I have had nothing but excellent experiences with VMWare Server on Windows and VMWare Workstation on Windows. And my employer uses VMWare ESX for a variety of projects.

0 Kudos
27 Replies
admin
Immortal
Immortal
Jump to solution

Awesome! Just what I was looking for!

Could I ask for another favour? If you don't mind sending your /var/log/system.log (sanitized if there's any private information you don't want to share) from around the time of the kernel panic?

Thanks for all your help in getting to the bottom of this issue! I can assure you that we'll have this fixed pretty soon so jumbo frames don't cause such kernel panics in the VMware vmnet kext.

0 Kudos
gglockner
Contributor
Contributor
Jump to solution

bhaveshdavda:

The attachment contains the system.log at the time of the two latest kernel panics. Below is the contents of panic.log. Two kernel panics occurred: one at Sat Apr 21 22:59:18 2007, the other at Sat Apr 21 23:02:21 2007. Although vmnet is not listed in the first kernel panic, I believe it is part of the problem since I have never had a kernel panic when Fusion was not installed.

Thanks, Greg.

Sat Apr 21 22:59:18 2007

panic(cpu 0 caller 0x001A429B): Unresolved kernel trap (CPU 0, Type 14=page fault), registers:

CR0: 0x8001003b, CR2: 0x86885099, CR3: 0x00dad000, CR4: 0x000006e0

EAX: 0x8688508d, EBX: 0x03f6c0d8, ECX: 0x36ee0800, EDX: 0x3ae67088

CR2: 0x86885099, EBP: 0x252ebc28, ESI: 0x2393e0b0, EDI: 0x00000000

EFL: 0x00010286, EIP: 0x0035afd5, CS: 0x00000008, DS: 0x00000010

Backtrace, Format - Frame : Return Address (4 potential args on stack)

0x252eba28 : 0x128d08 (0x3cb134 0x252eba4c 0x131de5 0x0)

0x252eba68 : 0x1a429b (0x3d0e4c 0x0 0xe 0x3d0670)

0x252ebb78 : 0x19ada4 (0x252ebb90 0x0 0x0 0x19e23a)

0x252ebc28 : 0x9db7a9 (0x8688508d 0x1f66 0x0 0x1)

0x252ebce8 : 0x9de4fc (0x3a1df00 0x36f22300 0x1f4e 0x1)

0x252ebe98 : 0x9d7785 (0x2393e000 0x3a0b480 0x40000000 0x3903b8c)

0x252ebf08 : 0x39a463 (0x2393e000 0x3a0b480 0x1 0x3903b8c)

0x252ebf58 : 0x399635 (0x3a0b480 0x135eb4 0x0 0x3903b8c)

0x252ebf88 : 0x39936b (0x3a188c0 0x252ebfd4 0x134c09 0x135eb4)

0x252ebfc8 : 0x19ac1c (0x3a188c0 0x0 0x19e0b5 0x4230a2c) Backtrace terminated-invalid frame pointer 0x0

Kernel loadable modules in backtrace (with dependencies):

com.apple.iokit.AppleYukon(1.0.11b2)@0x9d1000

dependency: com.apple.iokit.IONetworkingFamily(1.5.1)@0x6eb000

dependency: com.apple.iokit.IOPCIFamily(2.2)@0x572000

dependency: com.apple.iokit.IOACPIFamily(1.2.0)@0x665000

Kernel version:

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

*********

Sat Apr 21 23:02:21 2007

panic(cpu 0 caller 0x0035BFBD): mbuf address out of range 0xcd9c1be3

Backtrace, Format - Frame : Return Address (4 potential args on stack)

0x2534b7e8 : 0x128d08 (0x3cb134 0x2534b80c 0x131de5 0x0)

0x2534b828 : 0x35bfbd (0x3eb8f4 0xcd9c1be3 0x1 0x19e23a)

0x2534b848 : 0x35cbca (0x1 0x1 0x1000 0x2534b8f4)

0x2534b898 : 0x34b981 (0x36ef3e00 0x1 0x2534b918 0x221055)

0x2534b8b8 : 0x4f34a363 (0x36ef3e00 0x1 0x2534b948 0x19e23a)

0x2534b8d8 : 0x4f34cd74 (0x36ef3e00 0x2534b948 0x2534b908 0x0)

0x2534b968 : 0x4f34d0bb (0x3cccbc4 0x0 0x2534b9d8 0x2038cc)

0x2534b978 : 0x2038cc (0x3f66900 0x405a404 0x2 0x2534b9e8)

0x2534b9d8 : 0x233e82 (0x405a404 0x2 0x36ef3e00 0x431bd04)

0x2534bb18 : 0x23b1bd (0x36ef3e00 0x0 0x0 0x3fdffb8)

0x2534bc28 : 0x2397c2 (0x3fe0018 0x3e18 0x1 0x6400a8c0)

0x2534be08 : 0x22e364 (0x36f8ce00 0x14 0x2534be38 0x35c6aa)

0x2534be48 : 0x22fdc5 (0x36f8ce00 0x14 0x6 0x0)

0x2534bf58 : 0x21d53a (0x36f8ce00 0x36f8ce00 0x44507c 0x1a3010)

0x2534bf98 : 0x203df7 (0x405a404 0x36f8ce00 0x36f8ce34 0x1)

0x2534bfc8 : 0x19ac1c (0x0 0x0 0x19e0b5 0x4231cec) Backtrace terminated-invalid frame pointer 0x0

Kernel loadable modules in backtrace (with dependencies):

com.vmware.kext.vmnet(1.0.0d1)@0x4f349000

Kernel version:

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

0 Kudos
gglockner
Contributor
Contributor
Jump to solution

Any news on this? Thanks.

0 Kudos
admin
Immortal
Immortal
Jump to solution

Jumbo frames won't cause kernel panics after beta4 ships. Stay tuned for beta4...

Thanks!

0 Kudos
Andreas_Masur
Expert
Expert
Jump to solution

Jumbo frames won't cause kernel panics after beta4

ships. Stay tuned for beta4...

Hmmm....that is some nice information....seems we are getting closer to the next Beta... Smiley Happy

Ciao, Andreas

0 Kudos
gglockner
Contributor
Contributor
Jump to solution

Jumbo frames won't cause kernel panics after beta4

ships. Stay tuned for beta4...

Thanks, I look forward to testing beta 4! Smiley Happy

0 Kudos
gglockner
Contributor
Contributor
Jump to solution

Tested and confirmed that the bug is fixed in beta 4. Thanks very much for fixing this problem! Smiley Happy

0 Kudos
admin
Immortal
Immortal
Jump to solution

Awesome!

Thanks for reporting the issue in the first place!

0 Kudos