| View previous topic :: View next topic |
| Author |
Message |
TrainedChimp
Tux's lil' helper
Joined: 25 Jun 2004
Posts: 87
Location: Just west of Earth
|
 Posted: Tue Oct 10, 2006 12:40 am Post subject: VMware-workstation not working after update once again. |
 |
|
Wow, I hate updating VMware-workstation I always have problems and I'm too stupid to remember how to fix them next time. I did a emerge -puDv world recently and missed the Vmware-workstation update in there.
| Code: | /etc/vmware # /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. |
So then I do an "emerge --oneshot vmware-modules" and now I have this
| Code: | #/etc/vmware # emerge -pv vmware-workstation
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild UD] app-emulation/vmware-modules-1.0.0.11 [1.0.0.15] 0 kB
[ebuild R ] app-emulation/vmware-workstation-4.5.3.19414-r7 0 kB
|
Then I ran /opt/vmware/workstation/bin/vmware-config.pl
| Code: | /opt/vmware/workstation/bin/vmware-config.pl
Making sure services for VMware Workstation are stopped.
* 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) [no]
Do you want networking for your virtual machines? (yes/no/help) [yes]
Would you prefer to modify your existing networking configuration using the
wizard or the editor? (wizard/editor/help) [editor] wizard
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]
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: [ ok ]
* Virtual machine monitor [ ok ]
* Virtual ethernet [ ok ]
* Bridged networking on /dev/vmnet0 [ !! ]
The configuration of VMware Workstation 4.5.3 build-19414 for Linux for this
running kernel completed successfully. |
What gives with this? * Bridged networking on /dev/vmnet0 [ !! ]
So even after the "sucessful" run of the vmware-config.pl script I still have the file /etc/vmware/not_configured.
And I delete /etc/vmware/not_configured and try to start vmware-workstation I get an error "Version mismatch with vmmon module: expecting 81.0, got 137.0. You have an incorrect version of the 'vmmon' kernel module. Try reinstalling VMware Workstation."
If I get this working (and I need it for work and I'm on call) I am going to mask vmware workstation so it NEVER updates again. I am really sick of vmware-workstation updates breaking. What a freaking pain.
Can anyone help before I physically break something nearby? |
|
| Back to top |
|
 |
Truin
n00b
Joined: 05 Jul 2006
Posts: 54
|
| Posted: Tue Oct 10, 2006 7:41 am Post subject: VMWare headaches |
|
|
First, make sure that /usr/src/linux points to the correct kernel; i.e., the one you're actually running. Any time emerge builds modules, it looks at /usr/src/linux for the kernel sources. If your symlink isn't pointed to the right version, you'll have problems with the modules loading. Check 'dmesg' for obvious signs.
Second, when you run the vmware-config.pl script (or whatever it's called) it will insert the required modules for you - a job normaly handled by the vmware init script. If you try and run the `/etc/init.d/vmware start` (or equivelant) *after a successful completion of vmware-config*, you'll probably see some odd error messages but SHOULD be ok. A subsequent reboot should look normal.
Also, it seems that emerge wanted to DOWNGRADE your version of the vmware-modules package. What's up with that?
I've not played with vmware a whole lot, but enough to have run into similar issues. Hope this helps! |
|
| Back to top |
|
|
TrainedChimp
Tux's lil' helper
Joined: 25 Jun 2004
Posts: 87
Location: Just west of Earth
|
| Posted: Tue Oct 10, 2006 4:44 pm Post subject: Re: VMWare headaches |
|
|
| Truin wrote: | First, make sure that /usr/src/linux points to the correct kernel; i.e., the one you're actually running. Any time emerge builds modules, it looks at /usr/src/linux for the kernel sources. If your symlink isn't pointed to the right version, you'll have problems with the modules loading. Check 'dmesg' for obvious signs.
Second, when you run the vmware-config.pl script (or whatever it's called) it will insert the required modules for you - a job normaly handled by the vmware init script. If you try and run the `/etc/init.d/vmware start` (or equivelant) *after a successful completion of vmware-config*, you'll probably see some odd error messages but SHOULD be ok. A subsequent reboot should look normal.
Also, it seems that emerge wanted to DOWNGRADE your version of the vmware-modules package. What's up with that?
I've not played with vmware a whole lot, but enough to have run into similar issues. Hope this helps! |
Thanks for the reply I've checked/tried those things.
The upgrade/down grade ping-pong is part of my vmware portage frustration. If you do what the confil.pl tells you 'emerge --oneshot vmware-modules' then portage will want you to down grade. Nice, huh?
This is from my syslog:
| Code: | # tail -300 /var/log/messages |grep vm
Oct 10 10:21:01 kayak vmmon: no version magic, tainting kernel.
Oct 10 10:21:01 kayak /dev/vmmon[7567]: Module vmmon: registered with major=10 minor=165
Oct 10 10:21:01 kayak /dev/vmmon[7567]: Module vmmon: initialized
Oct 10 10:21:01 kayak vmnet: no version magic, tainting kernel.
Oct 10 10:21:01 kayak /dev/vmnet: open called by PID 7605 (vmnet-bridge)
Oct 10 10:21:01 kayak /dev/vmnet: hub 0 does not exist, allocating memory.
Oct 10 10:21:01 kayak /dev/vmnet: port on hub 0 successfully opened
Oct 10 10:21:01 kayak vmware-start: Bridged networking on /dev/vmnet0 failed |
I am frustrated and tired of this stuff related to vmware-workstation. Maybe it all works for vmware workstation ver 5 but I don't have a license for that do I still need to use 4.5. |
|
| Back to top |
|
|
TrainedChimp
Tux's lil' helper
Joined: 25 Jun 2004
Posts: 87
Location: Just west of Earth
|
| Posted: Thu Oct 12, 2006 1:38 am Post subject: |
|
|
| Bump - Any ideas? |
|
| Back to top |
|
|
uziel
n00b
Joined: 14 Feb 2003
Posts: 32
|
| Posted: Mon Oct 16, 2006 2:30 am Post subject: |
|
|
| TrainedChimp wrote: | | Bump - Any ideas? |
Well, I fought the same BS for the better part of tonight. Fixed it by unpacking vmware-any-any-update-104.tar.gz, the vmmon.tar and vmnet.tar therein and doing make inside each dir. The resulting .ko modules I copied to /lib/modules/`uname -r`/misc/ and vmware-config.pl no longer complained. It's actually the binaries like vmnet-bridge that complain about the version mismatch.
Maybe it's worth mentioning, after getting tired I kicked the modules out manually with rmmod before every next try.
Good luck!
uziel
_________________
Those who promise their way of freedom and peace still do not understand the meaning of the word... |
|
| Back to top |
|
|
appetitus
Apprentice
Joined: 28 Sep 2003
Posts: 210
|
| Posted: Tue Oct 17, 2006 7:30 am Post subject: |
|
|
| uziel wrote: | | TrainedChimp wrote: | | Bump - Any ideas? |
Well, I fought the same BS |
Well, I had such hopes. The gentoo dev QA is now worse than Mickeysoft.
despite trying the direct builds of the kernel modules, I still cannot get past the stupid vmware-config.pl program, last time I went thru this I had to track down the crap code and fix it.
| Code: |
vmware-start: Bridged networking on /dev/vmnetfailed
|
uziel How about some kernel and workstation version numbers please?
Dumping the bridged networking and then getting to run 'vmware' always hits this roadblock:
| Code: |
Verson mismatch with vmmon module: expecting 81.0 got 137.0
|
along with some useless advice
_________________
Being a Gentoo user means living in a house inhabited by a family of crazed carpenters. When you wake up, the house is different. Maybe there is a new turret, or some walls have moved, or perhaps someone has removed the floor under your bed. |
|
| Back to top |
|
|
uziel
n00b
Joined: 14 Feb 2003
Posts: 32
|
| Posted: Tue Oct 17, 2006 10:12 am Post subject: |
|
|
| appetitus wrote: | | Well, I had such hopes. The gentoo dev QA is now worse than Mickeysoft. |
Huh. Getting personal won't solve this one ; )
| appetitus wrote: | despite trying the direct builds of the kernel modules, I still cannot get past the stupid vmware-config.pl program, last time I went thru this I had to track down the crap code and fix it.
| Code: |
vmware-start: Bridged networking on /dev/vmnetfailed
|
Dumping the bridged networking and then getting to run 'vmware' always hits this roadblock:
| Code: |
Verson mismatch with vmmon module: expecting 81.0 got 137.0
|
along with some useless advice |
Yeah. So you have not solved your problem afaics, as I had the exact same messages from the init script and vmware before things worked out.
| appetitus wrote: | | How about some kernel and workstation version numbers please? |
| Code: | vanilla 2.6.16.29 (stable managed by Adrian Bunk)
vmware-workstation-4.5.3.19414-r7 |
That is the only thing pinning down your required module version, as you see too that is 81.0. So once you unpack vmware-any-any-update104.tar.gz and replace the modules already there in your current kernel's module dir with the ones you made yourself, you should be set. The Makefile uses /lib/modules/`uname -r`/build to get to your kernel source. Just do
| Code: | rmmod vmnet vmmon
rm /etc/vmware/not_configured |
and you're good to go. Works For Me [TM].
Regards,
uziel |
|
| Back to top |
|
|
appetitus
Apprentice
Joined: 28 Sep 2003
Posts: 210
|
| Posted: Tue Oct 17, 2006 2:39 pm Post subject: |
|
|
| uziel wrote: | | appetitus wrote: | | Well, I had such hopes. |
So once you unpack vmware-any-any-update104.tar.gz and replace the modules already there in your current kernel's module dir with the ones you made yourself, you should be set |
Reading that earlier is what gave me high hopes, but it didn't work either. Doing reinstalls is like Mickeysoft SOP, this is linux, or it was a few years ago. Module loading is trivial, but devs screwing up module required version numbers is not. Thanks for the version numbers, I'll give them a shot before I pull vmware out of gentoos hands and simply hand maintain it.
_________________
Being a Gentoo user means living in a house inhabited by a family of crazed carpenters. When you wake up, the house is different. Maybe there is a new turret, or some walls have moved, or perhaps someone has removed the floor under your bed. |
|
| Back to top |
|
|
uziel
n00b
Joined: 14 Feb 2003
Posts: 32
|
| Posted: Tue Oct 17, 2006 5:40 pm Post subject: |
|
|
| appetitus wrote: | | Reading that earlier is what gave me high hopes, but it didn't work either. Doing reinstalls is like Mickeysoft SOP, this is linux, or it was a few years ago. Module loading is trivial, but devs screwing up module required version numbers is not. Thanks for the version numbers, I'll give them a shot before I pull vmware out of gentoos hands and simply hand maintain it. |
Well, I still don't get it. The version numbers like 81.0 and 137.0 appear to be hard-coded into the module source. How am I supposed to build a v81.0 module from the same source that gives you v137.0? Preprocessor and shit comes to mind, but that's not what I mean. They change functionality, they increment the version, and vmware knows which versions it will work with, or rather not. So if you still get a 137 module, something is absolutely wrong. Maybe you should google for vmware-any-any-update and download the original file again from Petr's ftp mirror. Seek and destroy any vm* module anywhere. Same for the source code. Unpack, build, copy, rmmod, delete not_configured by hand, try again.
I don't bloody get this.
Regards,
uziel |
|
| Back to top |
|
|
TrainedChimp
Tux's lil' helper
Joined: 25 Jun 2004
Posts: 87
Location: Just west of Earth
|
| Posted: Wed Oct 18, 2006 2:02 am Post subject: |
|
|
Thanks for the replies. Well now it works. I just did an emerge vmware-modules-1.0.0.11-r1 and now everything works. This sucks I am masking vmware-workstation and vmware-modules and not updating them again. I am really tired of this. I don't know why this particular problem bothers me so much, perhaps because it happens every time, but I almost swithed to Fedora...
Edit: I just realized that I had put app-emulation/vmware-workstation ~x86 and app-emulation/vmware-modules ~x86 in /etc/portage/package.keywords - I have no idea whn I did that or why, must have been a while ago. Anyway they're both masked now because I don't want to risk updating again and wasting time trying to figure out what broke. |
|
| Back to top |
|
|
BigBaaadBob
Guru
Joined: 19 Apr 2003
Posts: 342
Location: Swampscott, MA USA
|
| Posted: Mon Oct 30, 2006 6:38 pm Post subject: |
|
|
Same problem here:
| Code: | localhost ~ # uname -srm
Linux 2.6.17-gentoo-r7 i686
localhost ~ # equery list vmware
[ Searching for package 'vmware' in all categories among: ]
* installed packages
[I--] [ -] app-emulation/vmware-modules-1.0.0.13 (0)
[I--] [ -] app-emulation/vmware-workstation-5.5.1.19175-r7 (0)
localhost ~ # lsmod | grep vm
localhost ~ # /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. [ !! ]
localhost ~ # /opt/vmware/workstation/bin/vmware-config.pl
Making sure services for VMware Workstation are stopped.
* WARNING: vmware has not yet been started.
Configuring fallback GTK+ 2.4 libraries.
You have already setup networking.
Would you like to skip networking setup and keep your old settings as they are?
(yes/no) [yes]
* Starting VMware services: [ ok ]
* Virtual machine monitor [ !! ]
* Virtual ethernet [ !! ]
* Bridged networking on /dev/vmnet0 [ !! ]
The configuration of VMware Workstation 5.5.1 build-19175 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
localhost ~ # /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. [ !! ]
localhost ~ #
|
I've tried unmerging/remerging, etc, etc, etc. This was working just before an emerge --update world, and I don't believe any new vmware got emerged.
How do I get more debugging information about the "!!" stuff? |
|
| Back to top |
|
|
BigBaaadBob
Guru
Joined: 19 Apr 2003
Posts: 342
Location: Swampscott, MA USA
|
| Posted: Mon Oct 30, 2006 9:23 pm Post subject: |
|
|
Switched to latest versions, same problem. I think the ebuilds are broken!
| Code: | localhost ~ # equery list vmware
[ Searching for package 'vmware' in all categories among: ]
* installed packages
[I--] [ ~] app-emulation/vmware-modules-1.0.0.15-r1 (0)
[I--] [ ~] app-emulation/vmware-workstation-5.5.2.29772 (0)
|
|
|
| Back to top |
|
|
BigBaaadBob
Guru
Joined: 19 Apr 2003
Posts: 342
Location: Swampscott, MA USA
|
| Posted: Mon Oct 30, 2006 9:47 pm Post subject: |
|
|
Nevermind! I had a kernel mixup! Ebuilds working fine (at least the new ones). My oops!!!!!!  |
|
| Back to top |
|
|
Ast0r
Guru
Joined: 11 Apr 2006
Posts: 404
Location: Dallas, Tx - USA
|
| Posted: Mon Oct 30, 2006 10:34 pm Post subject: |
|
|
| TrainedChimp wrote: | | Edit: I just realized that I had put app-emulation/vmware-workstation ~x86 and app-emulation/vmware-modules ~x86 in /etc/portage/package.keywords - I have no idea whn I did that or why, must have been a while ago. Anyway they're both masked now because I don't want to risk updating again and wasting time trying to figure out what broke. |
So you were running the unstable versions and bitching when it broke? Maybe you should try running the stable versions. You will be far less likely to have trouble. Running the stable version I only have to emerge --oneshot vmware-modules once every 3 or 4 time the package is updated (which is once every 6-8 months) and I never have nearly the issues you were having. Be a little more patient when you're running bleeding-edge software. |
|
| Back to top |
|
|
TrainedChimp
Tux's lil' helper
Joined: 25 Jun 2004
Posts: 87
Location: Just west of Earth
|
| Posted: Tue Oct 31, 2006 1:18 am Post subject: |
|
|
| Ast0r wrote: | | TrainedChimp wrote: | | Edit: I just realized ... |
So you were running the unstable versions and bitching when it broke? Maybe you should try running the stable versions. You will be far less likely to have trouble. Running the stable version I only have to emerge --oneshot vmware-modules once every 3 or 4 time the package is updated (which is once every 6-8 months) and I never have nearly the issues you were having. Be a little more patient when you're running bleeding-edge software. |
What part of "I just realized" don't you understand? I specificaly edited my post post to explain what happened and mention that it was my bad for running ~x86 and mention that I switched to the stable versions. I'll be a little more patient when you learn to comprehend what you read. |
|
| Back to top |
|
|
Ast0r
Guru
Joined: 11 Apr 2006
Posts: 404
Location: Dallas, Tx - USA
|
| Posted: Tue Oct 31, 2006 5:53 am Post subject: |
|
|
| TrainedChimp wrote: | | Ast0r wrote: | | TrainedChimp wrote: | | Edit: I just realized ... |
So you were running the unstable versions and bitching when it broke? Maybe you should try running the stable versions. You will be far less likely to have trouble. Running the stable version I only have to emerge --oneshot vmware-modules once every 3 or 4 time the package is updated (which is once every 6-8 months) and I never have nearly the issues you were having. Be a little more patient when you're running bleeding-edge software. |
What part of "I just realized" don't you understand? I specificaly edited my post post to explain what happened and mention that it was my bad for running ~x86 and mention that I switched to the stable versions. I'll be a little more patient when you learn to comprehend what you read. |
 |
|
| Back to top |
|
|
parsim
Guru
Joined: 12 Aug 2004
Posts: 347
Location: Melbourne, Australia
|
| Posted: Wed Dec 13, 2006 3:53 am Post subject: |
|
|
Gotta say, I have endless trouble with VMWare breaking, too. Seems like every time I update either VMWare or the kernel, everything breaks and requires lots of frigging around with re-emerging, vmware-config.pl, rebooting, etc.
Funny that it's the only piece of software on this machine I paid money for, and also the most frustrating. |
|
| Back to top |
|
|
weird wonko
Tux's lil' helper
Joined: 05 Jan 2003
Posts: 141
|
| Posted: Sat Jan 06, 2007 7:53 pm Post subject: |
|
|
| uziel wrote: | Well, I fought the same BS for the better part of tonight. Fixed it by unpacking vmware-any-any-update-104.tar.gz, the vmmon.tar and vmnet.tar therein and doing make inside each dir. The resulting .ko modules I copied to /lib/modules/`uname -r`/misc/ and vmware-config.pl no longer complained. It's actually the binaries like vmnet-bridge that complain about the version mismatch.
|
Thanks for that info, this is what just helped me. After not being able to run VMware for over one month, I did another attempt to fix the problem, without success. I even unmerged vmware and modules, removed /etc/vmware, and installed from scratch - but always I had trouble with vmmon and vmnet. vmware-config.pl was not able to activate vmmon and vmnet, but did not give an error. I also had the devices, and both modules running. This is what I have in my syslog:
| Code: | Jan 6 19:33:28 [kernel] vmmon: no version magic, tainting kernel.
Jan 6 19:33:28 [kernel] vmnet: no version magic, tainting kernel.
Jan 6 19:33:28 [vmware-start] Bridged networking on /dev/vmnet0_[71Gfailed
Jan 6 19:33:28 [vmware-start] NAT service on /dev/vmnet8_[71Gfailed
Jan 6 19:33:38 [VMware] Module version mismatch. Please update host.
Jan 6 19:33:38 [VMware] : Success |
Building vmmon and vmnet manually as you suggested did the trick.
I think I will NEVER agan change my vmware setup, unless I have to, because I am always having trouble afterwards. This just costs a lot of time. |
|
| Back to top |
|
|
|
Portage & Programming
