Solved: vmplayer-5.0.0 terminates immediately after start - Page 2

martinkg63 · ‎08-23-2012

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:[] [] HostIF_SafeRDMSR+0xf/0×30 [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] [] Vmx86GetMSR+0×83/0xd0 [vmmon]
Aug 23 20:01:01 localhost kernel: [ 710.974896] [] ? Vmx86GetUnavailPerfCtrsOnCPU+0×150/0×150 [vmmon]
Aug 23 20:01:01 localhost kernel: [ 710.974900] [] HostIF_CallOnEachCPU+0×20/0×40 [vmmon]
Aug 23 20:01:01 localhost kernel: [ 710.974904] [] Vmx86_GetAllMSRs+0x2c/0×50 [vmmon]
Aug 23 20:01:01 localhost kernel: [ 710.974907] [] LinuxDriver_Ioctl+0x70f/0xd40 [vmmon]
Aug 23 20:01:01 localhost kernel: [ 710.974911] [] ? unlock_page+0×31/0×50
Aug 23 20:01:01 localhost kernel: [ 710.974914] [] ? __do_fault+0x3f9/0×560
Aug 23 20:01:01 localhost kernel: [ 710.974916] [] ? handle_pte_fault+0×95/0xb10
Aug 23 20:01:01 localhost kernel: [ 710.974920] [] ? ext4_file_write+0xbf/0×260
Aug 23 20:01:01 localhost kernel: [ 710.974922] [] ? free_pages_and_swap_cache+0xad/0xd0
Aug 23 20:01:01 localhost kernel: [ 710.974924] [] ? handle_mm_fault+0×259/0×320
Aug 23 20:01:01 localhost kernel: [ 710.974927] [] ? do_page_fault+0x1bc/0x4b0
Aug 23 20:01:01 localhost kernel: [ 710.974930] [] LinuxDriver_UnlockedIoctl+0×18/0×20 [vmmon]
Aug 23 20:01:01 localhost kernel: [ 710.974933] [] do_vfs_ioctl+0×99/0×580
Aug 23 20:01:01 localhost kernel: [ 710.974935] [] sys_ioctl+0×99/0xa0
Aug 23 20:01:01 localhost kernel: [ 710.974937] [] system_call_fastpath+0×16/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 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 [] HostIF_SafeRDMSR+0xf/0×30 [vmmon]
Aug 23 20:01:01 localhost kernel: [ 710.974966] RSP
Aug 23 20:01:01 localhost kernel: [ 710.974968] —[ end trace 04aa45b3d8c2dbda ]—

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  ]

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. ?

Why exist vmplayer immediately after starting. ?

mwildam · ‎11-07-2012

@dannyvdz:

1. Did you carefullly read the first page of the thread?

2. You do not mention your Linux kernel version used which is relevant.

I was now able to get

VMware-Player-5.0.0-812388.

x86_64 to work in the following way
a) using the 3.5 or 3.6 Kernel (I am using 3.5.0-18 currently which I got from http://archive.ubuntu.com/ubuntu/pool/main/l/linux/ (4 files involved per version)

b) Completely uninstalling VMWare-Player using sudo vmware-installer -u vmware-player
c) Removing rest of older patch using sudo rm /usr/lib/vmware/modules/source/.patched
d) applying the patch attached (which has been already earlier mentioned and linked).
e) reinstall of VMware-Player-5.0.0-812388.x86_64 while running the 3.5 or 3.6 kernel.

dannyvdz · ‎11-08-2012

Thanks again for the replies.

I removed VMWare using the vmware-installer -u flag again.

Then I rebooted and checked my kernel version once more to be 100% sure (3.5.0-18-generic)

Upon trying to remove the patched files an error occured saying these files didn't exist so I removed the entire /usr/lib/vmware/ folder.

Fortunately for me I was looking on one of my fav tech websites and saw VMWare workstation 9.0.1 was just released.
I downloaded en installed VMWare 9.0.1 and it just works now, didn't even need to patch anything anymore!

My problem might have been installing it on kubuntu 12.10 (since the new version has full support according to the changelog)..

I'm not quite sure wat fixed it.. but it works now 🙂

Thanks a lot!

pst007x · ‎11-17-2012

Wouldn't it be amazing if there was an answer that actually worked! There are loads of links to here there and every where but no-one has said anything of use!!!!

Please could someone talk ENGLISH!!! and help!!!!!!!!!!!!

VM is SHIT!!!!!!!!!!!!!!!!