martinkg63
Contributor
Contributor

vmplayer-5.0.0 terminates immediately after start

Jump to solution

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

0 Kudos
1 Solution

Accepted Solutions
An_tony
Enthusiast
Enthusiast

I had what I think is the same problem on Workstation 9,  Fedora-17 64 bit.

I used the vmmon patch here:

http://communities.vmware.com/thread/400616?start=15&tstart=0

and modifed the patcher created by Artem S. Tashkinov to apply it.

Solved it for me, I hope it will for you, too.

View solution in original post

0 Kudos
22 Replies
continuum
Immortal
Immortal

dont worry about those two files - we all get this two messages - they can safely be ignored.

Do you need support with a recovery problem ? - call me via skype "sanbarrow"
0 Kudos
martinkg63
Contributor
Contributor

in previous vmware versions I had always import a patch for a working vmplayer on Fedora.

Thread with same kernel errors:

http://communities.vmware.com/message/2101694?tstart=0#2101694

maybe a workaround ?

http://communities.vmware.com/thread/407367

0 Kudos
An_tony
Enthusiast
Enthusiast

I had what I think is the same problem on Workstation 9,  Fedora-17 64 bit.

I used the vmmon patch here:

http://communities.vmware.com/thread/400616?start=15&tstart=0

and modifed the patcher created by Artem S. Tashkinov to apply it.

Solved it for me, I hope it will for you, too.

View solution in original post

0 Kudos
birdie
Expert
Expert

This patch looks very intrusive, has anyone tested it?

0 Kudos
rudefyet
Contributor
Contributor

Patch works with VMWare Workstation 9.0.0

Just make sure you rmmod/modprobe vmmon after you apply it or reboot.

0 Kudos
martinkg63
Contributor
Contributor
0 Kudos
void_main1
Contributor
Contributor

Thankyou for the patch.

This fixed my problems on Fedora 17 Desktop.

Kernel version 3.5.3-1 (x86_64) when trying to install and run VMware Player 5.0.0 (build 812338)

0 Kudos
melange
Contributor
Contributor

Thank you for the patch, ran into this problem after a kernel update this morning.  Saved me a ton of time.

0 Kudos
belloa
Contributor
Contributor

does someone has testes it with vmware workstation 9 and ubuntu 12.10 with kernel 3.5?

i patched it but sill getting the error:

Unable to change virtual machine power state: Cannot find a valid peer process to connect to

0 Kudos
cherieston_goa
Contributor
Contributor

The patch didn't seem to work for me either... I got the error 'Unable to change virtual machine power state: Cannot find a valid peer process to connect to' in Workstation 9 and vmplayer terminates as I try to open a VM.

The installation is on Ubuntu 12.04.1 Kernel 3.5.x

Hopefully vmware can fix this in their next update.

***UPDATE

Just wanted to add that my vm's have started working... Last thing I did was run this command:

sudo rm /lib/modules/$(uname -r)/misc/vm*

Which I think deletes all Vmware modules... and after a restart to my suprise all is working.

ref: http://communities.vmware.com/thread/415047

0 Kudos
mfelker
Expert
Expert

A   quck search on Google for the error message below shows some threads going back to 2006!

"Unable to change virtual machine power state: Cannot find a valid peer process to connect to"

This error is probably not due to  kernel  3.5.x:smileylaugh:

Anyway I have no problem whatsoever running VMware WS 9 on Ubunut 12.10 kernel 3.5..x   (up to date as  of  today).

All I used was the 3.5 patch "out of the box" directly after the WS 9 installation completeld  I am  running  Windows Server 2012 with a nested Hyper-V Windows 8 machine.  Works perfect ly.

I'm  posting this using  WS 9 running in Fedora 19 Rawhide kernel 3.6.x in a  openSUSE12.2 VM (full screen) with the same patch ( which is also good  for 3.6.x kernels.

I can't explain my good luckSmiley Happy

This is the link to "peer  proces  error Pretty amazing  that VMware hasn't resolved this issue in a least 6 years.

https://www.google.com/search?q=Unable+to+change+virtual+machine+power+state%3A+Cannot+find+a+valid+...

0 Kudos
niftymitch
Contributor
Contributor

RE the above

