vmware vmplayer-5.5.0 and kernel-3.5.2-3.fc17.x86_64

[TheBigRed]

Hello,

I’m running fedora 17 with kernel 3.5.2-3.fc17.x86_64 and VMware-Workstation-Full-9.0.0-812388.x86_64.bundle.
vmplayer-5.0.0 terminates immediately after the start.

vmplayer-5.0.0 only runs with kernel-3.4.0-1.fc17.x86_64

The contents of the file vmware-modconfig-5653.log looks like following:

2012-08-23T20:00:54.506+01:00| vthread-3| I120: Log for VMware Workstation pid=5653 version=9.0.0 build=build-812388 option=Release
2012-08-23T20:00:54.506+01:00| vthread-3| I120: The process is 64-bit.
2012-08-23T20:00:54.506+01:00| vthread-3| I120: Host codepage=UTF-8 encoding=UTF-8
2012-08-23T20:00:54.506+01:00| vthread-3| I120: Host is Linux 3.5.2-3.fc17.x86_64 Fedora release 17 (Beefy Miracle)
2012-08-23T20:00:54.505+01:00| vthread-3| I120: Msg_Reset:
2012-08-23T20:00:54.505+01:00| vthread-3| I120: [msg.dictionary.load.openFailed] Cannot open file "/usr/lib/vmware/settings": Datei oder Verzeichnis nicht gefunden.
2012-08-23T20:00:54.505+01:00| vthread-3| I120: ----------------------------------------
2012-08-23T20:00:54.505+01:00| vthread-3| I120: PREF Optional preferences file not found at /usr/lib/vmware/settings. Using default values.
2012-08-23T20:00:54.506+01:00| vthread-3| I120: Msg_Reset:
2012-08-23T20:00:54.506+01:00| vthread-3| I120: [msg.dictionary.load.openFailed] Cannot open file "/home/martin/.vmware/config": Datei oder Verzeichnis nicht gefunden.
2012-08-23T20:00:54.506+01:00| vthread-3| I120: ----------------------------------------
2012-08-23T20:00:54.506+01:00| vthread-3| I120: PREF Optional preferences file not found at /home/martin/.vmware/config. Using default values.
2012-08-23T20:00:54.506+01:00| vthread-3| W110: Logging to /tmp/vmware-martin/vmware-modconfig-5653.log
2012-08-23T20:00:54.511+01:00| vthread-3| I120: Reading in info for the vmmon module.
2012-08-23T20:00:54.511+01:00| vthread-3| I120: Reading in info for the vmnet module.
2012-08-23T20:00:54.511+01:00| vthread-3| I120: Reading in info for the vmblock module.
2012-08-23T20:00:54.511+01:00| vthread-3| I120: Reading in info for the vmci module.
2012-08-23T20:00:54.511+01:00| vthread-3| I120: Reading in info for the vsock module.
2012-08-23T20:00:54.511+01:00| vthread-3| I120: Setting vsock to depend on vmci.
2012-08-23T20:00:54.511+01:00| vthread-3| I120: Created new pathsHash.
2012-08-23T20:00:54.511+01:00| vthread-3| I120: Invoking modinfo on "vmmon".
2012-08-23T20:00:54.513+01:00| vthread-3| I120: "/sbin/modinfo" exited with status 0.
2012-08-23T20:00:54.513+01:00| vthread-3| I120: Invoking modinfo on "vmnet".
2012-08-23T20:00:54.516+01:00| vthread-3| I120: "/sbin/modinfo" exited with status 0.
2012-08-23T20:00:54.516+01:00| vthread-3| I120: Invoking modinfo on "vmblock".
2012-08-23T20:00:54.519+01:00| vthread-3| I120: "/sbin/modinfo" exited with status 0.
2012-08-23T20:00:54.519+01:00| vthread-3| I120: Invoking modinfo on "vmci".
2012-08-23T20:00:54.521+01:00| vthread-3| I120: "/sbin/modinfo" exited with status 0.
2012-08-23T20:00:54.521+01:00| vthread-3| I120: Invoking modinfo on "vsock".
2012-08-23T20:00:54.523+01:00| vthread-3| I120: "/sbin/modinfo" exited with status 0.

