Home | Docs | Forums | Lists | Bugs | Planet | Store | GMN | Get Gentoo!

Full Text Bug Listing

Hi,

After I do a vmware-config.pl, I can't run "/etc/init.d/vmware start" or I get
an "unconfigured" error message.

However, if I run "/etc/vmware/init.d/vmware stop" then "/etc/init.d/vmware
start", it works fine:

doesn't work:
vmware-config.pl; /etc/init.d/vmware start

does work:
vmware-config.pl; /etc/vmware/init.d/vware stop; /etc/init.d/vware start

I assume this is because vmware-config.pl starts vmware, but it doesn't use the
gentoo init.d script to start it - it uses the vmware script, which then means
the gentoo script doesn't know it's started.  or something.

Should vmware-config.pl be patched for gentoo?

*** This bug has been marked as a duplicate of 107930 ***

OK, I finally got around to re-opening, sorry about the delay!

Take close note of the paths of the initscripts in my original post
/etc/vmware/... and /etc/init.d/...

The problem happens because vmware-config.pl starts /etc/vmware/init.d/vmware
which is not the "gentoo way" of starting it, and so gentoo doesn't know it's
started.  When you then do a `/etc/init.d/vmware start`, gentoo tries to start
it again, fails (cause its already started) and then puts the "not_configured"
file in /etc/vmware.  To fix it that:

rm /etc/vmware/not_configured; /etc/vmware/init.d/vmware stop;
/etc/init.d/vmware/start

So my proposal is to patch vmware-config.pl so it runs /etc/init.d/vmware
instead of /etc/vmware/init.d/vmware (I had a look, but couldn't figure out how
to do it - thats one hellova script :)

I'm going to assume that you mean on vmware-workstation, since you never said
anywhere.

sorry, app-emulation/vmware-workstation-4.5.3.19414 is the current one I'm
using.

Please try the latest revision and see if the problem is solved.  I'm not sure
why you're having this problem, since I cannot reproduce it.

Once I could actually download the thing... (something wierd going on with file
sizes) I upgraded to app-emulation/vmware-workstation-4.5.3.19414-r3


iain@orpheus ~ $ sudo emerge -u vmware-workstation
iain@orpheus ~ $ sudo `which vmware-config.pl `
...
iain@orpheus ~ $ sudo /etc/init.d/vmware start
 * Starting VMware services:                                              [ ok
]
 *   Virtual machine monitor                                              [ !!
]
 *   Virtual ethernet                                                     [ !!
]
 *   Bridged networking on /dev/vmnet0                                    [ !!
]
iain@orpheus ~ $ sudo rm /etc/vmware/not_configured
iain@orpheus ~ $ sudo /etc/vmware/init.d/vmware stop
Stopping VMware services:
   Virtual machine monitor                                             done
   Bridged networking on /dev/vmnet0                                   done
   Virtual ethernet                                                    done
iain@orpheus ~ $ sudo /etc/init.d/vmware start
 * Starting VMware services:                                              [ ok
]
 *   Virtual machine monitor                                              [ ok
]
 *   Virtual ethernet                                                     [ ok
]
 *   Bridged networking on /dev/vmnet0                                    [ ok
]

Notice how the only thing I do to make it work, is delete not_configured, stop
the vmware init file, and start the gentoo init file.  Strange?

thanks.

Still happens with app-emulation/vmware-workstation-4.5.3.19414-r4

Well, I have never been able to reproduce this, so I'm really at a loss. 
Perhaps a newer baselayout has cleared this up?  Can someone who is
experiencing this give me the following:

vmware-workstation version
baselayout version
module-init-tools version
kernel version
udev version

Thanks

Sure!

app-emulation/vmware-workstation-4.5.3.19414-r4
sys-apps/baselayout-1.12.5
sys-apps/module-init-tools-3.2.2-r1
sys-kernel/suspend2-sources-2.6.18
sys-fs/udev-100-r2

(doesn't seem to be dependant on whether I start from hibernate, or clean boot)

I hear there's a new version of vmware-workstation out, so I'll try that now...

Created an attachment (id=98346) [details]
output from vmware-config.pl, etc

Here's the output from the commands I need to run to get it going.  Hope it
helps!

Chris, it looks as though the workstation-4.5 series is missing the
004_all_do-not-build-modules.patch (and several of the others) and also the
use-modprobe-over-insmod patch.  My guess is that the modprobe-over-insmod
patch will fix it, but I'll leave it to you for testing since I'm guessing the
original batch of patches were probably not all there for a reason...

Good eye.  I hadn't noticed that.  I think it actually is more a by-product of
the changes in how the patches were done, rather than intentional, as I can't
think of a reason why they were skipped.  I'm testing right now with some
changes in the patches applied and will report back once I've found something.

OK.  I've updated the patches in CVS.  Can you try merging vmware-workstation
again and see if this resolves the issue?

[In a small voice] where's CVS?

Hehehe,

Iain, CVS is just the place that the main repository is stored, and it's how
the developers can write to the portage tree.  Once it's in the main (single)
CVS repository, it gets pulled (every hour or so) by many mirrors around the
world which then offer the repository out (in read-only form) over rsync, which
is where you eventually will read it from when you do emerge --sync.

In short, it's just our way of saying it'll be available if you do an emerge
--sync in a few hours and remerge the affected package.  Hope that explains
it...  5:)