I had what I think is the same problem on Workstation 9,  Fedora-17 64 bit.

I used the vmmon patch here:

http://communities.vmware.com/thread/400616?start=15&tstart=0

and modifed the patcher created by Artem S. Tashkinov to apply it.

Solved it for me, I hope it will for you, too.

I also think I had this issue.

I applied this patch and it seems to have sorted out the black screen

and kernel oops.

Regarding to the black screen, It took me a while to discover that I could

toggle to alternate consoles then back to X11, i.e. CTL+ALT+F2; then CTL+ALT+F3

then CTL+ALT+F1    The error did make it to the system logs but my nVidea bits

and perhaps others "tained" my kernel

I picked up an eval of Workstation 9 and will have to scratch my head

to see if I want to dig in my wallet for the scratch to buy it in a couple

weeks based on this bug issue.  The same issue impacts Player as

well as the Workstation packages.

So far so good.

0 Kudos
mwildam
Contributor
Contributor

Thanks to An_tony - the patch worked fine for me, but:

I had troubles patching the VMWare Player because it was already previously patched with the older patch. So I uninstalled completely using

sudo vmware-installer -u vmware-player

and then

sudo rm  /usr/lib/vmware/modules/source/.patched

Then re-installed using the patch mentioned above - I mean this one: http://communities.vmware.com/message/2103172#2103172

0 Kudos
andreaplanet
Contributor
Contributor

Patch worked for WS9 & Ubuntu 12.10 fresh install.

Thank you 🙂

P.S.: before that I tried also sudo rm /lib/modules/$(uname -r)/misc/vm* + reboot, but it didnt solved the issue.

0 Kudos
cameigons
Contributor
Contributor

I was having the vmmon issue too. I'm on Ubuntu 12.10 and WS9, and the patch provided by An_tony worked for me too. Thanks man!

0 Kudos
dannyvdz
Contributor
Contributor

I keep getting 2 errors while trying to apply this patch:

Error 1:

patch-modules_3.5.0.sh: 27: [: workstation9.0.0: unexpected operator

patch-modules_3.5.0.sh: 28: [: workstation9.0.0: unexpected operator

Sorry, this script is only for VMWare WorkStation 9.0.0 or VMWare Player 5.0.0. Exiting

I am sure I have the correct versions though. So I just altered the script and removed the version check which made it execute.

When it executes the following error occurs:

Error 2:

patching file vmmon-only/linux/hostif.c
Stopping VMware services:
   VMware Authentication Daemon                                        done
At least one instance of VMware VMX is still running.
Please stop all running instances of VMware VMX first.
   VMware Authentication Daemon                                        done
Unable to stop services
-e
All done, you can now run .
Modules sources backup can be found in the '/usr/lib/vmware/modules/source-workstation9.0.0-2012-11-04-14:47:40-backup' directory

So basically it says a VMware VMX is still running but it's not. Even when I reboot my pc and kill all vmware processes I get this error...

I tried booting into single user mode but when I do that I can't apply the patch either...

Can anyone please help me out because I spent at least 5 hours on it now and I just want it to work...

0 Kudos
dannyvdz
Contributor
Contributor

*bump*

0 Kudos
mfelker
Expert
Expert

Just curious

A}  WSX is a standalone product and needs to be installed apart from WS 9 (as  .bundle file).  If you did not install the  product and still get an error message saying WSX is running I'd say y that VMware has  a serious problem and needs to address it ASAP.  Your error was reported by another poster  I believe  but he also did not say whter whether the WSX bundle had been installed.  The WSX product  was not seperate in the Tech Beta but I have no idea if that  is even available now

B)  Obviously if you did install it then you need to uninstall it using /usr/bin/vmware-installer.  Use the --help switch to find out the proper syntax for the command.

3)  Ifyiu  still get this error after  uninstallinig  WSX and rebooting then again VMware has a big problem.

The  3.5   patch  works every  time for   me on Ubuntu 12.10 so I can't help you there.

0 Kudos
dannyvdz
Contributor
Contributor

Thanks for your reply,

I'll take my time to check it out tomorrow.. I'm pretty tired now and I'll be better off tackling this when feeling good.

When I've figured something out I'll let you know!

0 Kudos