Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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.
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.
systemctl status --all|grep vm; returns the following:
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.
Quote:
Originally Posted by sryzdn
I didn't really understand what else you asked for.
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;'.
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.
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]
Quote:
Next time you don't understand a command you could first 'man whatevercommandname' and read a bit?
Yes, I'm sorry.
Quote:
'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;'.
I enclosed the result. Some guys have solved a similar problem here. But I'm not sure what they have exactly done:
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]
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:
Quote:
Why don't you people just run Virtualbox? You don't have to patch it to get it to work.
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.
or run this to try and configure things before starting the services:
Code:
vmware-config.pl
...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.
...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?!
Is this what "patching" does? changing the kernel version?
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.
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.
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.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.