shijukumar
Contributor
Contributor

VMware 8.0 is not suppoting for ubuntu 12.04

Hi Team,

My WMware workstation is not working after upgrading my ubuntu OS from 11.10 to 12.04 . Is any new patch is available for ubuntu 12.04

0 Kudos
19 Replies
RDPetruska
Leadership
Leadership

Try the Workstation Tech Preview version.

0 Kudos
Rahulverma20111
Enthusiast
Enthusiast

It is currently unsupported in VMware Workstation 8.0.2. I am not sure if it is supported in the tech preview as well. You can get the Tech Preview below:

http://communities.vmware.com/community/vmtn/beta/workstationtp2012

Note: Please do not consider my comments/suggestions as an official response from VMware.
0 Kudos
rizlaw
Contributor
Contributor

I'm having the same issue as the OP after upgrade from Ubuntu 11.10 to 12.04 64bit.

Any idea when VMW 8.03 will be out to fix this? I can't get 8.02 to compile the virtual network driver. The log file:

2012-03-29T12:33:53.492-05:00| vthread-3| I120: Log for VMware Workstation pid=14947 version=8.0.2 build=build-591240 option=Release
2012-03-29T12:33:53.492-05:00| vthread-3| I120: The process is 64-bit.
2012-03-29T12:33:53.492-05:00| vthread-3| I120: Host codepage=UTF-8 encoding=UTF-8
2012-03-29T12:33:53.492-05:00| vthread-3| I120: Host is Linux 3.2.0-20-generic Ubuntu precise (development branch)
2012-03-29T12:33:53.492-05:00| vthread-3| I120: Msg_Reset:
2012-03-29T12:33:53.492-05:00| vthread-3| I120: [msg.dictionary.load.openFailed] Cannot open file "/usr/lib/vmware/settings": No such file or directory.
2012-03-29T12:33:53.492-05:00| vthread-3| I120: ----------------------------------------
2012-03-29T12:33:53.492-05:00| vthread-3| I120: PREF Optional preferences file not found at /usr/lib/vmware/settings. Using default values.
2012-03-29T12:33:53.492-05:00| vthread-3| I120: Msg_Reset:
2012-03-29T12:33:53.492-05:00| vthread-3| I120: [msg.dictionary.load.openFailed] Cannot open file "/root/.vmware/config": No such file or directory.
2012-03-29T12:33:53.492-05:00| vthread-3| I120: ----------------------------------------
2012-03-29T12:33:53.492-05:00| vthread-3| I120: PREF Optional preferences file not found at /root/.vmware/config. Using default values.
2012-03-29T12:33:53.492-05:00| vthread-3| I120: Msg_Reset:
2012-03-29T12:33:53.492-05:00| vthread-3| I120: [msg.dictionary.load.openFailed] Cannot open file "/root/.vmware/preferences": No such file or directory.
2012-03-29T12:33:53.492-05:00| vthread-3| I120: ----------------------------------------
2012-03-29T12:33:53.492-05:00| vthread-3| I120: PREF Failed to load user preferences.
2012-03-29T12:33:53.492-05:00| vthread-3| W110: Logging to /tmp/vmware-root/modconfig-14947.log
2012-03-29T12:33:53.621-05:00| vthread-3| I120: modconf query interface initialized
2012-03-29T12:33:53.622-05:00| vthread-3| I120: modconf library initialized
2012-03-29T12:33:53.651-05:00| vthread-3| I120: Your GCC version: 4.6
2012-03-29T12:33:53.654-05:00| vthread-3| I120: Validating path /lib/modules/preferred/build/include for kernel release 3.2.0-20-generic
2012-03-29T12:33:53.654-05:00| vthread-3| I120: Failed to find /lib/modules/preferred/build/include/linux/version.h
2012-03-29T12:33:53.654-05:00| vthread-3| I120: Failed version test: /lib/modules/preferred/build/include/linux/version.h not found.
2012-03-29T12:33:53.654-05:00| vthread-3| I120: Validating path /lib/modules/3.2.0-20-generic/build/include for kernel release 3.2.0-20-generic
2012-03-29T12:33:53.655-05:00| vthread-3| I120: Your GCC version: 4.6
2012-03-29T12:33:53.662-05:00| vthread-3| I120: Your GCC version: 4.6
2012-03-29T12:33:53.685-05:00| vthread-3| I120: Header path /lib/modules/3.2.0-20-generic/build/include for kernel release 3.2.0-20-generic is valid.
2012-03-29T12:33:53.685-05:00| vthread-3| I120: Validating path /lib/modules/3.2.0-20-generic/build/include for kernel release 3.2.0-20-generic
2012-03-29T12:33:53.686-05:00| vthread-3| I120: Your GCC version: 4.6
2012-03-29T12:33:53.693-05:00| vthread-3| I120: Your GCC version: 4.6
2012-03-29T12:33:53.715-05:00| vthread-3| I120: Header path /lib/modules/3.2.0-20-generic/build/include for kernel release 3.2.0-20-generic is valid.
2012-03-29T12:33:53.732-05:00| vthread-3| I120: Trying to find a suitable PBM set for kernel 3.2.0-20-generic.
2012-03-29T12:33:53.734-05:00| vthread-3| I120: Trying to find a suitable PBM set for kernel 3.2.0-20-generic.
2012-03-29T12:33:53.737-05:00| vthread-3| I120: Trying to find a suitable PBM set for kernel 3.2.0-20-generic.
2012-03-29T12:33:53.739-05:00| vthread-3| I120: Trying to find a suitable PBM set for kernel 3.2.0-20-generic.
2012-03-29T12:33:53.742-05:00| vthread-3| I120: Trying to find a suitable PBM set for kernel 3.2.0-20-generic.
2012-03-29T12:33:53.757-05:00| vthread-3| I120: Trying to find a suitable PBM set for kernel 3.2.0-20-generic.
2012-03-29T12:33:53.759-05:00| vthread-3| I120: Trying to find a suitable PBM set for kernel 3.2.0-20-generic.
2012-03-29T12:33:53.761-05:00| vthread-3| I120: Trying to find a suitable PBM set for kernel 3.2.0-20-generic.
2012-03-29T12:33:53.764-05:00| vthread-3| I120: Trying to find a suitable PBM set for kernel 3.2.0-20-generic.
2012-03-29T12:33:53.766-05:00| vthread-3| I120: Trying to find a suitable PBM set for kernel 3.2.0-20-generic.
2012-03-29T12:33:53.768-05:00| vthread-3| I120: Validating path /lib/modules/preferred/build/include for kernel release 3.2.0-20-generic
2012-03-29T12:33:53.768-05:00| vthread-3| I120: Failed to find /lib/modules/preferred/build/include/linux/version.h
2012-03-29T12:33:53.768-05:00| vthread-3| I120: Failed version test: /lib/modules/preferred/build/include/linux/version.h not found.
2012-03-29T12:33:53.768-05:00| vthread-3| I120: Validating path /lib/modules/3.2.0-20-generic/build/include for kernel release 3.2.0-20-generic
2012-03-29T12:33:53.770-05:00| vthread-3| I120: Your GCC version: 4.6
2012-03-29T12:33:53.777-05:00| vthread-3| I120: Your GCC version: 4.6
2012-03-29T12:33:53.799-05:00| vthread-3| I120: Header path /lib/modules/3.2.0-20-generic/build/include for kernel release 3.2.0-20-generic is valid.
2012-03-29T12:33:53.817-05:00| vthread-3| I120: Trying to find a suitable PBM set for kernel 3.2.0-20-generic.
2012-03-29T12:33:53.820-05:00| vthread-3| I120: Trying to find a suitable PBM set for kernel 3.2.0-20-generic.
2012-03-29T12:33:53.822-05:00| vthread-3| I120: Trying to find a suitable PBM set for kernel 3.2.0-20-generic.
2012-03-29T12:33:53.825-05:00| vthread-3| I120: Trying to find a suitable PBM set for kernel 3.2.0-20-generic.
2012-03-29T12:33:53.827-05:00| vthread-3| I120: Trying to find a suitable PBM set for kernel 3.2.0-20-generic.
2012-03-29T12:33:53.829-05:00| vthread-3| I120: Validating path /lib/modules/preferred/build/include for kernel release 3.2.0-20-generic
2012-03-29T12:33:53.829-05:00| vthread-3| I120: Failed to find /lib/modules/preferred/build/include/linux/version.h
2012-03-29T12:33:53.829-05:00| vthread-3| I120: Failed version test: /lib/modules/preferred/build/include/linux/version.h not found.
2012-03-29T12:33:53.829-05:00| vthread-3| I120: Validating path /lib/modules/3.2.0-20-generic/build/include for kernel release 3.2.0-20-generic
2012-03-29T12:33:53.830-05:00| vthread-3| I120: Your GCC version: 4.6
2012-03-29T12:33:53.838-05:00| vthread-3| I120: Your GCC version: 4.6
2012-03-29T12:33:53.860-05:00| vthread-3| I120: Header path /lib/modules/3.2.0-20-generic/build/include for kernel release 3.2.0-20-generic is valid.
2012-03-29T12:33:53.884-05:00| vthread-3| I120: Trying to find a suitable PBM set for kernel 3.2.0-20-generic.
2012-03-29T12:33:53.886-05:00| vthread-3| I120: Trying to find a suitable PBM set for kernel 3.2.0-20-generic.
2012-03-29T12:33:53.889-05:00| vthread-3| I120: Trying to find a suitable PBM set for kernel 3.2.0-20-generic.
2012-03-29T12:33:53.891-05:00| vthread-3| I120: Trying to find a suitable PBM set for kernel 3.2.0-20-generic.
2012-03-29T12:33:53.893-05:00| vthread-3| I120: Trying to find a suitable PBM set for kernel 3.2.0-20-generic.
2012-03-29T12:33:53.980-05:00| vthread-3| I120: Trying to find a suitable PBM set for kernel 3.2.0-20-generic.
2012-03-29T12:33:53.980-05:00| vthread-3| I120: Validating path /lib/modules/3.2.0-20-generic/build/include for kernel release 3.2.0-20-generic
2012-03-29T12:33:53.982-05:00| vthread-3| I120: Your GCC version: 4.6
2012-03-29T12:33:53.988-05:00| vthread-3| I120: Your GCC version: 4.6
2012-03-29T12:33:54.004-05:00| vthread-3| I120: Header path /lib/modules/3.2.0-20-generic/build/include for kernel release 3.2.0-20-generic is valid.
2012-03-29T12:33:54.005-05:00| vthread-3| I120: Building module vmmon.
2012-03-29T12:33:54.005-05:00| vthread-3| I120: Extracting the sources of the vmmon module.
2012-03-29T12:33:54.011-05:00| vthread-3| I120: Building module with command: /usr/bin/make -j -C /tmp/vmware-root/modules/vmmon-only auto-build SUPPORT_SMP=1 HEADER_DIR=/lib/modules/3.2.0-20-generic/build/include CC=/usr/bin/gcc GREP=/usr/bin/make IS_GCC_3=no VMCCVER=4.6
2012-03-29T12:33:55.279-05:00| vthread-3| I120: Installing module vmmon from /tmp/vmware-root/modules/vmmon.o to /lib/modules/3.2.0-20-generic/misc.
2012-03-29T12:33:55.279-05:00| vthread-3| I120: Registering file: /usr/lib/vmware-installer/2.0/vmware-installer --register-file vmware-vmx regular /lib/modules/3.2.0-20-generic/misc/vmmon.ko
2012-03-29T12:33:56.049-05:00| vthread-3| I120: Trying to find a suitable PBM set for kernel 3.2.0-20-generic.
2012-03-29T12:33:56.049-05:00| vthread-3| I120: Validating path /lib/modules/3.2.0-20-generic/build/include for kernel release 3.2.0-20-generic
2012-03-29T12:33:56.051-05:00| vthread-3| I120: Your GCC version: 4.6
2012-03-29T12:33:56.058-05:00| vthread-3| I120: Your GCC version: 4.6
2012-03-29T12:33:56.082-05:00| vthread-3| I120: Header path /lib/modules/3.2.0-20-generic/build/include for kernel release 3.2.0-20-generic is valid.
2012-03-29T12:33:56.082-05:00| vthread-3| I120: Building module vmnet.
2012-03-29T12:33:56.082-05:00| vthread-3| I120: Extracting the sources of the vmnet module.
2012-03-29T12:33:56.088-05:00| vthread-3| I120: Building module with command: /usr/bin/make -j -C /tmp/vmware-root/modules/vmnet-only auto-build SUPPORT_SMP=1 HEADER_DIR=/lib/modules/3.2.0-20-generic/build/include CC=/usr/bin/gcc GREP=/usr/bin/make IS_GCC_3=no VMCCVER=4.6
2012-03-29T12:33:57.404-05:00| vthread-3| I120: Failed to compile module vmnet!
2012-03-29T12:33:57.408-05:00| vthread-3| I120: Trying to find a suitable PBM set for kernel 3.2.0-20-generic.
2012-03-29T12:33:57.408-05:00| vthread-3| I120: Validating path /lib/modules/3.2.0-20-generic/build/include for kernel release 3.2.0-20-generic
2012-03-29T12:33:57.410-05:00| vthread-3| I120: Your GCC version: 4.6
2012-03-29T12:33:57.417-05:00| vthread-3| I120: Your GCC version: 4.6
2012-03-29T12:33:57.440-05:00| vthread-3| I120: Header path /lib/modules/3.2.0-20-generic/build/include for kernel release 3.2.0-20-generic is valid.
2012-03-29T12:33:57.440-05:00| vthread-3| I120: Building module vmblock.
2012-03-29T12:33:57.440-05:00| vthread-3| I120: Extracting the sources of the vmblock module.
2012-03-29T12:33:57.450-05:00| vthread-3| I120: Building module with command: /usr/bin/make -j -C /tmp/vmware-root/modules/vmblock-only auto-build SUPPORT_SMP=1 HEADER_DIR=/lib/modules/3.2.0-20-generic/build/include CC=/usr/bin/gcc GREP=/usr/bin/make IS_GCC_3=no VMCCVER=4.6
2012-03-29T12:33:59.123-05:00| vthread-3| I120: Installing module vmblock from /tmp/vmware-root/modules/vmblock.o to /lib/modules/3.2.0-20-generic/misc.
2012-03-29T12:33:59.123-05:00| vthread-3| I120: Registering file: /usr/lib/vmware-installer/2.0/vmware-installer --register-file vmware-vmx regular /lib/modules/3.2.0-20-generic/misc/vmblock.ko
2012-03-29T12:33:59.910-05:00| vthread-3| I120: Trying to find a suitable PBM set for kernel 3.2.0-20-generic.
2012-03-29T12:33:59.910-05:00| vthread-3| I120: Validating path /lib/modules/3.2.0-20-generic/build/include for kernel release 3.2.0-20-generic
2012-03-29T12:33:59.912-05:00| vthread-3| I120: Your GCC version: 4.6
2012-03-29T12:33:59.919-05:00| vthread-3| I120: Your GCC version: 4.6
2012-03-29T12:33:59.942-05:00| vthread-3| I120: Header path /lib/modules/3.2.0-20-generic/build/include for kernel release 3.2.0-20-generic is valid.
2012-03-29T12:33:59.942-05:00| vthread-3| I120: Building module vmci.
2012-03-29T12:33:59.942-05:00| vthread-3| I120: Extracting the sources of the vmci module.
2012-03-29T12:33:59.955-05:00| vthread-3| I120: Building module with command: /usr/bin/make -j -C /tmp/vmware-root/modules/vmci-only auto-build SUPPORT_SMP=1 HEADER_DIR=/lib/modules/3.2.0-20-generic/build/include CC=/usr/bin/gcc GREP=/usr/bin/make IS_GCC_3=no VMCCVER=4.6
2012-03-29T12:34:01.227-05:00| vthread-3| I120: Installing module vmci from /tmp/vmware-root/modules/vmci.o to /lib/modules/3.2.0-20-generic/misc.
2012-03-29T12:34:01.227-05:00| vthread-3| I120: Registering file: /usr/lib/vmware-installer/2.0/vmware-installer --register-file vmware-vmx regular /lib/modules/3.2.0-20-generic/misc/vmci.ko
2012-03-29T12:34:01.990-05:00| vthread-3| I120: Trying to find a suitable PBM set for kernel 3.2.0-20-generic.
2012-03-29T12:34:01.990-05:00| vthread-3| I120: Validating path /lib/modules/3.2.0-20-generic/build/include for kernel release 3.2.0-20-generic
2012-03-29T12:34:01.992-05:00| vthread-3| I120: Your GCC version: 4.6
2012-03-29T12:34:02.000-05:00| vthread-3| I120: Your GCC version: 4.6
2012-03-29T12:34:02.023-05:00| vthread-3| I120: Header path /lib/modules/3.2.0-20-generic/build/include for kernel release 3.2.0-20-generic is valid.
2012-03-29T12:34:02.023-05:00| vthread-3| I120: Building module vmci.
2012-03-29T12:34:02.023-05:00| vthread-3| I120: Extracting the sources of the vmci module.
2012-03-29T12:34:02.030-05:00| vthread-3| I120: Building module with command: /usr/bin/make -j -C /tmp/vmware-root/modules/vmci-only auto-build SUPPORT_SMP=1 HEADER_DIR=/lib/modules/3.2.0-20-generic/build/include CC=/usr/bin/gcc GREP=/usr/bin/make IS_GCC_3=no VMCCVER=4.6
2012-03-29T12:34:02.470-05:00| vthread-3| I120: Building module vsock.
2012-03-29T12:34:02.470-05:00| vthread-3| I120: Extracting the sources of the vsock module.
2012-03-29T12:34:02.481-05:00| vthread-3| I120: Building module with command: /usr/bin/make -j -C /tmp/vmware-root/modules/vsock-only auto-build SUPPORT_SMP=1 HEADER_DIR=/lib/modules/3.2.0-20-generic/build/include CC=/usr/bin/gcc GREP=/usr/bin/make IS_GCC_3=no VMCCVER=4.6
2012-03-29T12:34:04.507-05:00| vthread-3| I120: Installing module vsock from /tmp/vmware-root/modules/vsock.o to /lib/modules/3.2.0-20-generic/misc.
2012-03-29T12:34:04.508-05:00| vthread-3| I120: Registering file: /usr/lib/vmware-installer/2.0/vmware-installer --register-file vmware-vmx regular /lib/modules/3.2.0-20-generic/misc/vsock.ko

