I'm unsuccessfully trying to run vmware.service via systemd on Fedora 19.
Kernel Info: 3.10.3-300.fc19.x86_64
VMware player: VMware-Player-5.0.2-1031769.x86_64.bin
altus# rpm -qa |grep vmware
When I try to run vmware player from the GUI (), first I get messagebox saying "Before you can run VMware, several modules must be compiled and loaded into the running kernel" and when I click on Install button, nothing happens. Here are some logs generated on button click:
Aug 1 11:23:24 altus kernel: [157759.696449] vmware-gksu: segfault at 7fe5d58194ab ip 00007fe5da08c196 sp 00007fff14246b78 error 4 in libc-2.17.so[7fe5d9f5b000+1b5000]
Aug 1 11:23:24 altus abrt: Saved core dump of pid 24580 (/usr/lib/vmware/bin/appLoader) to /var/tmp/abrt/ccpp-2013-08-01-11:23:24-24580 (2121728 bytes)
Aug 1 11:23:24 altus abrtd: Directory 'ccpp-2013-08-01-11:23:24-24580' creation detected
Aug 1 11:23:26 altus abrtd: Executable '/usr/lib/vmware/bin/appLoader' doesn't belong to any package and ProcessUnpackaged is set to 'no'
Aug 1 11:23:26 altus abrtd: 'post-create' on '/var/tmp/abrt/ccpp-2013-08-01-11:23:24-24580' exited with 1
Aug 1 11:23:26 altus abrtd: Deleting problem directory '/var/tmp/abrt/ccpp-2013-08-01-11:23:24-24580'
After that I tried to run systemctl start vmware.service but if FAILS.
altus# systemctl start vmware.service
Job for vmware.service failed.
|journalctl -xn output:|
-- Logs begin at Tue 2013-07-02 16:51:21 CEST, end at Thu 2013-08-01 11:05:15 CEST. --
Aug 01 11:05:09 altus.local vmware: Starting VMware services:
Aug 01 11:05:10 altus.local vmware: Virtual machine monitor[FAILED]
Aug 01 11:05:10 altus.local vmware: Virtual machine communication interface[FAILED]
Aug 01 11:05:15 altus.local vmware: VM communication interface socket family[ OK ]
Aug 01 11:05:15 altus.local vmware: Blocking file system[ OK ]
Aug 01 11:05:15 altus.local vmware: Virtual ethernet[FAILED]
Aug 01 11:05:15 altus.local vmware: VMware Authentication Daemon[ OK ]
Aug 01 11:05:15 altus.local systemd: vmware.service: control process exited, code=exited status=1
Aug 01 11:05:15 altus.local systemd: Failed to start SYSV: This service starts and stops VMware servic
-- Subject: Unit vmware.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/be02cf6855d2428ba40df7e9d022f0
-- Unit vmware.service has failed.
-- The result is failed.
Aug 01 11:05:15 altus.local systemd: Unit vmware.service entered failed state.
Has anyone achieved to start vmware service on systemd? Am I missing some modules or what? Also, If you need output of some other logs I currently can't remember, I will be glad to post it here.
I have the same problem. Fedora 19 + VMware WS 9.0.2.
Failed to build vmblock
# uname -r
systemd: Failed to start SYSV: This services starts and stops the Workstation as a Server daemon..
Anyone care to help? I would hate to resort to VirtualBox 😕
I reverted to the 3.9 kernel in Fedora 19 and WS starts now.
Strangely, I could not enter the serial # in the normal GUI. I had to run:
/usr/lib/vmware/bin/vmware-enter-serial -n 'VMware Workstation' -v '9.0'
and then enter my key.
Hope this helps.
Ok, this has been solved, at least for me.
First, check this page out:
Vmware 9.0.x on Linux-3.10.0 patches?
Then, the vmblock issue is solved here:
Best of luck,
put together some old and new stuff, this worked for me well:
Not sure why VMware makes WS available for Linux, but yet enjoy making their users go to hell and back to get it working. And good luck with getting support for WS. All queries go to /dev/null.
Considering VirtualBox as they actually keep up with kernel / OS releases. Everyone in my company has abandoned VMware WS for this reason (we are a linux shop).
I have the same problem ,and My configuration is Fedora 19 ( )+VM 9.0.2
Although there mmmm90
provide a useful link , but I don't know how to use it .
I just run download and run the .sh file ,but it doesn't work
And now I try to install the latest version VM 10.0 ,
What about u ?
Is it useful for 3.11.3-201.fc19.x86_64 ?