How To Install VMware Server 2 On Ubuntu 9.10 - Page 2

If the installation aborts with the following error...

Building the vmmon module.

Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config0/vmmon-only'
make -C /lib/modules/2.6.31-14-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.31-14-generic'
  CC [M]  /tmp/vmware-config0/vmmon-only/linux/driver.o
In file included from /tmp/vmware-config0/vmmon-only/linux/driver.c:31:
/tmp/vmware-config0/vmmon-only/./include/compat_wait.h:78: error: conflicting types for â€˜poll_initwait’
include/linux/poll.h:70: note: previous declaration of â€˜poll_initwait’ was here
In file included from /tmp/vmware-config0/vmmon-only/./include/vmware.h:38,
                 from /tmp/vmware-config0/vmmon-only/linux/driver.c:99:
/tmp/vmware-config0/vmmon-only/./include/vm_basic_types.h:108:7: warning: "__FreeBSD__" is not defined
In file included from /tmp/vmware-config0/vmmon-only/./include/vcpuset.h:103,
                 from /tmp/vmware-config0/vmmon-only/./include/modulecall.h:37,
                 from /tmp/vmware-config0/vmmon-only/./common/vmx86.h:33,
                 from /tmp/vmware-config0/vmmon-only/linux/driver.h:29,
                 from /tmp/vmware-config0/vmmon-only/linux/driver.c:101:
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:329:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:333:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:401:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:407:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:460:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:506:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:551:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:595:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:640:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:684:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:729:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:773:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:775:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:816:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:860:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:862:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:903:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:945:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:947:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:986:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:1028:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:1030:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:1069:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:1223:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:1227:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:1313:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:1536:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:1663:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:1796:7: warning: "_MSC_VER" is not defined
In file included from /tmp/vmware-config0/vmmon-only/./include/vm_asm_x86_64.h:39,
                 from /tmp/vmware-config0/vmmon-only/./include/vm_asm.h:41,
                 from /tmp/vmware-config0/vmmon-only/linux/driver.c:103:
/tmp/vmware-config0/vmmon-only/./include/vm_asm_x86.h:486:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_asm_x86.h:779:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_asm_x86.h:820:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_asm_x86.h:922:7: warning: "_MSC_VER" is not defined
In file included from /tmp/vmware-config0/vmmon-only/./include/vm_asm.h:41,
                 from /tmp/vmware-config0/vmmon-only/linux/driver.c:103:
/tmp/vmware-config0/vmmon-only/./include/vm_asm_x86_64.h:56:7: warning: "_MSC_VER" is not defined
In file included from /tmp/vmware-config0/vmmon-only/linux/driver.c:119:
/tmp/vmware-config0/vmmon-only/./common/hostif.h:53:7: warning: "WINNT_DDK" is not defined
/tmp/vmware-config0/vmmon-only/linux/driver.c: In function â€˜LinuxDriverSyncCallOnEachCPU’:
/tmp/vmware-config0/vmmon-only/linux/driver.c:1423: error: too many arguments to function â€˜smp_call_function’
/tmp/vmware-config0/vmmon-only/linux/driver.c: In function â€˜LinuxDriver_Ioctl’:
/tmp/vmware-config0/vmmon-only/linux/driver.c:1987: error: â€˜struct task_struct’ has no member named â€˜euid’
/tmp/vmware-config0/vmmon-only/linux/driver.c:1987: error: â€˜struct task_struct’ has no member named â€˜uid’
/tmp/vmware-config0/vmmon-only/linux/driver.c:1988: error: â€˜struct task_struct’ has no member named â€˜fsuid’
/tmp/vmware-config0/vmmon-only/linux/driver.c:1988: error: â€˜struct task_struct’ has no member named â€˜uid’
/tmp/vmware-config0/vmmon-only/linux/driver.c:1989: error: â€˜struct task_struct’ has no member named â€˜egid’
/tmp/vmware-config0/vmmon-only/linux/driver.c:1989: error: â€˜struct task_struct’ has no member named â€˜gid’
/tmp/vmware-config0/vmmon-only/linux/driver.c:1990: error: â€˜struct task_struct’ has no member named â€˜fsgid’
/tmp/vmware-config0/vmmon-only/linux/driver.c:1990: error: â€˜struct task_struct’ has no member named â€˜gid’
/tmp/vmware-config0/vmmon-only/linux/driver.c:2007: error: too many arguments to function â€˜smp_call_function’
make[2]: *** [/tmp/vmware-config0/vmmon-only/linux/driver.o] Error 1
make[1]: *** [_module_/tmp/vmware-config0/vmmon-only] Error 2
make[1]: Leaving directory `/usr/src/linux-headers-2.6.31-14-generic'
make: *** [vmmon.ko] Error 2
make: Leaving directory `/tmp/vmware-config0/vmmon-only'
Unable to build the vmmon module.

