dzeman
Contributor
Contributor

VMware Player 2.5 118166 x86_64 Linux RPM missing vmware-config.pl after install

There is no vmware-config.pl found after installing via RPM to reconfig vmware after a new kernel is installed. Only way to reconfigure is to uninstall the RPM then reinstall. Is there another script that can be run, or is the vmware-config.pl file just missing? The PDF manual for 2.5 references vmware-config.pl... Thanks

0 Kudos
30 Replies
admin
Immortal
Immortal

It should build/install the modules when you try to start up if they're not available. If that doesn't work for whatever reason you can try running vmware-modconfig --console --install-all.

-jay

0 Kudos
dzeman
Contributor
Contributor

thanks for the reply. vmware-modconfig does the trick for manually compiling new modules. It is not rebuilding and installing automatically on boot however. Using CentOS 5.2 x86_64. Is vmware-config.pl being phased out then?

0 Kudos
Elguapaul
Contributor
Contributor

I apologize for intruding into this thread, however, I too was looking for the config.pl. I would like to change the network mappings (vmnet0 -> ethX and such). Is there a tool I could use to do this?

Again... sorry for intruding.

0 Kudos
guyg61
Contributor
Contributor

Ditto.... Recently installed the latest VMware Player 2.5 on a Linux Host and cannot find the vmware-config.pl. The documentation makes reference to it. Is there another tool available that takes its place? Or is is just missing?

Guy G

0 Kudos
CDH_COM-jasonc-
Contributor
Contributor

I ran into this when I tried to install a 32-bit RPM on a 64-bit OS. Installing from the bash prompt 'rpm -Uhv VMware-Player...rpm' showed me the error I needed to see...

0 Kudos
Raydude
Contributor
Contributor

For vmplayer 2.5 you can do this:

vmware-networks --migrate-network-settings /your_path/your.vmx

This will import your settings from your vmx.

Raydude

0 Kudos
tinti1234
Contributor
Contributor

Have the same problem, re-compiling of the module works the way described in this thread, but changing the IP address isn't working this way.

Does somebody knows how I can change the IP address for vmnet8?

0 Kudos
johnb128
Contributor
Contributor

I'm also missing vmware-config.pl. I'm trying to disable bridging and was able to do that in previous versions with vmware-config.pl.

Is there a new way to configure the network?

0 Kudos
ritchiev
Contributor
Contributor

I am having difficulties, as in earlier version I could change the config through vmware-config.pl (Ubuntu 8.04 host, LTSP), the eth0 is the internal for the LTSP, eth1 for the external (www etc). Now I cannot change the eth0 to eth1 for bridging, and if I change the config file manually then the problem is not fixed some how. Does anybode can give me a hand of how to to it.

Thanks, Richard

0 Kudos
grantstreet
Contributor
Contributor

I have seen this when you try to install the RPM when /dev/tty is not availible. eg install the RPM from rc.local. The way the installer works is that it unpackages an executable into a temp directory and executes it reading from /dev/tty. It is this executable that installs all the files, you can see this by running rpm -ql --scripts VMware-Player . If this command fails for any reason the vmware files will not exist but the OS will think that the RPM is installed. This could explain your symptoms or at least you will know why your symptoms have occured. I have another thread about this with no response.

http://communities.vmware.com/message/1101419

0 Kudos
mheslep
Contributor
Contributor

Well after installing the rpm, and then again trying with just the bundle on 2.5.1, none of the vmxxx modules are installed and /etc/init.d/vmware fails to start. So the configuration done at install time failed to do what it needed to do. Then 'vmware-modconfig --console --install-all' gives a segfault. Arg!! There's no mention of removal of the long used vmware-config.pl (perl) based tool in the release notes, nor the major switch over to python. ????

Fedora 10

Linux 2.6.27.7-134.fc10.x86_64 #1 SMP Mon Dec 1 22:21:35 EST 2008 x86_64 x86_64 x86_64 GNU/Linux

  1. vmplayer

Logging to /tmp/vmware-root/setup-18572.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

0 Kudos
mwichmann
Contributor
Contributor

I guess the subject line isn't helpful any more; it's not the end of the world that the command we're used to doesn't exist any more, but it is a big problem that the replacement segfaults - and there doesn't seem to be a sane way to debug it. It's failing for me, too - I've tried the 64bit rpm (more on that later) and the bundle, both, and they appear to work fine but the modules aren't found. When running the command indicated here, it just fails:

  1. vmware-modconfig --console --install-all

Segmentation fault

Again, Fedora 10 x64 version is the host.

On the rpm, if you're listening VMware, the new scheme is horrid, please don't do this. The purpose of using the package manager is to be able to track the files installed, be able to verify them, etc. If this is not the result of installing a package through the package manager, it's not worth doing at all. This scheme installs the bundle in a temporary location, then the postinstall script runs the bundle and then removes it! This means that the only file actually installed by the rpm does not exist on the system after the installation is complete; meanwhile the whole set of files actually installed is nowhere tracked by the package manager. If you're going to do things this way...well... just forget about distributing an rpm and tell people to use the bundle, there's no difference except with the bundle people at least won't have an apparent broken package should they run "rpm --verify". This is bad enough that when distros start doing 3rd-party whitelist/blacklist settings (probably something that will become prevalent quite soon), I can pretty much guarantee vmware player and anything else that uses this scheme will end up being blacklisted.

