VMWare Fails to Start

Message

andrewd18 · Post by **andrewd18** » Fri Jan 05, 2007 6:59 pm

I have this issue with both vmware player and vmware workstation... whenever I try to start the /etc/init.d/vmware service, it fails saying I haven't configured it. However, it even fails when I've just finished configuring it.

Here's how I set up the configuration; as you can see at the bottom, it's a PITA.

vmware-modules is installed and configured for the running kernel, so it's probably not that. I can post the output of that emerge, though, because there were a few warnings I wasn't familiar with (and yet the compile seemed to have worked...).

Code: Select all

StubbornAesthetics bin # ./vmware-config.pl
Making sure services for VMware Workstation are stopped.

 * Caching service dependencies ...                                                                                                                    [ ok ]
 * WARNING:  vmware has not yet been started.

You must read and accept the End User License Agreement to continue.
Press enter to display it.


Do you accept? (yes/no) yes

Thank you.

Configuring fallback GTK+ 2.4 libraries.

Do you want networking for your virtual machines? (yes/no/help) [yes]

Configuring a bridged network for vmnet0.

Your computer has multiple ethernet network interfaces available: ath0, eth0,
vmnet1, vmnet8. Which one do you want to bridge to vmnet0? [eth0] ath0

The following bridged networks have been defined:

Do you wish to configure another bridged network? (yes/no) [no]

Do you want to be able to use NAT networking in your virtual machines? (yes/no)
[yes] yes

Configuring a NAT network for vmnet8.

Do you want this program to probe for an unused private subnet? (yes/no/help)
[yes] yes

Probing for an unused private subnet (this can take some time)...

The subnet 192.168.7.0/255.255.255.0 appears to be unused.

The following NAT networks have been defined:

Do you wish to configure another NAT network? (yes/no) [no]

Do you want to be able to use host-only networking in your virtual machines?
[yes]

Configuring a host-only network for vmnet1.

Do you want this program to probe for an unused private subnet? (yes/no/help)
[yes]

Probing for an unused private subnet (this can take some time)...

The subnet 172.16.170.0/255.255.255.0 appears to be unused.

The following host-only networks have been defined:

Do you wish to configure another host-only network? (yes/no) [no]

 * Service vmware starting
 Vmware Workstation is installed, but it has not been (correctly) configured
 for the running kernel.
 Please ensure that the modules have been compiled for this kernel:
 emerge --oneshot vmware-modules
 Also ensure Vmware Workstation has been configured:
 /opt/vmware/workstation/bin/vmware-config.pl
 VMware is not properly configured! See above.                                                                                                                                                                                                                                                  [ !! ]
 * ERROR:  vmware failed to start

The configuration of VMware Workstation 5.5.3 build-34685 for Linux for this
running kernel completed successfully.

You can now run VMware Workstation by invoking the following command:
"/opt/vmware/workstation/bin/vmware".

Enjoy,

--the VMware team

nahpets · Post by **nahpets** » Fri Jan 05, 2007 9:29 pm

did you do

Code: Select all

# rm /etc/vmware/not_configured

before starting vmware?

andrewd18 · Post by **andrewd18** » Fri Jan 05, 2007 9:51 pm

Yes I did. Once that file is removed, the vmware init script gives me this, which is much more detailed:

Code: Select all

 * Service vmware starting



                                                                                                                                                       [ !! ]


                                                                                                                                                       [ !! ]
 * ERROR:  vmware failed to start

nahpets · Post by **nahpets** » Fri Jan 05, 2007 11:09 pm

I've been able to fix vmware by rebooting. If you have vmnet and friends running, then the init script won't work etc. The easiest way to make sure that NOTHING vmware related is loaded is to reboot and start VMware from scratch.

Ast0r · Post by **Ast0r** » Sat Jan 06, 2007 2:52 am

Have you tried

Code: Select all

emerge vmware-modules

... followed by

Code: Select all

/opt/vmware/workstation/bin/vmware-config.pl

???

andrewd18 · Post by **andrewd18** » Sun Jan 07, 2007 5:49 am

Yes, as I mentioned in the original post. Doesn't help. That being said, I do get some warnings while compiling it, so I'll post those:

Code: Select all

StubbornAesthetics ~ # emerge vmware-modules
Calculating dependencies... done!

>>> Emerging (1 of 1) app-emulation/vmware-modules-1.0.0.15-r1 to /

