Hi,

I have tried installing vmware workstation 9 bundle, but I am receiving the following message while I want to start the service:

I have enclosed systemctl and journalctl -xn. I cannot figure out what is missing here.

Attached Files

	system2.txt (10.7 KB, 17 views)
	journal.txt (1.5 KB, 22 views)

What does 'systemctl show vmware.service' return? Also note in your systemctl output there's a "vmware-w...n-server.service". No idea what its name is (figure it out with locate or find or 'systemctl status --all|grep vm;') and return the systemctl "status" and "show" for it.

I have enclosed the result.


systemctl status --all|grep vm; returns the following:

I didn't really understand what else you asked for.

Attached Files

show.txt (3.0 KB, 20 views)

Apparently it starts /etc/rc.d/init.d/vmware so see what '/etc/rc.d/init.d/vmware status; /etc/rc.d/init.d/vmware start' returns.


Next time you don't understand a command you could first 'man whatevercommandname' and read a bit? 'systemctl list-units --all | grep vm' should return also "vmware-workstation-server.service", so run 'systemctl status vmware-workstation-server.service; systemctl show vmware-workstation-server.service;'.

It returns:

Module vmmon not loaded
Module vmnet not loaded
Starting vmware (via systemctl): Job for vmware.service failed. See 'systemctl status vmware.service' and 'journalctl -xn' for details. [FAILED]

Yes, I'm sorry.

I enclosed the result. Some guys have solved a similar problem here. But I'm not sure what they have exactly done:

https://communities.vmware.com/threa...art=0&tstart=0

Attached Files

1.txt (3.5 KB, 14 views)

Ah, thought that would be it. You'll have to find out if the installation built the vmmon and vmnet kernel modules for you before you start the service. However:


Indeed. Sure you could patch the kernel to allow VMware Workstation to work but I especially like the last reply in one of the mentioned resources:
That kind of makes sense if you want to work with virtualization right away.
*Note all that patching isn't a Fedora or Linux error but VMware not catching up.

How can I find it out? If I want to install it again, how can I do it?

Either check the modules if installed for the current kernel:
or run this to try and configure things before starting the services:
...except the latter probably won't work without patching your kernel first. For that you have to download the kernel source RPM for your current kernel, patch it, configure it, give it a local version tag so you won't overwrite it on install, run make, pray it doesn't error out, install it, then run vmware-config.pl to make it build the modules. As you can see that's slightly more work than running Virtualbox.

That's a university course for me as a beginner. I wonder why I didn't have such problem installing the same vmware bundle on fedora 19 last time with exactly similar env?!

You could always install virual machine manager works wonders for me...

I have some problems with my vmware installation

I am sorry if this seems naive to ask, I just can't do anything else unless I solve and understand a problem:

I read somewhere that a guy with similar problem said:

Is this what "patching" does? changing the kernel version?

A course in VMware products or just using virtualization in general as an aid to actually accomplish things?


You did it so without details I can't tell why.

The Linux kernel source is delivered as a monolithic tar ball (example: https://www.kernel.org/pub/linux/ker...3.10.11.tar.xz) and as a patch (https://www.kernel.org/pub/linux/ker...tch-3.10.11.xz). So essentially you should be able to upgrade kernel linux-3.10.10 by applying the patch to the kernel source directory. But that's not what we're talking about here. VMware released their product back then using an older kernel version. Now modules like vmnet and vmmon should compile cleanly but as the kernel source progresses some functions have gotten renamed, been deprecated and Other Stuff happened that keeps those modules from compiling cleanly. Out of the goodness of their heart some Deities took pity upon others and wrote patches to fix things. That's what this patching is all about.

No, I just meant that if I want to do all the things you mentioned it will take me so long, because I am a very beginner.

Thanks so much for the explanation.

I read in a post that pasting the vmware-server directory in the new kernel directory in /lib/modules must work.
The problem I have is that after installing vmware, I cannot see any vmware-server directories in any of the kernel directories in /lib/modules.