Oh, ok.  I'm used to CVS as being "check it out from cvs and compile it
yourself".  I think I already got 
app-emulation/vmware-workstation-4.5.3.19414-r5 from `emerge --sync` before I
saw your post.

Bad news, same behaviour.

Just a thought: I have in the past installed my own version of the
vmware-any-any thing - could there be something stale lying around?  I heard
once of a program that checked every file on your gentoo system and reported
orphaned files - do you think it's worth trying it?

or would a --noconfmem help any?


I did some investigation - I couldn't understand why the gentoo init script
fails when all it does is call the vmware init script.  So I removed the
"vmware-prettify" and set VMWARE_DEBUG, and this is the output, right after a
vmware-config.pl:

$ sudo /etc/init.d/vmware start
Starting VMware services:
   Virtual machine monitorinsmod: error inserting
'/lib/modules/2.6.18-suspend2/misc/vmmon.o': -1 File exists
                                                                      failed
   Virtual ethernetinsmod: error inserting
'/lib/modules/2.6.18-suspend2/misc/vmnet.o': -1 File exists
                                                                      failed
   Bridged networking on /dev/vmnet0eth0: Resource deadlock avoided
                                                                      failed

as you can see, it's failing because the modules are already loaded (by
vmware-config.pl).

can someone check the vmware init file:
$ cksum /etc/vmware/init.d/vmware
3229718463 32373 /etc/vmware/init.d/vmware

other than that, I'm lost...

Hmm, I emerge -C'd and deleted everything vmware-ish (init-scripts and all). 
Then I re-emerged it, and now I can't start it at all, no matter what I do! The
init script keeps telling me vmware is not configured.

When I run vmware-config.pl, it seems to complete without errors.

This is what the init script says (with the prettify output bypassed, and
VMWARE_DEBUG set):

$ sudo /etc/init.d/vmware start
Starting VMware services:
   Virtual machine monitor                                             done
   Virtual ethernet                                                    done
   Bridged networking on /dev/vmnet0Module version mismatch. Please update
host.: Success
                                                                      failed

re-merging vmware-modules or re-running vmware-config.pl seems to make no
difference... *sigh*...

Please emerge --sync again.  What you got in comment #16 tells me that you
didn't get the updated ebuild, as it should now use modprobe instead of insmod.

Ah ok, I saw the update to -r5 on sep 29th, so I thought that was the one you'd
just checked in.

I just synced, and got app-emulation/vmware-workstation-4.5.3.19414-r6, but
vmware-config.pl fails (again bypassing the prettify output, and setting
VMWARE_DEBUG):


$ sudo `which vmware-config.pl`
Making sure services for VMware Workstation are stopped.

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

You have already setup networking.

Would you like to skip networking setup and keep your old settings as they are?
(yes/no) [yes]

Do you want this program to automatically configure your system to allow your
virtual machines to access the host's filesystem? (yes/no/help) [no]

Starting VMware services:
   Virtual machine monitor                                             done
   Virtual ethernet                                                    done
   Bridged networking on /dev/vmnet0Module version mismatch. Please update
host.
: Success
                                                                      failed

The configuration of VMware Workstation 4.5.3 build-19414 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


even thought it says it was successful, it wasn't... as you can see, something
to do with "Module version mismatch"?

thanks for your time on this...

Ok, that's much better now.  Now could you please double check that vmmon and
vmnet are not loaded (do lsmod).  If they are, please go for a reboot, or rmmod
them.  Then give vmware-modules a rebuild, you should be using
vmware-modules-1.0.0.11 (and not any higher versions).  Then start vmware again
and see if that fixes the situation.  If it doesn't, please attach the output
from emerging vmware-modules and we'll try and see what's going on.  If it
does, then please do the happy dance...  5:)