QA Notice: ECLASS 'pax-utils' inherited illegally in app-emulation/vmware-modules-1.0.0.15-r1

 * vmware-any-any-update105.tar.gz MD5 ;-) ...                                                                                                         [ ok ]
 * vmware-any-any-update105.tar.gz RMD160 ;-) ...                                                                                                      [ ok ]
 * vmware-any-any-update105.tar.gz SHA1 ;-) ...                                                                                                        [ ok ]
 * vmware-any-any-update105.tar.gz SHA256 ;-) ...                                                                                                      [ ok ]
 * vmware-any-any-update105.tar.gz size ;-) ...                                                                                                        [ ok ]
 * checking ebuild checksums ;-) ...                                                                                                                   [ ok ]
 * checking auxfile checksums ;-) ...                                                                                                                  [ ok ]
 * checking miscfile checksums ;-) ...                                                                                                                 [ ok ]
 * checking vmware-any-any-update105.tar.gz ;-) ...                                                                                                    [ ok ]

QA Notice: ECLASS 'pax-utils' inherited illegally in app-emulation/vmware-modules-1.0.0.15-r1

 * Determining the location of the kernel source code
 * Found kernel source directory:
 *     /usr/src/linux
 * Found kernel object directory:
 *     /lib/modules/2.6.18-gentoo-r5/build
 * Found sources for kernel version:
 *     2.6.18-gentoo-r5
>>> Unpacking source...
>>> Unpacking vmware-any-any-update105.tar.gz to /var/tmp/portage/vmware-modules-1.0.0.15-r1/work
>>> Unpacking ./vmware-any-any-update105/vmmon.tar to /var/tmp/portage/vmware-modules-1.0.0.15-r1/work
 * Applying various patches (bugfixes/updates) ...
 *       000_all_makefile-include-directory.patch ...                                                                                                  [ ok ]
 *       010_all_makefile-vm-build-no-unused-warnings.patch ...                                                                                        [ ok ]
 *       020_all_epoll-def-warnings.patch ...                                                                                                          [ ok ]
 * Done with patching
 * Converting vmmon-only/Makefile to use M= instead of SUBDIRS= ...                                                                                    [ ok ]
>>> Unpacking ./vmware-any-any-update105/vmnet.tar to /var/tmp/portage/vmware-modules-1.0.0.15-r1/work
 * Applying various patches (bugfixes/updates) ...
 *       000_all_makefile-include-directory.patch ...                                                                                                  [ ok ]
 *       010_all_makefile-vm-build-no-unused-warnings.patch ...                                                                                        [ ok ]
 *       020_all_epoll-def-warnings.patch ...                                                                                                          [ ok ]
 * Done with patching
 * Converting vmnet-only/Makefile to use M= instead of SUBDIRS= ...                                                                                    [ ok ]
>>> Source unpacked.
>>> Compiling source in /var/tmp/portage/vmware-modules-1.0.0.15-r1/work ...
 * Preparing vmmon module
Using 2.6.x kernel build system.
make -C /usr/src/linux/include/.. M=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-2.6.18-gentoo-r5'
make[1]: warning: jobserver unavailable: using -j1.  Add `+' to parent make rule.
  CC [M]  /var/tmp/portage/vmware-modules-1.0.0.15-r1/work/vmmon-only/linux/driver.o
  CC [M]  /var/tmp/portage/vmware-modules-1.0.0.15-r1/work/vmmon-only/linux/hostif.o
  CC [M]  /var/tmp/portage/vmware-modules-1.0.0.15-r1/work/vmmon-only/common/cpuid.o
  CC [M]  /var/tmp/portage/vmware-modules-1.0.0.15-r1/work/vmmon-only/common/hash.o
  CC [M]  /var/tmp/portage/vmware-modules-1.0.0.15-r1/work/vmmon-only/common/memtrack.o
  CC [M]  /var/tmp/portage/vmware-modules-1.0.0.15-r1/work/vmmon-only/common/phystrack.o
  CC [M]  /var/tmp/portage/vmware-modules-1.0.0.15-r1/work/vmmon-only/common/task.o
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for C/ObjC but not for C++
cc1plus: warning: command line option "-Wdeclaration-after-statement" is valid for C/ObjC but not for C++
cc1plus: warning: command line option "-Wno-pointer-sign" is valid for C/ObjC but not for C++
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for C/ObjC but not for C++
/var/tmp/portage/vmware-modules-1.0.0.15-r1/work/vmmon-only/common/task_compat.h: In function void Task_Switch_V45(VMDriver*, Vcpuid):
/var/tmp/portage/vmware-modules-1.0.0.15-r1/work/vmmon-only/common/task_compat.h:1713: warning: sysenterState$validEIP may be used uninitialized in this function
/var/tmp/portage/vmware-modules-1.0.0.15-r1/work/vmmon-only/common/task_compat.h:1713: warning: sysenterState$cs may be used uninitialized in this function
/var/tmp/portage/vmware-modules-1.0.0.15-r1/work/vmmon-only/common/task_compat.h:1713: warning: sysenterState$rsp may be used uninitialized in this function
/var/tmp/portage/vmware-modules-1.0.0.15-r1/work/vmmon-only/common/task_compat.h:1713: warning: sysenterState$rip may be used uninitialized in this function
  CC [M]  /var/tmp/portage/vmware-modules-1.0.0.15-r1/work/vmmon-only/common/vmx86.o
  CC [M]  /var/tmp/portage/vmware-modules-1.0.0.15-r1/work/vmmon-only/vmcore/compat.o
  CC [M]  /var/tmp/portage/vmware-modules-1.0.0.15-r1/work/vmmon-only/vmcore/moduleloop.o
  LD [M]  /var/tmp/portage/vmware-modules-1.0.0.15-r1/work/vmmon-only/vmmon.o
  Building modules, stage 2.
  MODPOST
  CC      /var/tmp/portage/vmware-modules-1.0.0.15-r1/work/vmmon-only/vmmon.mod.o
  LD [M]  /var/tmp/portage/vmware-modules-1.0.0.15-r1/work/vmmon-only/vmmon.ko
make[1]: Leaving directory `/usr/src/linux-2.6.18-gentoo-r5'
cp -f vmmon.ko ./../vmmon.o
 * Preparing vmnet module