The contents of the kernel.log file looks like following:

Aug 23 20:01:01 localhost kernel: [  710.974813] general protection fault: 0000 [#5] SMP
Aug 23 20:01:01 localhost kernel: [  710.974818] CPU 1
Aug 23 20:01:01 localhost kernel: [  710.974819] Modules linked in: stv0299 ves1x93 dvb_ttpci ttpci_eeprom saa7146_vv saa7146 dvb_core videobuf_dma_sg videobuf_core v4l2_common videodev media bnep bluetooth rfkill vmnet(O) vsock(O) vmci(O) vmmon(O) fuse snd_hda_codec_hdmi ppdev coretemp lpc_ich mfd_core nvidia(PO) snd_rme96 snd_hda_codec_analog serio_raw parport_pc shpchp parport skge sky2 i2c_i801 nfsd nfs_acl auth_rpcgss lockd sunrpc kvm_intel i2c_core kvm snd_hda_intel snd_hda_codec snd_hwdep snd_pcm asus_atk0110 uinput i82975x_edac edac_core microcode snd_page_alloc snd_timer snd soundcore binfmt_misc firewire_ohci firewire_core crc_itu_t [last unloaded: scsi_wait_scan]
Aug 23 20:01:01 localhost kernel: [  710.974851]
Aug 23 20:01:01 localhost kernel: [  710.974853] Pid: 6227, comm: vmware-vmx Tainted: P      D    O 3.5.2-3.fc17.x86_64 #1 stem manufacturer System Product Name/P5WDG2 WS PRO
Aug 23 20:01:01 localhost kernel: [  710.974855] RIP: 0010:[<ffffffffa0d4800f>]  [<ffffffffa0d4800f>] HostIF_SafeRDMSR+0xf/0x30 [vmmon]
Aug 23 20:01:01 localhost kernel: [  710.974863] RSP: 0018:ffff88016e7e5b88  EFLAGS: 00010246
Aug 23 20:01:01 localhost kernel: [  710.974864] RAX: 0000000000000000 RBX: 0000000000000001 RCX: 000000000000048b
Aug 23 20:01:01 localhost kernel: [  710.974866] RDX: 0000000000000000 RSI: ffff88016e7f2590 RDI: 000000000000048b
Aug 23 20:01:01 localhost kernel: [  710.974867] RBP: ffff88016e7e5b88 R08: ffff8801bfc96610 R09: ffffffffa0d46672
Aug 23 20:01:01 localhost kernel: [  710.974868] R10: 0000000000000038 R11: 0000000000003246 R12: 0000000000000000
Aug 23 20:01:01 localhost kernel: [  710.974869] R13: ffff88016e7f2580 R14: ffff88016e7f2580 R15: 00007fffdfd66850
Aug 23 20:01:01 localhost kernel: [  710.974871] FS:  00007ff5cd372740(0000) GS:ffff8801bfc80000(0000) knlGS:0000000000000000
Aug 23 20:01:01 localhost kernel: [  710.974872] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Aug 23 20:01:01 localhost kernel: [  710.974874] CR2: 000000000099ca10 CR3: 00000001446d5000 CR4: 00000000000007e0
Aug 23 20:01:01 localhost kernel: [  710.974875] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Aug 23 20:01:01 localhost kernel: [  710.974876] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Aug 23 20:01:01 localhost kernel: [  710.974878] Process vmware-vmx (pid: 6227, threadinfo ffff88016e7e4000, task ffff8801b2699710)
Aug 23 20:01:01 localhost kernel: [  710.974879] Stack:
Aug 23 20:01:01 localhost kernel: [  710.974880]  ffff88016e7e5bb8 ffffffffa0d48e23 ffffffffa0d48da0 ffff88016e7e5be8
Aug 23 20:01:01 localhost kernel: [  710.974883]  ffff88016e7f2580 0000000000000000 ffff88016e7e5bd8 ffffffffa0d47780
Aug 23 20:01:01 localhost kernel: [  710.974885]  ffff88016e7f2580 00000000fffffff4 ffff88016e7e5c08 ffffffffa0d4ac1c
Aug 23 20:01:01 localhost kernel: [  710.974888] Call Trace:
Aug 23 20:01:01 localhost kernel: [  710.974892]  [<ffffffffa0d48e23>] Vmx86GetMSR+0x83/0xd0 [vmmon]
Aug 23 20:01:01 localhost kernel: [  710.974896]  [<ffffffffa0d48da0>] ? Vmx86GetUnavailPerfCtrsOnCPU+0x150/0x150 [vmmon]
Aug 23 20:01:01 localhost kernel: [  710.974900]  [<ffffffffa0d47780>] HostIF_CallOnEachCPU+0x20/0x40 [vmmon]
Aug 23 20:01:01 localhost kernel: [  710.974904]  [<ffffffffa0d4ac1c>] Vmx86_GetAllMSRs+0x2c/0x50 [vmmon]
Aug 23 20:01:01 localhost kernel: [  710.974907]  [<ffffffffa0d454df>] LinuxDriver_Ioctl+0x70f/0xd40 [vmmon]
Aug 23 20:01:01 localhost kernel: [  710.974911]  [<ffffffff81125141>] ? unlock_page+0x31/0x50
Aug 23 20:01:01 localhost kernel: [  710.974914]  [<ffffffff8114a729>] ? __do_fault+0x3f9/0x560
Aug 23 20:01:01 localhost kernel: [  710.974916]  [<ffffffff8114d335>] ? handle_pte_fault+0x95/0xb10
Aug 23 20:01:01 localhost kernel: [  710.974920]  [<ffffffff8120220f>] ? ext4_file_write+0xbf/0x260
Aug 23 20:01:01 localhost kernel: [  710.974922]  [<ffffffff8115f12d>] ? free_pages_and_swap_cache+0xad/0xd0
Aug 23 20:01:01 localhost kernel: [  710.974924]  [<ffffffff8114e6b9>] ? handle_mm_fault+0x259/0x320
Aug 23 20:01:01 localhost kernel: [  710.974927]  [<ffffffff816103ec>] ? do_page_fault+0x1bc/0x4b0
Aug 23 20:01:01 localhost kernel: [  710.974930]  [<ffffffffa0d45b28>] LinuxDriver_UnlockedIoctl+0x18/0x20 [vmmon]
Aug 23 20:01:01 localhost kernel: [  710.974933]  [<ffffffff811996c9>] do_vfs_ioctl+0x99/0x580
Aug 23 20:01:01 localhost kernel: [  710.974935]  [<ffffffff81199c49>] sys_ioctl+0x99/0xa0
Aug 23 20:01:01 localhost kernel: [  710.974937]  [<ffffffff81614969>] system_call_fastpath+0x16/0x1b
Aug 23 20:01:01 localhost kernel: [  710.974938] Code: 83 c4 01 e8 84 a6 3e e0 44 89 e0 48 3b 43 08 72 e9 48 89 df e8 33 b4 42 e0 eb 9e 90 55 48 89 e5 66 66 66 66 90 31 c0 89 c2 89 f9 <0f> 32 31 ff 41 89 c0 48 c1 e2 20 89 f8 4c 09 c2 48 89 16 5d c3
Aug 23 20:01:01 localhost kernel: [  710.974962] RIP  [<ffffffffa0d4800f>] HostIF_SafeRDMSR+0xf/0x30 [vmmon]
Aug 23 20:01:01 localhost kernel: [  710.974966]  RSP <ffff88016e7e5b88>
Aug 23 20:01:01 localhost kernel: [  710.974968] ---[ end trace 04aa45b3d8c2dbda ]---

The two files "/usr/lib/vmware/settings" and "/home/martin/vmware/config" do not exist.
Now the question is, how can i create these files or what files must be deleted of the old settings. ?

[TheBigRed]

vmware kernel modules compiles fine:

[root@fc17 tmp]# vmware-modconfig --console --install-all
Stopping vmware (via systemctl):                           [  OK  ]
Using 2.6.x kernel build system.
make: Entering directory `/tmp/modconfig-C4tvy7/vmmon-only'
/bin/make -C /lib/modules/3.5.2-3.fc17.x86_64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/kernels/3.5.2-3.fc17.x86_64'
  CC [M]  /tmp/modconfig-C4tvy7/vmmon-only/linux/hostif.o
  CC [M]  /tmp/modconfig-C4tvy7/vmmon-only/linux/driver.o
  CC [M]  /tmp/modconfig-C4tvy7/vmmon-only/linux/driverLog.o
  CC [M]  /tmp/modconfig-C4tvy7/vmmon-only/common/apic.o
  CC [M]  /tmp/modconfig-C4tvy7/vmmon-only/common/memtrack.o
  CC [M]  /tmp/modconfig-C4tvy7/vmmon-only/common/hashFunc.o
  CC [M]  /tmp/modconfig-C4tvy7/vmmon-only/common/vmx86.o
  CC [M]  /tmp/modconfig-C4tvy7/vmmon-only/common/cpuid.o
  CC [M]  /tmp/modconfig-C4tvy7/vmmon-only/common/task.o
  CC [M]  /tmp/modconfig-C4tvy7/vmmon-only/common/comport.o
  CC [M]  /tmp/modconfig-C4tvy7/vmmon-only/common/phystrack.o
  CC [M]  /tmp/modconfig-C4tvy7/vmmon-only/vmcore/moduleloop.o
  LD [M]  /tmp/modconfig-C4tvy7/vmmon-only/vmmon.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /tmp/modconfig-C4tvy7/vmmon-only/vmmon.mod.o
  LD [M]  /tmp/modconfig-C4tvy7/vmmon-only/vmmon.ko
make[1]: Leaving directory `/usr/src/kernels/3.5.2-3.fc17.x86_64'
/bin/make -C $PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/modconfig-C4tvy7/vmmon-only'
make[1]: »postbuild« ist bereits aktualisiert.
make[1]: Leaving directory `/tmp/modconfig-C4tvy7/vmmon-only'
cp -f vmmon.ko ./../vmmon.o
make: Leaving directory `/tmp/modconfig-C4tvy7/vmmon-only'
Using 2.6.x kernel build system.
make: Entering directory `/tmp/modconfig-C4tvy7/vmnet-only'
/bin/make -C /lib/modules/3.5.2-3.fc17.x86_64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/kernels/3.5.2-3.fc17.x86_64'
  CC [M]  /tmp/modconfig-C4tvy7/vmnet-only/driver.o
  CC [M]  /tmp/modconfig-C4tvy7/vmnet-only/hub.o
  CC [M]  /tmp/modconfig-C4tvy7/vmnet-only/userif.o
  CC [M]  /tmp/modconfig-C4tvy7/vmnet-only/netif.o
  CC [M]  /tmp/modconfig-C4tvy7/vmnet-only/bridge.o
  CC [M]  /tmp/modconfig-C4tvy7/vmnet-only/filter.o
  CC [M]  /tmp/modconfig-C4tvy7/vmnet-only/procfs.o
  CC [M]  /tmp/modconfig-C4tvy7/vmnet-only/smac_compat.o
  CC [M]  /tmp/modconfig-C4tvy7/vmnet-only/smac.o
  CC [M]  /tmp/modconfig-C4tvy7/vmnet-only/vnetEvent.o
  CC [M]  /tmp/modconfig-C4tvy7/vmnet-only/vnetUserListener.o
  LD [M]  /tmp/modconfig-C4tvy7/vmnet-only/vmnet.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /tmp/modconfig-C4tvy7/vmnet-only/vmnet.mod.o
  LD [M]  /tmp/modconfig-C4tvy7/vmnet-only/vmnet.ko
make[1]: Leaving directory `/usr/src/kernels/3.5.2-3.fc17.x86_64'
/bin/make -C $PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/modconfig-C4tvy7/vmnet-only'
make[1]: »postbuild« ist bereits aktualisiert.
make[1]: Leaving directory `/tmp/modconfig-C4tvy7/vmnet-only'
cp -f vmnet.ko ./../vmnet.o
make: Leaving directory `/tmp/modconfig-C4tvy7/vmnet-only'
Using 2.6.x kernel build system.
make: Entering directory `/tmp/modconfig-C4tvy7/vmblock-only'
/bin/make -C /lib/modules/3.5.2-3.fc17.x86_64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/kernels/3.5.2-3.fc17.x86_64'
  CC [M]  /tmp/modconfig-C4tvy7/vmblock-only/linux/filesystem.o
  CC [M]  /tmp/modconfig-C4tvy7/vmblock-only/linux/file.o
  CC [M]  /tmp/modconfig-C4tvy7/vmblock-only/linux/block.o
  CC [M]  /tmp/modconfig-C4tvy7/vmblock-only/linux/module.o
  CC [M]  /tmp/modconfig-C4tvy7/vmblock-only/linux/super.o
  CC [M]  /tmp/modconfig-C4tvy7/vmblock-only/linux/control.o
  CC [M]  /tmp/modconfig-C4tvy7/vmblock-only/linux/stubs.o
  CC [M]  /tmp/modconfig-C4tvy7/vmblock-only/linux/inode.o
  CC [M]  /tmp/modconfig-C4tvy7/vmblock-only/linux/dentry.o
  LD [M]  /tmp/modconfig-C4tvy7/vmblock-only/vmblock.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /tmp/modconfig-C4tvy7/vmblock-only/vmblock.mod.o
  LD [M]  /tmp/modconfig-C4tvy7/vmblock-only/vmblock.ko
make[1]: Leaving directory `/usr/src/kernels/3.5.2-3.fc17.x86_64'
/bin/make -C $PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/modconfig-C4tvy7/vmblock-only'
make[1]: »postbuild« ist bereits aktualisiert.
make[1]: Leaving directory `/tmp/modconfig-C4tvy7/vmblock-only'
cp -f vmblock.ko ./../vmblock.o
make: Leaving directory `/tmp/modconfig-C4tvy7/vmblock-only'
Using 2.6.x kernel build system.
make: Entering directory `/tmp/modconfig-C4tvy7/vmci-only'
/bin/make -C /lib/modules/3.5.2-3.fc17.x86_64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/kernels/3.5.2-3.fc17.x86_64'
  CC [M]  /tmp/modconfig-C4tvy7/vmci-only/linux/driver.o
  CC [M]  /tmp/modconfig-C4tvy7/vmci-only/linux/vmciKernelIf.o
  CC [M]  /tmp/modconfig-C4tvy7/vmci-only/common/vmciDriver.o
  CC [M]  /tmp/modconfig-C4tvy7/vmci-only/common/vmciResource.o
  CC [M]  /tmp/modconfig-C4tvy7/vmci-only/common/vmciRoute.o
  CC [M]  /tmp/modconfig-C4tvy7/vmci-only/common/vmciContext.o
  CC [M]  /tmp/modconfig-C4tvy7/vmci-only/common/vmciDatagram.o
  CC [M]  /tmp/modconfig-C4tvy7/vmci-only/common/vmciHashtable.o
  CC [M]  /tmp/modconfig-C4tvy7/vmci-only/common/vmciEvent.o
  CC [M]  /tmp/modconfig-C4tvy7/vmci-only/common/vmciQueuePair.o
  CC [M]  /tmp/modconfig-C4tvy7/vmci-only/common/vmciQPair.o
  CC [M]  /tmp/modconfig-C4tvy7/vmci-only/common/vmciDoorbell.o
  CC [M]  /tmp/modconfig-C4tvy7/vmci-only/driverLog.o
  LD [M]  /tmp/modconfig-C4tvy7/vmci-only/vmci.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /tmp/modconfig-C4tvy7/vmci-only/vmci.mod.o
  LD [M]  /tmp/modconfig-C4tvy7/vmci-only/vmci.ko
make[1]: Leaving directory `/usr/src/kernels/3.5.2-3.fc17.x86_64'
/bin/make -C $PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/modconfig-C4tvy7/vmci-only'
make[1]: »postbuild« ist bereits aktualisiert.
make[1]: Leaving directory `/tmp/modconfig-C4tvy7/vmci-only'
cp -f vmci.ko ./../vmci.o
make: Leaving directory `/tmp/modconfig-C4tvy7/vmci-only'
Using 2.6.x kernel build system.
make: Entering directory `/tmp/modconfig-C4tvy7/vsock-only'
/bin/make -C /lib/modules/3.5.2-3.fc17.x86_64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/kernels/3.5.2-3.fc17.x86_64'
  CC [M]  /tmp/modconfig-C4tvy7/vsock-only/linux/af_vsock.o
  CC [M]  /tmp/modconfig-C4tvy7/vsock-only/linux/vsockAddr.o
  CC [M]  /tmp/modconfig-C4tvy7/vsock-only/linux/notifyQState.o
  CC [M]  /tmp/modconfig-C4tvy7/vsock-only/linux/util.o
  CC [M]  /tmp/modconfig-C4tvy7/vsock-only/linux/stats.o
  CC [M]  /tmp/modconfig-C4tvy7/vsock-only/linux/notify.o
  CC [M]  /tmp/modconfig-C4tvy7/vsock-only/driverLog.o
  LD [M]  /tmp/modconfig-C4tvy7/vsock-only/vsock.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /tmp/modconfig-C4tvy7/vsock-only/vsock.mod.o
  LD [M]  /tmp/modconfig-C4tvy7/vsock-only/vsock.ko
make[1]: Leaving directory `/usr/src/kernels/3.5.2-3.fc17.x86_64'
/bin/make -C $PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/modconfig-C4tvy7/vsock-only'
make[1]: »postbuild« ist bereits aktualisiert.
make[1]: Leaving directory `/tmp/modconfig-C4tvy7/vsock-only'
cp -f vsock.ko ./../vsock.o
make: Leaving directory `/tmp/modconfig-C4tvy7/vsock-only'
Starting vmware (via systemctl):                           [  OK  ]

[kiyoseki]

I am facing the same issue.

I was running VMware Player 4.0.4 with a patch quite fine though, Windows8 RTM doesn't run if VMware-tools installed while Windows version of VMware4.0.4 runs it with no obviouce problem. So, I upgraded the VMware to 5.0.0. The Windows virsion runs very well but Linux virsion on Fedora17.
Now, no Virtual Machine can be activated.

Compairing my call trace with the above one, they are almost identical. It implise the issue is the same.

Env:
Kernel :3.5.2-3.fc17.x86_64
Mother:Asrock P5B-DE
CPU:Intel Core2 Duo E8500
RAM:6GB / HDD:500GB SATA2

My message log.
Aug 23 17:47:43 Fedora17 kernel: [ 960.747528] general protection fault: 0000 [#1] SMP
Aug 23 17:47:43 Fedora17 kernel: [ 960.747544] CPU 1
Aug 23 17:47:43 Fedora17 kernel: [ 960.747547] Modules linked in: vmnet(O) parport_pc vsock(O) vmci(O) vmmon(O) tpm_bios lockd bnep sunrpc bluetooth rfkill ppdev parport fuse ip6t_REJECT nf_conntrack_ipv4 nf_conntrack_ipv6 nf_defrag_ipv4 nf_defrag_ipv6 ip6table_filter xt_state nf_conntrack ip6_tables snd_hda_codec_via snd_hda_intel snd_hda_codec snd_hwdep snd_pcm lpc_ich r8169 i2c_i801 coretemp snd_page_alloc mfd_core mii kvm_intel kvm snd_timer snd soundcore microcode uinput binfmt_misc ata_generic firewire_ohci pata_acpi aic7xxx pata_via scsi_transport_spi firewire_core crc_itu_t nouveau mxm_wmi wmi video i2c_algo_bit drm_kms_helper ttm drm i2c_core [last unloaded: vmnet]
Aug 23 17:47:43 Fedora17 kernel: [ 960.747654]
Aug 23 17:47:43 Fedora17 kernel: [ 960.747656] Pid: 5857, comm: vmware-vmx Tainted: G O 3.5.2-1.fc17.x86_64 #1 To Be Filled By O.E.M. To Be Filled By O.E.M./P5B-DE
Aug 23 17:47:43 Fedora17 kernel: [ 960.747667] RIP: 0010:[<ffffffffa030f20f>] [<ffffffffa030f20f>] HostIF_SafeRDMSR+0xf/0x30 [vmmon]
Aug 23 17:47:43 Fedora17 kernel: [ 960.747680] RSP: 0018:ffff880137419b88 EFLAGS: 00010246
Aug 23 17:47:43 Fedora17 kernel: [ 960.747684] RAX: 0000000000000000 RBX: 0000000000000001 RCX: 000000000000048c
Aug 23 17:47:43 Fedora17 kernel: [ 960.747689] RDX: 0000000000000000 RSI: ffff880197c5dd10 RDI: 000000000000048c
Aug 23 17:47:43 Fedora17 kernel: [ 960.747694] RBP: ffff880137419b88 R08: ffff8801a3c96610 R09: ffffffffa030d872
Aug 23 17:47:43 Fedora17 kernel: [ 960.747783] R10: 0000000000000038 R11: 0000000000000000 R12: 0000000000000000
Aug 23 17:47:43 Fedora17 kernel: [ 960.747789] R13: ffff880197c5dd00 R14: ffff880197c5dd00 R15: 00007fff14551f20
Aug 23 17:47:43 Fedora17 kernel: [ 960.747794] FS: 00007ffaca2e9740(0000) GS:ffff8801a3c80000(0000) knlGS:0000000000000000
Aug 23 17:47:43 Fedora17 kernel: [ 960.747799] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Aug 23 17:47:43 Fedora17 kernel: [ 960.747803] CR2: 000000000099ca10 CR3: 00000001532a1000 CR4: 00000000000407e0
Aug 23 17:47:43 Fedora17 kernel: [ 960.747808] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Aug 23 17:47:43 Fedora17 kernel: [ 960.747814] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Aug 23 17:47:43 Fedora17 kernel: [ 960.747819] Process vmware-vmx (pid: 5857, threadinfo ffff880137418000, task ffff88019670ae20)
Aug 23 17:47:43 Fedora17 kernel: [ 960.747826] Stack:
Aug 23 17:47:43 Fedora17 kernel: [ 960.747829] ffff880137419bb8 ffffffffa030fe23 ffffffffa030fda0 ffff880137419be8
Aug 23 17:47:43 Fedora17 kernel: [ 960.747838] ffff880197c5dd00 0000000000000000 ffff880137419bd8 ffffffffa030e980
Aug 23 17:47:43 Fedora17 kernel: [ 960.747848] ffff880197c5dd00 00000000fffffff4 ffff880137419c08 ffffffffa0311c1c
Aug 23 17:47:43 Fedora17 kernel: [ 960.747858] Call Trace:
Aug 23 17:47:43 Fedora17 kernel: [ 960.747865] [<ffffffffa030fe23>] Vmx86GetMSR+0x83/0xd0 [vmmon]
Aug 23 17:47:43 Fedora17 kernel: [ 960.747873] [<ffffffffa030fda0>] ? Vmx86GetUnavailPerfCtrsOnCPU+0x150/0x150 [vmmon]
Aug 23 17:47:43 Fedora17 kernel: [ 960.747882] [<ffffffffa030e980>] HostIF_CallOnEachCPU+0x20/0x40 [vmmon]
Aug 23 17:47:43 Fedora17 kernel: [ 960.747890] [<ffffffffa0311c1c>] Vmx86_GetAllMSRs+0x2c/0x50 [vmmon]
Aug 23 17:47:43 Fedora17 kernel: [ 960.747896] [<ffffffffa030c6df>] LinuxDriver_Ioctl+0x70f/0xd40 [vmmon]
Aug 23 17:47:43 Fedora17 kernel: [ 960.747905] [<ffffffff81125141>] ? unlock_page+0x31/0x50
Aug 23 17:47:43 Fedora17 kernel: [ 960.747912] [<ffffffff8114a729>] ? __do_fault+0x3f9/0x560
Aug 23 17:47:43 Fedora17 kernel: [ 960.747917] [<ffffffff8114d335>] ? handle_pte_fault+0x95/0xb10
Aug 23 17:47:43 Fedora17 kernel: [ 960.747925] [<ffffffff8120220f>] ? ext4_file_write+0xbf/0x260
Aug 23 17:47:43 Fedora17 kernel: [ 960.747931] [<ffffffff8115f12d>] ? free_pages_and_swap_cache+0xad/0xd0
Aug 23 17:47:43 Fedora17 kernel: [ 960.747939] [<ffffffff8114e6b9>] ? handle_mm_fault+0x259/0x320
Aug 23 17:47:43 Fedora17 kernel: [ 960.747946] [<ffffffff8161036c>] ? do_page_fault+0x1bc/0x4b0
Aug 23 17:47:43 Fedora17 kernel: [ 960.747953] [<ffffffffa030cd28>] LinuxDriver_UnlockedIoctl+0x18/0x20 [vmmon]
Aug 23 17:47:43 Fedora17 kernel: [ 960.747960] [<ffffffff811996c9>] do_vfs_ioctl+0x99/0x580
Aug 23 17:47:43 Fedora17 kernel: [ 960.747969] [<ffffffff812793da>] ? inode_has_perm.isra.31.constprop.61+0x2a/0x30
Aug 23 17:47:43 Fedora17 kernel: [ 960.747983] [<ffffffff8127a9b7>] ? file_has_perm+0x97/0xb0
Aug 23 17:47:43 Fedora17 kernel: [ 960.747992] [<ffffffff81199c49>] sys_ioctl+0x99/0xa0
Aug 23 17:47:43 Fedora17 kernel: [ 960.748001] [<ffffffff816148e9>] system_call_fastpath+0x16/0x1b
Aug 23 17:47:43 Fedora17 kernel: [ 960.748001] Code: 83 c4 01 e8 84 34 e2 e0 44 89 e0 48 3b 43 08 72 e9 48 89 df e8 33 42 e6 e0 eb 9e 90 55 48 89 e5 66 66 66 66 90 31 c0 89 c2 89 f9 <0f> 32 31 ff 41 89 c0 48 c1 e2 20 89 f8 4c 09 c2 48 89 16 5d c3
Aug 23 17:47:43 Fedora17 kernel: [ 960.748001] RIP [<ffffffffa030f20f>] HostIF_SafeRDMSR+0xf/0x30 [vmmon]
Aug 23 17:47:43 Fedora17 kernel: [ 960.748001] RSP <ffff880137419b88>
Aug 23 17:47:43 Fedora17 kernel: [ 960.765735] ---[ end trace d80d9248f5020065 ]---
Aug 23 17:47:43 Fedora17 kernel: [ 960.929054] [drm] nouveau 0000:05:00.0: EvoCh 1 Mthd 0x0080 Data 0x00000000 (0x0006 0x05)
Aug 23 17:47:49 Fedora17 kernel: [ 966.928627] [drm] nouveau 0000:05:00.0: EvoCh 1 Mthd 0x0080 Data 0x00000000 (0x1006 0x05)

[TheBigRed]

Well, i started a discussion on the vmware forum and a guy told me, that i should use a vmmon patch
for Workstation 9, Fedora-17 64 bit from here

vmware9_kernel35_patch.tar.bz2

the patch solved the problem.

1. stop vmware services

[root@fc17 tmp]# systemctl stop vmware-USBArbitrator.service vmware-workstation-server.service vmware.service

2. unpack patch archive and execute vmware modul patch script as user

martin@fc17 tmp$ tar xfj vmware9_kernel35_patch.tar.bz2
martin@fc17 tmp$ cd vmware9_kernel3.5_patch
martin@fc17 tmp$ “sudo ./patch-modules_3.5.0.sh"