VMware Communities
dcatkin
Contributor
Contributor

Version mismatch with vmmon module: expecting 167.0, got 161.0. Version mismatch with vmmon module

I had it up and running fine, until my machine has a kernel fart and needed to be reinstalled, could I get some help with this one, I have reinstalled vmware 3 times, and tried the any-any patch, aone of which has worked.

David C. Atkin

Version mismatch with vmmon module: expecting 167.0, got 161.0.

You have an incorrect version of the `vmmon' kernel module.

Try reinstalling VMware Workstation.

Reply
0 Kudos
34 Replies
larstr
Champion
Champion

you tried any-any-update 114 too?

Reply
0 Kudos
dcatkin
Contributor
Contributor

I thought I was using 114, but if not, where can I get it.

Reply
0 Kudos
dcatkin
Contributor
Contributor

I checked on it, it is any-any-update114, and that is why I am stumped.

Reply
0 Kudos
uebelacker
Contributor
Contributor

I got the same error message using openSUSE 10.3, VMware-workstation-6.0.2-59824.i386.rpm, and any-any-update114.

While compiling I got this info:

"Unknown VMware Workstation 6.0.2 build 59824 detected. Building for Workstation 6.0.0."

Maybe you see the same?

Reply
0 Kudos
dcatkin
Contributor
Contributor

I have not gotten this up and running again, somebody please help.

Thank You

David C. Atkin

Reply
0 Kudos
uebelacker
Contributor
Contributor

Then provide us some information like I did. Distribution, Kernel Version, VMware version and build...

I think the any-any-script needs to be updated by the author.

Reply
0 Kudos
larstr
Champion
Champion

What kernel version are you using? Would it be possible for you to downgrade to an older kernel?

Lars

Reply
0 Kudos
dcatkin
Contributor
Contributor

I am rumming linux Fedora Core 7 the latest kernel version of 2.6.23.1-4.fc7, and version 6.0.2 build-59824 of vmware workstation 6.

Here is some more info.

Warning 1) Version mismatch with vmmon module: expecting 167.0, got 161.0.

You have an incorrect version of the `vmmon' kernel module.

Try reinstalling VMware Workstation.

Warning 2) Failed to initialize monitor device.

Warning 3) Unable to change virtual machine power state: Cannot find a valid peer process to connect to.

Thank You

David C. Atkin

Reply
0 Kudos
dagbj
Contributor
Contributor

Hi,

I'm experiencing the same problem. I'm also running FC7. I tried to upgrade Virtual Machines from v5 of the workstation. I

also used the VM upgrade option.

I downgraded (booted into an earlier kernel) to 2.6.21-1.3194.fc7, and ran any-any 1.1.4 again. That did not help.

So any suggestions would be nice.

Regards

Dag Bjerkeli

Reply
0 Kudos
soccja
Contributor
Contributor

Hi,

I had the same problem, but on arch-linux. Similar scenario: problem arose on updating the kernel.

I ran /usr/bin/vmware-config.pl and answered 'yes' to Would you like to skip networking setup and keep your old settings as they are? Started vmware and got the error.

I then reran vmware-config.pl and answered 'no' to this question. Re-started vmware and all was well.

Don't know if that helps anyone but thought it worth mentioning.

--Charlie

Reply
0 Kudos
egiceme
Contributor
Contributor

Hello,

Here is my setup:

  • Ubuntu 7.10, Kernel 2.6.22-14-generic

  • vmware-workstation-6.0.2-59825-Linux

  • vmware-any-any-update114

Same issue, tried all posted things - didn't help

Also: While compiling I got this info:

"Unknown VMware Workstation 6.0.2 build 59824 detected. Building for Workstation 6.0.0."

Help would be appreciated.

Reply
0 Kudos
LoSeR_5150
Contributor
Contributor

vmware-workstation-6.0.2-59825

vmware-any-any-update114

Same issue with 2.6.23-gentoo kernel... the only fix is to downgrade back to 6.01 vmware-workstation.... any other workarounds / fixes welcome

Reply
0 Kudos
nielsb_11
Contributor
Contributor

Same issue here, running Ubuntu 7.10 and workstation 6.02-59825. and the 114 patch. As someone else in this thread reported, when building the modules there is a message that the version is unknown and it compiles for 6.0.0.

Is there anything that can be done, or ...?

Niels

Reply
0 Kudos
egiceme
Contributor
Contributor

Work arrounds:

  1. Downgrade to vmware-workstation-6.0.0.45731-Linux on Ubuntu 7.10. Works only if you start as root (sudo vmware). Probably permission issue.

  2. Downgrade to Ubuntu 7.04.

  3. Use VMware-server-1.0.4-56528 on Ubuntu 7.10. Works without any problems. No need to apply any-any-1.

But really, we need a new "any-any 1.5 ?" .

Reply
0 Kudos
nielsb_11
Contributor
Contributor

Thanks! Yeah, I downgraded to 6.0.0 and it works fine now.

Niels

Reply
0 Kudos
bennetts2
Contributor
Contributor

Heh. I just got this too. I'm running Fedora 7, and I'd just upgraded from kernel-2.6.22.4-65.fc7.x86_64, and VMwareWorkstation-6.0.0-45731.i386, to kernel-2.6.23.1-10.fc7.x86_64, VMwareWorkstation-6.0.2-59824.x86_64 and vmware-any-any-update114. And I got the "Version mismatch with vmmon module: expecting 167.0, got 161.0." error.

My guess is that my mistake was to apply update114 - it's not necessary - it contains versions of vmmon and vmnet for 6.0.0, and overwrites the newer versions that are in 6.0.2.

I uninstalled vmware, and put it back again, without update114, and it seems to work now (i.e.I am successfully running kernel-2.6.23.1-10.fc7.x86_64 and VMwareWorkstation-6.0.2-59824.x86_64). Even the machine that I suspended before the upgrade seems to be happy.

It would be interesting to hear if this works for others too.

Steve.

Reply
0 Kudos
dcatkin
Contributor
Contributor

I am not running the X64 fc7, but I am running the latest kernel on fc7, have removed and re-installed the program with and without the any-any patch, it doesn't work either way, I'm considdering buying the program, but I need to get this resolved first, and get a working version, because I update the kernel everytime I possibly can.

David C. Atkin

Reply
0 Kudos
bennetts2
Contributor
Contributor

because I update the kernel everytime I possibly can.

Hi David,

In my experience, it's not a good idea to upgrade the kernel whenever you can. Kernel updates can introduce problems (like it seems is happening for you here), so if if your current kernel is OK for you, stick with it for a while. Or to put it another way - if you do a kernel update and find a problem, going back to your older kernel is a good thing to do.

Steve.

Reply
0 Kudos
dcatkin
Contributor
Contributor

Ok boys and girls, after farting around with it for a couple of hours, I got it fixed, on FC7 let me explain how I did it, this time around I noticed that vmware creates a folder called vmware in your home folder, and I deleted the contents from that folder out, and then opened up synaptic package manager and did a search for vmware and when it located vmware I told the package manager to completly remove the vmware program, then rebooted the machine and logged back in to the user that I installed vmware on and ran the rpm installer, and lowe and behold it's working great, without even one flaw, except of course windows LOL.

David C. Atkin

Reply
0 Kudos