Using 2.6.x kernel build system.
make -C /usr/src/linux/include/.. M=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-2.6.18-gentoo-r5'
make[1]: warning: jobserver unavailable: using -j1.  Add `+' to parent make rule.
  CC [M]  /var/tmp/portage/vmware-modules-1.0.0.15-r1/work/vmnet-only/driver.o
  CC [M]  /var/tmp/portage/vmware-modules-1.0.0.15-r1/work/vmnet-only/hub.o
  CC [M]  /var/tmp/portage/vmware-modules-1.0.0.15-r1/work/vmnet-only/userif.o
  CC [M]  /var/tmp/portage/vmware-modules-1.0.0.15-r1/work/vmnet-only/netif.o
  CC [M]  /var/tmp/portage/vmware-modules-1.0.0.15-r1/work/vmnet-only/bridge.o
  CC [M]  /var/tmp/portage/vmware-modules-1.0.0.15-r1/work/vmnet-only/procfs.o
  CC [M]  /var/tmp/portage/vmware-modules-1.0.0.15-r1/work/vmnet-only/smac_compat.o
  CC [M]  /var/tmp/portage/vmware-modules-1.0.0.15-r1/work/vmnet-only/smac_linux.x86_64.o
  LD [M]  /var/tmp/portage/vmware-modules-1.0.0.15-r1/work/vmnet-only/vmnet.o
  Building modules, stage 2.
  MODPOST
  CC      /var/tmp/portage/vmware-modules-1.0.0.15-r1/work/vmnet-only/vmnet.mod.o
  LD [M]  /var/tmp/portage/vmware-modules-1.0.0.15-r1/work/vmnet-only/vmnet.ko
make[1]: Leaving directory `/usr/src/linux-2.6.18-gentoo-r5'
cp -f vmnet.ko ./../vmnet.o
>>> Source compiled.
>>> Test phase [not enabled]: app-emulation/vmware-modules-1.0.0.15-r1

>>> Install vmware-modules-1.0.0.15-r1 into /var/tmp/portage/vmware-modules-1.0.0.15-r1/image/ category app-emulation
 * Installing vmmon module
 * Installing vmnet module
>>> Completed installing vmware-modules-1.0.0.15-r1 into /var/tmp/portage/vmware-modules-1.0.0.15-r1/image/

man:
strip: x86_64-pc-linux-gnu-strip --strip-unneeded
>>> Merging app-emulation/vmware-modules-1.0.0.15-r1 to /
--- /etc/
--- /etc/udev/
--- /etc/udev/rules.d/
>>> /etc/udev/rules.d/60-vmware.rules
--- /lib/
--- /lib/modules/
--- /lib/modules/2.6.18-gentoo-r5/
--- /lib/modules/2.6.18-gentoo-r5/misc/
>>> /lib/modules/2.6.18-gentoo-r5/misc/vmmon.ko
>>> /lib/modules/2.6.18-gentoo-r5/misc/vmnet.ko
>>> Safely unmerging already-installed instance...

QA Notice: ECLASS 'pax-utils' inherited illegally in app-emulation/vmware-modules-1.0.0.15-r1

