Home » Blogs » sugree's blog

How to install VMware on Ubuntu Gutsy Gibbon

Posted August 11th, 2007 by sugree

This is my first task. I would like to run VMware under Ubuntu Gutsy Gibbon. Unfortunately, it seems like VMware doesn't support the latest kernel, 2.6.22-9, yet. As a result, I got below error messages.

Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config0/vmnet-only'
make -C /lib/modules/2.6.22-9-386/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.22-9-386'
  CC [M]  /tmp/vmware-config0/vmnet-only/driver.o
  CC [M]  /tmp/vmware-config0/vmnet-only/hub.o
  CC [M]  /tmp/vmware-config0/vmnet-only/userif.o
/tmp/vmware-config0/vmnet-only/userif.c: In function ‘VNetCopyDatagramToUser’:
/tmp/vmware-config0/vmnet-only/userif.c:630: error: ‘const struct sk_buff’ has no member named ‘h’
/tmp/vmware-config0/vmnet-only/userif.c:630: error: ‘const struct sk_buff’ has no member named ‘nh’
/tmp/vmware-config0/vmnet-only/userif.c:636: error: ‘const struct sk_buff’ has no member named ‘h’
make[2]: *** [/tmp/vmware-config0/vmnet-only/userif.o] Error 1
make[1]: *** [_module_/tmp/vmware-config0/vmnet-only] Error 2
make[1]: Leaving directory `/usr/src/linux-headers-2.6.22-9-386'
make: *** [vmnet.ko] Error 2
make: Leaving directory `/tmp/vmware-config0/vmnet-only'
Unable to build the vmnet module.

One tip as always, I solved this problem by just using vmware-any-any. The one I used is 113.

Then extract it and simply run sudo ./runme.pl.

Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config1/vmnet-only'
make -C /lib/modules/2.6.22-9-386/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.22-9-386'
  CC [M]  /tmp/vmware-config1/vmnet-only/driver.o
  CC [M]  /tmp/vmware-config1/vmnet-only/hub.o
  CC [M]  /tmp/vmware-config1/vmnet-only/userif.o
  CC [M]  /tmp/vmware-config1/vmnet-only/netif.o
  CC [M]  /tmp/vmware-config1/vmnet-only/bridge.o
  CC [M]  /tmp/vmware-config1/vmnet-only/filter.o
  CC [M]  /tmp/vmware-config1/vmnet-only/procfs.o
  CC [M]  /tmp/vmware-config1/vmnet-only/smac_compat.o
  CC [M]  /tmp/vmware-config1/vmnet-only/smac_linux.x386.o
  LD [M]  /tmp/vmware-config1/vmnet-only/vmnet.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /tmp/vmware-config1/vmnet-only/vmnet.mod.o
  LD [M]  /tmp/vmware-config1/vmnet-only/vmnet.ko
make[1]: Leaving directory `/usr/src/linux-headers-2.6.22-9-386'
cp -f vmnet.ko ./../vmnet.o
make: Leaving directory `/tmp/vmware-config1/vmnet-only'
The module loads perfectly in the running kernel.

Tags: , ,

Linux sucks

On August 14th, 2007 Anonymous (not verified) says:
For the record, I understand this "any any" patch works, but I refuse to install it. How the hell do we know if this is a trustworthy source? I mean, you're patching stuff that you run as root. There's nothing more dangerous than that. For a while, I thought that VMware should just set up a repository for Ubuntu, or Fedora or whatever distribution so that we can automatically get a working version if the kernel was upgraded. However, the Linux 2.6 kernel is always in motion and completely lacks compatibility to earlier 2.6 version. For an so-called enterprise product, this is really a joke. Compare that to Solaris e.g. If Solaris becomes GPL3, Linux will become irrelevant pretty quickly. Then, Mr. Torvalds can go back to his "little hobby".
  • reply
  • be

Re: Linux sucks