0 Kudos
mfelker
Expert
Expert

A few thoughts.

1) Did you completely remove VMware WS before upgrading Uuntu  I do this myself before any kernel upgrade  - let alone a a major host version upgrade  The VM's themselves should remain functional after this operation  .Thendo a clean re-inston  atll

2) I guess VMware techs will tell you that such  and such an OS is not supported,  Depending on you or your companies support level you will probably be locked into this advice.  In my opiinion  only this is basically a CYA.

However

  a)  Some people have instatlled VMware  |unsupported" hosts.  Before the Beat was released people instaTll Vmware on Windows 8 Developers version. BMware is extremely conservative about this.

  b)  Even if a OS is "offically" supported VMware might not instatll in your particualr environemnt for one reason or another. 

There is an insatll log ceated iin /var/log.  I foget the exact file name but it should not be very difficult to locate it.  Look at that and/or posrt the log.

0 Kudos
rizlaw
Contributor
Contributor

Mfelker,

Thanks for the reply. In answer to your first question, I didn't uninstall WS 8.0.2 before performing the distro upgrade; totally slipped my mind.

Anyway, I took a chance and downloaded the technology preview mentioned in this thread. I uninstalled WS 8.0.2 and all config files and installed the technology preview. I now can get my Mint12 VM up and running and it seems to work OK. It might even be a little faster, but that also could be partly due to Ubuntu 12.04 LTS - not sure.