--- cfgpro obj /lib/modules/2.6.18-gentoo-r5/misc/vmnet.ko
--- cfgpro obj /lib/modules/2.6.18-gentoo-r5/misc/vmmon.ko
--- cfgpro dir /lib/modules/2.6.18-gentoo-r5/misc
--- cfgpro dir /lib/modules/2.6.18-gentoo-r5
--- cfgpro obj /etc/udev/rules.d/60-vmware.rules
--- cfgpro dir /etc/udev/rules.d
--- cfgpro dir /etc/udev
--- !empty dir /lib/modules
--- !empty dir /lib
--- !empty dir /etc
 * Removing app-emulation/vmware-modules-1.0.0.15-r1 from moduledb.

QA Notice: ECLASS 'pax-utils' inherited illegally in app-emulation/vmware-modules-1.0.0.15-r1

>>> Regenerating /etc/ld.so.cache...
>>> Original instance of package unmerged safely.
 * Updating module dependencies for 2.6.18-gentoo-r5 ...                                                                                               [ ok ]
 * Adding module to moduledb.
>>> Regenerating /etc/ld.so.cache...
>>> app-emulation/vmware-modules-1.0.0.15-r1 merged.

QA Notice: ECLASS 'pax-utils' inherited illegally in app-emulation/vmware-modules-1.0.0.15-r1

>>> Recording app-emulation/vmware-modules in "world" favorites file...

>>> No packages selected for removal by clean.

>>> Auto-cleaning packages...

>>> No outdated packages were found on your system.


 * GNU info directory index is up-to-date.

StubbornAesthetics ~ #

andrewd18 · Post by **andrewd18** » Tue Jan 09, 2007 11:51 pm

Um... bump and stuff.

mrpdaemon · Post by **mrpdaemon** » Wed Jan 10, 2007 5:58 am

After you run the init script (and it fails) do you see vmnet and vmmon in the output of 'lsmod' ?

If not try to manually load them with:

modprobe vmnet
modprobe vmmon

If those fail run depmod and try again. If its still failing try

insmod /lib/modules/2.6.18-gentoo-r5/misc/vmmon.ko
insmod /lib/modules/2.6.18-gentoo-r5/misc/vmnet.ko

If you're seeing these modules loaded (in lsmod output) you should be able to start workstation. If it still complains about proper configuration remove /etc/vmware/not_configured and try again.

andrewd18 · Post by **andrewd18** » Wed Jan 10, 2007 12:46 pm

If I manually load the modules and remove not_configured, vmware starts but gets no ethernet. If I manually load the modules, remove not_configured, and then run "/etc/init.d/vmware start", it still errors out with no information, but then the /dev/vmnet0, etc. links are set up properly and vmware works just fine.

However, I have to do all that every time I want to start vmware. I shouldn't have to do that. That's what the init script is there for in the first place.

nahpets · Post by **nahpets** » Wed Jan 10, 2007 10:00 pm

andrewd18 wrote:If I manually load the modules and remove not_configured, vmware starts but gets no ethernet. If I manually load the modules, remove not_configured, and then run "/etc/init.d/vmware start", it still errors out with no information, but then the /dev/vmnet0, etc. links are set up properly and vmware works just fine.

However, I have to do all that every time I want to start vmware. I shouldn't have to do that. That's what the init script is there for in the first place.

Did you try running the init script after a reboot? As I mentioned earlier, I noticed that the init script complains if there's any VMWare related stuff already running/loaded.

andrewd18 · Post by **andrewd18** » Thu Jan 11, 2007 12:40 am

Rebooting does not change the situation.

nahpets · Post by **nahpets** » Thu Jan 11, 2007 6:20 am

andrewd18 wrote:Rebooting does not change the situation.

Oh well... I know it sounds stupid to reboot your linux machine, but that's what fixed vmware for me. From what I've seen, the vmware init scripts seem to be a little fragile and VMware can get borked pretty easily.

andrewd18 · Post by **andrewd18** » Thu Jan 11, 2007 1:03 pm

nahpets wrote:Oh well... I know it sounds stupid to reboot your linux machine, but that's what fixed vmware for me. From what I've seen, the vmware init scripts seem to be a little fragile and VMware can get borked pretty easily.

I don't mind rebooting my Linux machine anyway... the computer is loud enough that I turn it off at night. Besides; better a reboot for a possible fix than never to know.

MixedSoul · Post by **MixedSoul** » Tue Jan 23, 2007 11:46 pm

I'm having the exact same problem... have you found a solution for this?

andrewd18 · Post by **andrewd18** » Wed Jan 24, 2007 4:22 am

