I have install vmware-workstation 6.5 in FC 10

when I typy vmware on command line I get following error ablow.


[root@rahil ~]# vmware
Logging to /tmp/vmware-root/setup-4534.log
modinfo: could not find module vmmon
modinfo: could not find module vmnet
modinfo: could not find module vmblock
modinfo: could not find module vmci
modinfo: could not find module vsock
modinfo: could not find module vmmon
modinfo: could not find module vmnet
modinfo: could not find module vmblock
modinfo: could not find module vmci
modinfo: could not find module vsock
[root@rahil ~]#


is there any solution for this error.

Did you start vmware's services before attempting to load the application?

Any problems during installation? (specially on modules compilation)

How to start vmware. I just type vmware to configure Vmware WS 6.5.

Let's see...

Assuming that installing VMWare over fedora is like everywhere else, after installation you should run vmware-config.pl (it should be located where vmware was installed, normally in /opt)

This, among other things, is in charge of creating vmware's modules (vmmon, vmnet...)

It also create the entries needed to start/stop vmware process (normally under xinetd)

Did you run vmware-config?

Since you doesn't have the modules I'm guessing no, so start doing that.

Then, you should be able to start/stop vmware through fedora's service manager

Hi

I have the same problem as rahilmaknojia, there does not appear to be a vmware-config.pl anywhere on my Fedora 10 64bit system. If I try to run the consol from the applications menu bar you see the application try to start but it then conks out (there is nothing in /var/log/messages that indicate any problems) however the vmware network consol starts fine.

Anymore idea's anyone?

Srooi

It appears that starting with version 6.5, vmware no longer has a "vmware-config.pl". I've tried to install the RPM, and it reported success, however, when I look in "/var/log/vmware-installer", I can see that if failed to build/install the required kernel modules. Bad thing is, I have no idea what to do about it.

There actually is a good fix, posted here:
http://geekdom.wesmo.com/2008/11/14/...rkstation-650/

In a nutshell, i did this:
$ sudo mv /usr/lib/vmware/modules/binary /usr/lib/vmware/modules/binary.old
$ sudo vmware-modconfig --console --install-all

You wait while it all compiles (assuming you have the kernel source packages installed), and booyah.

I, too, am in the same boat as the OP. I downloaded the latest VMware Workstation from VMWare's site, and ran the RPM installer. It came back with a warning about it Missing Security Signature. I click on the Force Install button and enter the root authentication, and it comes back as being successful. However, I cannot find where it installed to, nor can I start it from a terminal prompt. It says not found. I am also using Fedora 10 w/ the latest updates.

I have no VMware directory under /usr/lib, nor do I have any vmware entries under /var/log.

Anyone have any other ideas?

Thanks,
Dave

Hi Guys

The answer was surprisingly simple, just run /usr/bin/vmware from the consol obviously as root, Vmware 6.5.1 is now happily chugging along in my Fedora 10 box

Hth

Srooi

Hi Srooi,

Well, I would love to have done that, but after installing the packages, and received an install successful message, that folder doesn't exist. Because of some software tools I use for work, I ended up putting Vista back on the machine. Instead of running Vista or XP in a VM, I will now be running Fedora inside of a VM...go figure. Thanks for the suggestion though...
Dave

The problem lies in that the installer for vmware is an interactive install. As such, you can't install it successfully through the GUI. You need to install via command line in order to accept/agree to the licensing agreement. If you've already 'successfully' installed it via the GUI package manager, back it out through the command line first using the command rpm -e VMware-Workstation then re-install using rpm -ivh VMware-Workstation-<version>.x86_64.rpm.

This looks promising. Thank you! I'll try it once I return from my conference this week.