For more information on how to troubleshoot module-related problems, please
visit our Web site at "" and

Execution aborted.


... please do the following (I found this solution on

cd ~/Downloads
rm -fr vmware-server-distrib/
chmod +x
sudo ./

This will patch the VMware Server 2 installer and start the installation again. As before, the installer will ask you a lot of questions. You can always accept the default values simply by hitting <ENTER>.

When the installer asks you

In which directory do you want to keep your virtual machine files?
[/var/lib/vmware/Virtual Machines]

you can either accept the default value or specify a location that has enough free space to store your virtual machines.

At the end of the installation, you will be asked to enter a serial number:

Please enter your 20-character serial number.

Type XXXXX-XXXXX-XXXXX-XXXXX or 'Enter' to cancel:

Fill in your serial number for VMware Server.

After the successful installation, you can delete the VMware Server download file and the installation directory:

cd /home/falko/Downloads
rm -f VMware-server*
rm -fr vmware-server-distrib/

If you have accepted all default values during the installation, root is now the VMware Server login name. On Ubuntu, root has no password by default, therefore we create a password now:

sudo passwd root

VMware Server 2 does not have a desktop application for managing virtual machines - this is now done through a browser (e.g. Firefox). You can access the management interface over HTTPS (https://<IP ADDRESS>:8333) or HTTP (http://<IP ADDRESS>:8222); the management interface can be accessed locally and also remotely. If you want to access it from the same machine, type or into the browser's address bar.

If you're using Firefox 3 and use HTTPS, Firefox will complain about the self-signed certificate, therefore you must tell Firefox to accept the certificate - to do this, click on the I Understand the Risks link:

Click on Add Exception...:

The Add Security Exception window opens. In that window, click on the Get Certificate button first and then on the Confirm Security Exception button:

Afterwards, you will see the VMware Server login form. Type in root and the password you've just created:

This is how the VMware Server web interface looks. The structure is similar to the old VMware Server 1 desktop application, so the usage of the web interface is pretty straightforward.


3 Links

Share this page:

15 Comment(s)

Add comment


From: at: 2009-12-22 05:25:32

this is a great help for me,,



From: jhone at: 2009-12-27 06:11:14

Good one!

From: at: 2010-01-28 08:56:38

I will test. thank

From: BK at: 2009-12-31 16:06:40

Thanks!  I am a long time Window's junkie who is making the jump into the linux world.  I was toiling with this install for a while before I came upon your write-up.  Good work!  Thanks!

From: Radu at: 2009-12-21 17:12:33

It is not advisable to create a password for the root account. Therefore you'd better use your own user account when you are asked about VMware's Server administrator account.

The installation without the required patch (as supplied in my script) will fail (and not gracefully). So I suggest using the script from the beginning because in some cases traces of a failed installation of VMware Server might interfere with the patched installation done after.

By the way, people on my blog have said that the script also works on OpenSUSE 11.2 (but one should alter the lines which handle package dependencies).

For Mandriva a reader of my blog (Oliver Burger) adapted the script and put it online here. More details about how to use the script on Mandriva are provided here (German).

Thank you for making my script more popular among the Linux users!

From: Jeffrey Anthony at: 2009-12-26 17:57:51

The script worked perfectly, thank you very much.

Now how would one go about remotely getting and using (i.e. seeing) a virtual desktop and how many concurrent and/or total desktops can one server handle?

From: Jakob at: 2009-12-27 17:49:44

Great tutorial. All works as described ... leaving me in state of total aw.

Would not have made it without your help. Thank you.


From: Arindam at: 2010-01-19 12:15:54

Excellent article, got vmware working on my Ubuntu9.10 box in no time. Thanks a lot:-).

From: Steven Barden at: 2010-01-23 02:20:58

Thank you very much for your extreamly helpful artical. I was about to go back to Win08 x64 Core, and you saved me, and gave me a perm reason to use linux daily. I blasted you on a previous artical. This is what I know admire your work for.

Thank you.

From: Anonymous at: 2010-02-14 12:19:13

thank you very much!

 I'm an absolute rookie with ubuntu / linux and your instructions worked for me :))

 tnx again

From: systek at: 2010-03-02 19:43:08

The tutorial really does the job! I succsesfully moved from win xp to ubuntu.

Thanks a lot.

From an new Linux user.

From: Riccardo at: 2010-04-05 17:03:33

I found a lot of howto's on the internet, but none worked. Your howto was the only one that solved my problem. Thanks!

From: Moran Levy at: 2010-04-10 07:14:46

Thanks for this post .

Please notice that the script is updated and the wget link will not work ,just go to ( as linked in the post ) and get the new link from there

From: Dave at: 2010-04-25 10:59:26

Great! Many thanks! It's working alright.


From: Anton at: 2010-05-15 16:38:32

Thank you very much, great article and script, worked first time