MixedSoul wrote:I'm having the exact same problem... have you found a solution for this?

Code: Select all

su -
modprobe vmmon
modprobe vmnet
/etc/init.d/vmware start
rm /etc/conf.d/vmware/not_configured
exit
vmplayer

That's the series of commands I run, and it works fine... but it's certainly not elegant.

MixedSoul · Post by **MixedSoul** » Wed Jan 24, 2007 1:00 pm

Well... the problem is that i don't want to have to do that each time i need VMware

but i guess there's no solution for that yet

andrewd18 · Post by **andrewd18** » Wed Jan 24, 2007 2:34 pm

I'm not saying I like it either.

MixedSoul · Post by **MixedSoul** » Wed Jan 24, 2007 3:00 pm

I guess we'll have to wait till someone come up with a better solution =P
Anyway... my windows is running fine and..
is it just me or it runs faster then when natively booted (at least the internet speeds and general system functionality)

rlittle · Post by **rlittle** » Mon Jan 29, 2007 10:46 pm

I'm having some strange problems with vmware-workstation after emerging it. I had no problems with the straight VMware tarball and built-in installer, then I uninstalled it and emerged. I can't check things right now, but by posting here I won't have to hunt for this thread anymore.

rlittle · Post by **rlittle** » Tue Jan 30, 2007 12:30 am

Adding myself to the "vmware" group and rebooting took care of basically all my problems.

andrewd18 · Post by **andrewd18** » Tue Jan 30, 2007 4:17 am

rlittle wrote:Adding myself to the "vmware" group and rebooting took care of basically all my problems.

I wish it were that easy for me.

Code: Select all

vmware:x:450:andrew,root

miscdebris · Post by **miscdebris** » Sat Feb 03, 2007 3:57 am

Are you trying to bridge a wireless interface? On my laptop, I was trying to bridge both my lan and wireless adapters, and I couldn't figure out why it failed. So I dug around in /etc/init.d/vmware and found "/etc/vmware/init.d/vmware". When I ran it, it told me it failed on vmnet2, which was my wireless bridge. I reconfigured it to only bridge eth0, and it worked fine. I then set vmnet0 to bridge only to ath0, my wireless, and it fails every time. It would seem that vmware does not like to bridge to wireless.

andrewd18 · Post by **andrewd18** » Sat Feb 03, 2007 5:33 am

miscdebris wrote:Are you trying to bridge a wireless interface? On my laptop, I was trying to bridge both my lan and wireless adapters, and I couldn't figure out why it failed. So I dug around in /etc/init.d/vmware and found "/etc/vmware/init.d/vmware". When I ran it, it told me it failed on vmnet2, which was my wireless bridge. I reconfigured it to only bridge eth0, and it worked fine. I then set vmnet0 to bridge only to ath0, my wireless, and it fails every time. It would seem that vmware does not like to bridge to wireless.

That might be why; I also have an Atheros card that I use for internet. So... if I needed internet, if I told it to bridge to eth0, wouldn't it get no connection at all (since my ethernet isn't connected?)?

miscdebris · Post by **miscdebris** » Sat Feb 03, 2007 5:51 am

If you only bridge to ethernet, you won't be able to get directly connected to the internet. However, you can use the NAT interface, and you'll be able to use the internet that way, without any bridging via your wireless. It works pretty well actually.

kalle2 · Post by **kalle2** » Fri Feb 09, 2007 1:06 pm

I had the same problem wirth vmware-workstation4.5.3.19414-r7 and vmware-modules 1.0.0.11 - it only worked if I did:

Code: Select all

su
modprobe vmmon
modprobe vmnet
/etc/init.d/vmware start
rm /etc/conf.d/vmware/not_configured

The reason was that "/etc/init.d/vmware start" did not load the vmnet/vmmon modules correctly:

Code: Select all

 * Starting VMware services:                                                                            [ ok ]
 *   Virtual machine monitor                                                                            [ !! ]
 *   Virtual ethernet                                                                                   [ !! ]
 *   Bridged networking on /dev/vmnet0                                                                  [ ok ]

I found out that this is caused by an error in the vmware init script (/etc/vmware/init.d/vmware):

Code: Select all

577 : vmware_load_module() {
578 :   /sbin/insmod -s -f "/lib/modules/`uname -r`/misc/$1.o" || exit 1
579 :   exit 0
580 : }

This tries to load vmnet.o and not vmnet.ko, but the modules are named .ko since some time ago. The solution was to change the ".o" to ".ko" in line 578.

Perhaps the people who maintain the ebuild can fix this?