Selecting any other preset than Windows XP Professional results in kernel panic

[Razorblade12]

I am using Fedora 16_x64 (kernel  3.3.4-3.fc16.x86_64) and VMware Workstation 8.0.3 x64.

When creating a new VM and selecting the "Microsoft Windows / Windows XP Professional" preset, everything runs fine - I can power on the VM and it starts installing.

But when creating/selecting anything else than Windows XP, create a VM and then power it on I receive a kernel panic.

[ 1153.841304] ------------[ cut here ]------------
[ 1153.841332] kernel BUG at include/linux/mm.h:402!
[ 1153.841353] invalid opcode: 0000 [#1] SMP
[ 1153.841374] CPU 2
[ 1153.841384] Modules linked in: vmnet(O) parport_pc vsock(O) vmci(O) vmmon(O) lp vboxpci(O) vboxnetadp(O) vboxnetflt(O) vboxdrv(O) lockd ppdev parport fuse nf_conntrack_ipv4 nf_defrag_ipv4 ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 xt_state nf_conntrack ip6table_filter ip6_tables snd_usb_audio snd_usbmidi_lib snd_rawmidi joydev snd_hda_codec_hdmi sp5100_tco microcode edac_core edac_mce_amd k10temp serio_raw r8169 mii snd_hda_codec_realtek i2c_piix4 uinput snd_hda_intel snd_hda_codec snd_hwdep snd_seq snd_seq_device snd_pcm snd_timer snd soundcore snd_page_alloc sunrpc ata_generic pata_acpi pata_jmicron radeon ttm drm_kms_helper drm i2c_algo_bit i2c_core [last unloaded: vmnet]
[ 1153.841705]
[ 1153.841714] Pid: 5322, comm: vmware-vmx Tainted: G         C O 3.3.4-3.fc16.x86_64 #1 MSI MS-7599/870A-G54 (MS-7599)
[ 1153.841762] RIP: 0010:[<ffffffffa032a2d8>]  [<ffffffffa032a2d8>] get_page.part.0+0x4/0xd2c [vmmon]
[ 1153.841806] RSP: 0018:ffff880098dedd38  EFLAGS: 00010246
[ 1153.841829] RAX: 0000000000000000 RBX: ffffea000262b600 RCX: 0000000000000000
[ 1153.841860] RDX: ffffea000262b640 RSI: ffffea000262b600 RDI: ffff880098ad9000
[ 1153.841891] RBP: ffff880098dedd38 R08: 0000000000100000 R09: 000000000003a9de
[ 1153.841921] R10: 0000000000000003 R11: ffff880098f34dc0 R12: ffff880098c10b38
[ 1153.841952] R13: 0000000000000004 R14: 0000000000000003 R15: 0000000000000001
[ 1153.841983] FS:  00007f3f377f8740(0000) GS:ffff880227240000(0000) knlGS:0000000000000000
[ 1153.842002] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 1153.842002] CR2: 0000000000987720 CR3: 0000000098e81000 CR4: 00000000000006e0
[ 1153.842002] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 1153.842002] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[ 1153.842002] Process vmware-vmx (pid: 5322, threadinfo ffff880098dec000, task ffff880098acae60)
[ 1153.842002] Stack:
[ 1153.842002]  ffff880098deddc8 ffffffffa0320a28 ffff88022680a000 0000000513def09d
[ 1153.842002]  ffff880098e44bb0 ffff880098c10b10 0000000000000003 0000000000000004
[ 1153.842002]  0000000400000003 ffff880098c10b00 00000002000200d2 0000000000000000
[ 1153.842002] Call Trace:
[ 1153.842002]  [<ffffffffa0320a28>] LinuxDriverMmap+0x2a8/0x2d0 [vmmon]
[ 1153.842002]  [<ffffffff8114cc89>] mmap_region+0x369/0x510
[ 1153.842002]  [<ffffffff81146f68>] ? handle_mm_fault+0x1f8/0x350
[ 1153.842002]  [<ffffffff8114d178>] do_mmap_pgoff+0x348/0x360
[ 1153.842002]  [<ffffffff8114d256>] sys_mmap_pgoff+0xc6/0x230
[ 1153.842002]  [<ffffffff810d3a16>] ? __audit_syscall_exit+0x3d6/0x410
[ 1153.842002]  [<ffffffff810189e2>] sys_mmap+0x22/0x30
[ 1153.842002]  [<ffffffff815fbee9>] system_call_fastpath+0x16/0x1b
[ 1153.842002] Code: c7 c7 7a c8 32 a0 e8 48 9f ff ff 31 c0 e9 82 fc ff ff c7 83 78 04 00 00 00 00 00 00 66 b8 00 e0 e9 eb fb ff ff 00 00 55 48 89 e5 <0f> 0b bf f2 ff ff ff e9 f4 9d ff ff 00 00 00 00 00 00 00 00 00
[ 1153.842002] RIP  [<ffffffffa032a2d8>] get_page.part.0+0x4/0xd2c [vmmon]
[ 1153.842002]  RSP <ffff880098dedd38>
[ 1153.853725] ---[ end trace e6e019e26b978fe2 ]---

This is a clean/fresh install of Fedora and Workstation - no additional kernel modules have been installed.

It is the same with VMware Workstation 8.0.2

Workstion and Player used to work with kernel 3.2

Could anybody please help me.

Thank you

[mfelker]

I receive  as siimiliar  problem everytime I try to power on a VM in Fedora 16/17.  VMware  installs fine (with all the development headers and compiler program )cc, make etc).  However powering  on the VM results  in an immediatee kernel panic frequiring a hard reset of thephysical machine.  I have searche deverywhere fro a soluion (Fedofra foumns elsewhere o Google ) and can't fine anything.  Seemls to me this is a problem with the Fedora kernel and not VMware.   Virtualbox works perfectly (I us the script - .run file rather than the precompiled rpm  binary)   If anybody has creaed a VM on Fedora 16/17/ please,please  let us know your machine specs adn whether the VMware VM  is working properfly e.g. Tools install etc.

[Razorblade12]

I am not sure about this being a Linx/Fedora error or bug. Because a kernel panic usually points towards defective hardware or a faulty driver.

What I also did to test this:

I installed Workstation 8.0.3 on Windows 7. There I installed Fedora 16 x64, VMware Tools for Linux and then, afterwards I installed VMware Workstation 8.0.3 for Linux into that Fedora VM. Everything runs fine.

I am quite sure that my hardware is fine as Workstation 8.0.2 was working well on my computer (with kernel 3.2)

Maybe some developer can have a look into this.

[mfelker]

Razoblade.

       If I am understand  you corectly you are essetially talking about a nested  version of WS.  If this is correct  then hadn't thought of it and it ts elegant.   Do you mean that you install  VMware Tools using  the outer VMware program (installed  on Windows 7). where you have created a Fedora VM? .  Of course a   VM is essentialy  like a physical machine but with the ability  to   dynamicaly   install and manipulate virtual hardlware so . his  would  be very intrestinig  indeed.  I might be completely off-base here but I hope I am not!

Marty

[Razorblade12]

Marty,

This was just a test to see if Fedora is to blame for the kernel panics.

But essentially yes I am talking about a nested WS 8.

What I did: I Installed WS 8 on a Windows 7 computer, created a Fedora 16 VM, installed Fedora 16 x64, installed VMware Tools on the Fedora VM (without this, the WS setup would not complete successfully). And then finally installed WS 8 within the Fedora VM. There I created a non-Windows-XP-VM and fired it up.

--> No kernel panic.