0 Kudos
Speedbird
Contributor
Contributor

Hi there,

I am having the same issue (installing either the RPM or the .bundle versions) (My System is a Fedora 10, Kernel Version 2.6.27.9-159.fc10.x86_64). I believe there are two main problem here: (1) that the installation itself fails and also fails to report that back to the user, and (2) the reason that it fails is that it cannot compile a kernel module, here is a snippet from /var/log/vmware-installer:

Configuring Bridged network vmnet0 Configuring hostonly network vmnet1, probing for unused subnet ... Configuring NAT network vmnet8, probing for unused subnet ... Configured default networks - Bridged, Hostonly, NAT Stopping cups: \[ OK \] Starting cups: \[ OK \] Unable to install kernel modules Using UI type null Opening database file /etc/vmware/database Stopping VMware services: Virtual machine communication interface\[ OK \] Virtual machine monitor\[ OK \] Blocking file system\[ OK \]

And then in the same log file I see a command line usage dump from gconftool-2 which tells me that the installer script probably tried to execute it with invalid/obsolete parameters

I am actually surprised that just a few people have reported this issue, I just hope this does not mean that FC users are declining :smileygrin:

And finally, I believe the ulprit is the installation of /usr/lib/vmware/modules/source/vmmon.tar which is added bythe installer, it is failing trying to compile some header files that are not located in the approprtiate directories in the kernel source (local) tree (asm and linus folders specifically), there could be more issues like this one though, I hope this helps a bit.

Thanks,

SB

0 Kudos
RonnieD
Contributor
Contributor

Hi there,

after browsing the net i found the following solution.

-


The vmware-config.pl script has been incorporated into the

installation routine so you can’t issue it via command line anymore,

but VmWare won’t remove this without replacing it with something else

(they’re not Microsoft :P) so you can issue the following command to

force the reconfiguration and reinstallation of kernel modules :

+vmware-modconfig –console –install-all +

This will make the actual seg-fault error show up now simply issue :

mv /usr/lib/vmware/modules/binary /usr/lib/vmware/modules/binary.old (or whatever name you prefer, this is just to rename the binary directory to something else).

Now everything should be fixed and you can issue again :

+vmware-modconfig –console –install-all +

-


It worked for me on opensuse 11.1 and vmplayer 2.5.1

Not sure if these files where there before installation and made it fail or these files are placed there by the installer.

Have fun!

0 Kudos
mwichmann
Contributor
Contributor

Yes, this does indeed work for me. Thanks!

0 Kudos
mhanby
Contributor
Contributor

Thanks RonnieD, that was the command that I needed.

I installed VMware Player 2.5.1 on Fedora 10 i386 using "rpm -i vm*" and didn't get anything in the output that indicated an error:

Here's the command and output for reference:

$ sudo rpm -ivh ~/Download/VMware/VMware-Player-2.5.1-126130.i386.rpm 
Preparing...                ########################################### [100%]
   1:VMware-Player          ########################################### [100%]
Extracting VMware Installer...done.
Installing VMware Installer 1.0
Copying files...
Configuring...
Installing VMware Player 2.5.1
Copying files...
Configuring...
Installing VMware Player 2.5.1
Copying files...
Configuring...
Installation was successful

But attempting to start vmware service after resulted in these failures:

$ sudo /sbin/service vmware start
Starting VMware services:
   Virtual machine monitor                                 [FAILED]
   Virtual machine communication interface                 [  OK  ]
   Blocking file system                                    [  OK  ]
   Virtual ethernet                                        [FAILED]

0 Kudos
edmeades
Contributor
Contributor

mv /usr/lib/vmware/modules/binary /usr/lib/vmware/modules/binary.old (or whatever name you prefer, this is just to rename the binary directory to something else).

Thankyouthankyouthankyouthankyouthankyouthankyouthankyouthankyouthankyouthankyouthankyou

I didn't get more info when I tried the command the first time, but renaming the binary directory forced a recompile and got me past the segfault.

Thanks again!

0 Kudos
aztrix
Contributor
Contributor

fair play to you ronnie, that did the trick :smileygrin:

cheers

bruce

0 Kudos
JDThompson
Contributor
Contributor

Trying to install VWware-Player-2.5.1-126130.x86_64.rpm on Fedora 10 x86_64 I cannot get the vmplayer application to work. It appears the modules have not been properly configured, and the lack of vmware-confiog.pl has made it exceedingly difficult to figure out where the problem lies. I've tried all the suggestions in this thread -- uninstalling VMware-Player, unpacking the .bundle from the rpm file and running "sudo VMware-Player-2.5.1-126130.x86_64.bundle -r" -- I get a lovely gui install window which cheerfully tells me that installation has been successful, but it still doesn't work. I've run "vmware-modconfig --console --install-all" and it seg-faults:

  1. vmware-modconfig --console --install-all

Segmentation fault

#

What's the deal here? Is there some significant advantage to hiding everything in that stupid bundle, or can we have vmware-config.pl back again, please?

0 Kudos