Anyway, it looks like the Technology Preview is the short term solution until they release the next update to VMW 8.0.

0 Kudos
mfelker
Expert
Expert

Glad things worked out for you!  You might consider checking out the Beta forum!

0 Kudos
shijukumar
Contributor
Contributor

Thanks,

Now it is working with Tech preview version

0 Kudos
mfelker
Expert
Expert

Tech preview is workinig very well indeed on Ubuntu   12.04.   My practice (and suggestion) is to uninstall WS (/usr/bin/vmware-installer -u vmware-workstation  <keep configuration files>.  Then after booting to the new kernel reinstalll WS.

Cheers

0 Kudos
mydearcosmo
Contributor
Contributor

Should you not have to check for updates for your VMWare after upgrading your Ubuntu to 12.04?

0 Kudos
lucasmv
Enthusiast
Enthusiast

Hi all,

The vmware workstation is working very well with ubuntu 12.04 kernel 3.2. But you have to apply patch in the attacment.

After you install the vmware workstation, insatll the patch with this command,, with root user

./patch-modules_3.2.0.sh

thanks

Lucas

0 Kudos
mfelker
Expert
Expert

You don'teven the need the patch for WS 8 using TEch Preview.  Works fine on Ubuntu 12.04 host kernel 3.2.x.

0 Kudos
topsch
Contributor
Contributor

Hi Lucas.

Thank you for the patch. After installing this patch workstation works well again.

Klaus

0 Kudos
lucasmv
Enthusiast
Enthusiast

you are welcome.

0 Kudos
Tanker_Bob
Contributor
Contributor

Thanks for the link to the tech preview. It works perfectly in 12.04!

0 Kudos
tadao
Contributor
Contributor

Lucas, thank you very much for the patch, I disagree heavily on the statement that the patch in not needed because of the Tech Preview.

I hate to depend on a Tech Preview with expiring  date, which ALWAYS HAPPENS when you're working hard with deadline on  your neck. This is indeed a ridiculous option for anyone who is using a tool for a living.

For the ones like us who work hard with computers as primary  jobs and tools, is really difficult to be looking for such distracting  and out of focus things like a expiring date with one of your job tools!

So, THANK YOU FOR YOUR PATCH, it is reaaally a welcome contribution.

Best regards,

Tadao

0 Kudos
sjwk
Contributor
Contributor

VMWare 8.0.3 is now out and has reverted the fix by replacing the source files with the originals, but still doesn't provide working modules for Ubuntu 12.04.  The patch as it stands doesn't work as it checks for the version, but with a simple fix it does appear to build the modules correctly and Workstation runs afterwards.

Simply edit the patch-modules_3.2.0.sh file after extracting the archive and edit the lines starting 'vmreqver' and 'plreqver' to be for versions 8.0.3 and 4.0.3 respectively.

If you previously had installed this on workstation 8.0.2 then you also need to remove the file /usr/lib/vmware/modules/source/.patched otherwise it thinks it has already patched them and won't do it again!

Thanks for the original fix.

Steve.

0 Kudos
henryadriel001
Contributor
Contributor

im having the same problem even after installing the patch what can i do ? and how to fix it please help

0 Kudos
continuum
Immortal
Immortal

the screenshot looks like you are running MacOS ???
you may want to post in the fuision forum

Do you need support with a recovery problem ? - send a message via skype "sanbarrow"
0 Kudos
kevincrocker
Contributor
Contributor

I'm using the Tech Preview on Ubuntu 12.04 - and I had a VMWare support person talk me through the reinstallation this morning. Everything looked like it was OK - and at the time the VM Workstation came up and I could start my VM.

Since then (and all I did was powerdown, go to work, and power up again), I'm getting a 'vmmon' error.

Could not open /dev/vmmon: No such file or directory.
Please make sure that the kernel module `vmmon' is loaded.

Of course, all I can do is click OK to get the next message.

Failed to initialize monitor device.

And then click OK again to get the next message

Unable to change virtual machine power state: Cannot find a valid peer process to connect to

I think I understand what the problem is, but I have no idea how to fix it. I'm also reluctant to experiement as I have a critical deadline of Tuesday morning at 8 am to have this up and running perfectly.

any pointers or help would be appreciated. I did submit a VMware support request but I've had not response from VMWare despite the fact that they've helped me instantly before.

0 Kudos