On August 18th, 2007 Anonymous says:
yeah right... so you realy think ppl will leave Linux for Solaris :) Well this is what's make Linux so great! Even if, in this case, vmware does not support you own kernel there is often someone else out there who solved the problem. He also gives you the source code so why not read it and make sure for you self that it is clean from bad stuff.
  • reply
  • se

Go read the source!

On August 31st, 2007 Anonymous (not verified) says:
Just go be happy.
  • reply
  • us

Is it Linux that sucks or

On September 4th, 2007 Anonymous (not verified) says:
Is it Linux that sucks or the idiots that write malicous code ? Im freaking tired of ****** that think they are so good that they spend their life trying to screw your machine and hack into you server by using malicous code.. Theres no dignity no honour in what they do, they are just a bunch of fools.. So dont blame Linux blame the idiots that resort to writing crap to exploit your box. blame the black hats.. Biggest arse holes on this planet.. They should be round up and shot .. A user thats just tired of constantly having to look over their shoulder so as to make sure they aint stepped in some one elses excrement..
  • reply
  • us

Further to the comment

On September 4th, 2007 Anonymous (not verified) says:
Further to the comment above.. Those idiots are exactly the type that make everyone else out to do a good thing look bad. There are hundreds to thousands of people out there producing good code producing little tools to solve their own problems which might inadvertently solve your problem too or do it specifically to try and help everyone else out.. Then there are the brain dead morons, that look into the code check up against some vulnerability database and try and do something malicious with it, or find a vulnerability and use it for malicious intent .. All props and respect to you if your doing a good turn pointing out a vulnerability for it to be fixed.. Contacting big software warehouses and showing flaws.. Eat my **** to the rest of you that find an exploit and use it to access individual users information that use it to screw over the end users.. That go out of your way to try and screw over a person behind their machine.. You ain't doing any one any favors, your just selfish individuals that give everyone doing good a bad name. Sucks to be you it truly does.... Your not smart your just an idiot !!
  • reply
  • us

linux sucks cos u cant use it

On September 4th, 2007 Anonymous (not verified) says:
the subject says it all now go and buy linux for dummies
  • reply
  • us

On fedora7 the vmnet was not

On September 4th, 2007 Anonymous (not verified) says:
On fedora7 the vmnet was not building, moved the vmnet.tar from the any-any patch into /usr/lib/vmware/modules/source and moved the original vmnet.tar to a backup and started vmwarec-config.pl.. worked a treat..
  • reply
  • at

Can you run it when you are done compiling?

On September 5th, 2007 John DeCarlo (not verified) says:
I can compile with any one of several approaches (CC=g++, vmnet.tar patch, anyany patch), but they all result in: "/usr/lib/vmware/bin/vmplayer: error while loading shared libraries: /usr/lib/vmware/lib/libvmwareui.so.0/libvmwareui.so.0: invalid ELF header I just installed Gutsy Tribe 5 over the weekend. Thanks.
  • reply
  • us

yes

On September 5th, 2007 sugree says:
Yes, I can. I just upgraded to the last kernel this morning and it still works.
  • reply
  • th

Thanks

On September 29th, 2007 Kreuger Burns (not verified) says:
Thank you so much for this, it helped me get my VMWare back up and running :)
  • reply
  • ca

Damn ELVES! If I had a

On October 13th, 2007 Anonymous (not verified) says:
Damn ELVES! If I had a dollar for every time an ELF crashed my app stack...
  • reply
  • us

I dunno why we need to

On April 28th, 2008 man (not verified) says:
I dunno why we need to download anybody else's patch, we can read the code and patch it ourselves. I remember that on Slackware 12.0 VMWare wouldn't work unless I had an /etc/init.d directory , etc, etc. Still got round to looking up the var unsigned errors and other crazy stuff. Fixed it mostly by hand, and one or two diff files ... (note if you can read code its enuf ... watchout for free() being called more than once and all that ;-) ) Finally built and installed VMware Server without much more issues on Slackware 12.0 which I had running on a 2.6.x kernel.
  • reply
  • in

Post new comment