(In reply to comment #20)
> Ok, that's much better now.

I'm glad you think so ;)

>  Now could you please double check that vmmon and
> vmnet are not loaded (do lsmod).  If they are, please go for a reboot, or rmmod
> them.

modprobe -r'd them.

>  Then give vmware-modules a rebuild, you should be using
> vmware-modules-1.0.0.11 (and not any higher versions).

it wanted to pull in 1.0.0.15, so I forced 1.0.0.11.

>  Then start vmware again

got this message:

$ sudo /etc/init.d/vmware start
 * 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.                          [ !!
]

How come the modules aren't built as part of "vmware-config.pl" now?

> and see if that fixes the situation.  If it doesn't, please attach the output
> from emerging vmware-modules and we'll try and see what's going on.  If it
> does, then please do the happy dance...  5:)

*lol* I wish I was doing the happy dance...

I emerged vmware-modules again, and started vmware init.d service and got the
same message.  Once again without the pretty output:


$ sudo /etc/init.d/vmware start
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

output to follow...

Created an attachment (id=98701) [details]
output from `emerge -va =vmware-modules-1.0.0.11`

D'oh!

Well, I've had another bug come in relating to vmware-workstation-4.5 and the
module system.  And, during all of this, we've had a few difficulties dealing
with an openssl so it's gonna take a couple of days to sort out.  If you really
want to try and get it working today, you can try unmasking -r7 of
vmware-workstation, and removing the VMWARE_VER line from
/usr/portage/eclass/vmware-mod.eclass.  If that's all a bit much, then give it
a couple of days and hopefully we'll get it all sorted out.  Sorry for the
mess...  5:(

(In reply to comment #23)
> D'oh!

and this is your pearl of wisdom, that I stayed up late especially to hear ;)

>   And, during all of this, we've had a few difficulties dealing
> with an openssl so it's gonna take a couple of days to sort out.

I noticed a libssl-something unpack error when I tried to downgrade to -r4...

>  If you really
> want to try and get it working today, you can try unmasking -r7 of
> vmware-workstation, and removing the VMWARE_VER line from
> /usr/portage/eclass/vmware-mod.eclass.

yes, I really want to try and get it working - had I known I would have stuck
with -r4.  But I do run unstable after all 5:)
      (adopted your hair-do)    -----------^

anyway, I'm doing some plc programming atm and I need vmware to run the
programming IDE.  Otherwised I'd have to boot to windows (yeuch).  Just making
idle chatter till the compile finishes...

>   Sorry for the mess...  5:(

not at all - you and Chris have been more than helpful.  I'm the one running
~x86 after all :)  some of my bug reports (even when I go so far as providing
pathces) just get the response "why the hell would I want to apply that patch
to my ebuild?"...

ok it's compiled (-r7 that is) and guess what? same modules problem.  I get
"not configured" after recompiling vmware-modules and starting
/etc/init.d/vmware...

looks like I'm booting to windows for a while...

cya.

HALLELUJAH! IT WORKS! *happy dance*

The final working combination is:
app-emulation/vmware-workstation-4.5.3.19414-r7
app-emulation/vmware-modules-1.0.0.11

it didn't work last night because I was using vmware-modules-1.0.0.15...

(In reply to comment #24)
> and this is your pearl of wisdom, that I stayed up late especially to hear ;)

that was a joke by the way :)

Thank you _very_ much.  Now I won't touch vmware in the middle of a project
again!

Hold the phone... it doesn't work with 2.6.18 anymore... I re-merged
vmware-modules (1.0.0.11) and vmware-config, and I get the "Module version
mismatch" problem.  Can anyone shed any light?

$ sudo vmware-config.pl 
Making sure services for VMware Workstation are stopped.

 * WARNING:  vmware has not yet been started.

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

Configuring a bridged network for vmnet0.

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

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

Do you want this program to automatically configure your system to allow your 
virtual machines to access the host's filesystem? (yes/no/help) [no] no

 * Starting VMware services:                                            [ ok ]
 *   Virtual machine monitor                                            [ ok ]
 *   Virtual ethernet                                                   [ ok ]
Module version mismatch. Please update host.
: Success
 *   Bridged networking on /dev/vmnet0                                  [ !! ]

The configuration of VMware Workstation 4.5.3 build-19414 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

That's a know issue which I thought I'd fixed.  Apparently I only ever fixed it
in the overlay, sorry about that.  I'll commit it to the main tree as soon as I
get back home (so by the end of the day).  I do apologize about that...  5:(

*woot* it's aliiiive!

app-emulation/vmware-modules-1.0.0.11-r1
app-emulation/vmware-workstation-4.5.3.19414-r7
sys-kernel/suspend2-sources-2.6.18

I think this bug can be closed :)  Thanks heaps to all who helped.

Cool, glad you got it all working finally...  5:)  

Marking as FIXED.  Please feel free to reopen this if the problem returns.