How To Install VMware Server On A Fedora Core 6 Desktop

Version 1.0
Author: Falko Timme

This tutorial provides step-by-step instructions on how to install VMware Server on a Fedora Core 6 desktop system. With VMware Server you can create and run guest operating systems ("virtual machines") such as Linux, Windows, FreeBSD, etc. under a host operating system. This has the benefit that you can run multiple operating systems on the same hardware which saves a lot of money, and you can move virtual machines from one VMware Server to the next one (or to a system that has the VMware Player which is also free).

Also, with VMware Server you can let your old Windows desktop (that you previously converted into a VMware virtual machine with VMware Converter, as described in this tutorial: run under your Fedora desktop. This can be useful if you depend on some applications that exist for Windows only, or if you want to switch to Linux slowly.

I want to say first that this is not the only way of setting up such a system. There are many ways of achieving this goal but this is the way I take. I do not issue any guarantee that this will work for you!


1 Installing Required Packages

Before we install VMware Server, we must install some prerequisites. To install them, go to Applications > Add/Remove Software:

Type in the root password:

The Package Manager opens. Go to the Browse tab and select:

  • Development > Development Libraries
  • Development > Development Tools

Then go to the List tab. Select the following package for installation and click on Apply afterwards:

  • xinetd

The Package Manager will then resolve all dependencies, download the packages, maybe ask you to accept some unknown software keys (please accept them), and finally install the packages.


2 VMware Server

To download VMware Server, go to and click on Download Now:

Accept the license agreement by clicking on Yes:

Then download the VMware Server for Linux .tar.gz file (not the rpm file!), e.g. to /home/falko/Desktop:

Then open a terminal and become root:


Then do this:

cd /home/falko/Desktop
tar xvfz VMware-server-*.tar.gz

It is possible that you get this error when you run the VMware installer later on:

make[1]: Entering directory `/usr/src/kernels/2.6.19-1.2911.fc6-i686'
  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/procfs.o
/tmp/vmware-config1/vmnet-only/procfs.c:33:26: error: linux/config.h: No such file or directory

To avoid that, we simply create that config.h file now:

touch /usr/src/kernels/`uname -r`-i686/include/linux/config.h

Before we run the VMware installer, we should check our kernel version now by running:

uname -r

For me, the output looks like this:

[[email protected] Desktop]# uname -r

Now we start the VMware installer:

cd vmware-server-distrib

The installer will ask you a lot of questions. You can always accept the default values simply by hitting <ENTER>. If you don't get any errors, go to chapter 19.1 Finishing The VMware Server Installation.

If your kernel is 2.6.19, you will most likely get an error like this:

Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config0/vmnet-only'
make -C /lib/modules/2.6.19-1.2911.fc6/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/kernels/2.6.19-1.2911.fc6-i686'
  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:629: error: 'CHECKSUM_HW' undeclared (first use in this function)
/tmp/vmware-config0/vmnet-only/userif.c:629: error: (Each undeclared identifier is reported only once
/tmp/vmware-config0/vmnet-only/userif.c:629: error: for each function it appears in.)
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/kernels/2.6.19-1.2911.fc6-i686'
make: *** [vmnet.ko] Error 2
make: Leaving directory `/tmp/vmware-config0/vmnet-only'
Unable to build the vmnet module.

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

Execution aborted.

In kernel 2.6.19, CHECKSUM_HW has been replaced by CHECKSUM_PARTIAL. So if you get that error, do this:

cd /usr/lib/vmware/modules/source/
tar -xvvf vmnet.tar
cd vmnet-only/
gedit bridge.c

In the text editor that comes up replace CHECKSUM_HW with CHECKSUM_PARTIAL, then save the file:

Do the same for the file userif.c:

gedit userif.c 

Then run

cd ..
tar -cvvf vmnet.tar vmnet-only/

This will take you through the VMware configuration again. Again, accept all default values.

If you get this error:

This program previously created the file /dev/vmmon, and was about to remove
it. Somebody else apparently did it already.

mknod: `/dev/vmmon': File exists
Unable to create the character device /dev/vmmon with major number 10 and minor
number 165.

Execution aborted.

simply run


again. This time the error will be gone, and the VMware Server installation should finally succeed.


2.1 Finishing The VMware Server Installation

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:

Go to again and click on the Register button:

Fill in your personal details. Afterwards you will get a page with serial numbers for VMware Server. Copy one of them and paste it into the terminal where you were asked for the serial number.

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

cd /home/falko/Desktop
rm -fr vmware-server-distrib
rm -f VMware-server-*.tar.gz

You will now find VMware Server under Applications > System Tools:

When you start it, select Local host:

Afterwards, you can create virtual machines (or import your virtual Windows machine that you created with VMware Converter):


Share this page:

Suggested articles

5 Comment(s)

Add comment



1) Stop and turn off Xend daemon (service xend stop ; chkconfig xend off)

2) Edit grub to use the non-xen kernel (default= etc etc)

3) Install kernel-devel (yum install kernel-devel)

4) Install xinetd (yum install xinetd)

5) Install vmware-server (rpm -ivvh  blah)

6) reboot 




Hi. Because i don't know how i can add howto, i'm  writing here.

If you have a problem about VMware-server new version like me, you can fallow this way

 # yum install kernel-xen kernel-devel-xen

if you use same kernel version  with xen, change grub.conf for using xen in boot

# reboot 

# wget
# wget
# rpm -Uvh VMware-server-1.0.3-44356.i386.rpm
# tar -xvf vmware-any-any-update109.tar.gz
# cd vmware-any-any-update109
# ./


If you get de following error when running the VMWare server install:

Building the vmmon module.

Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config1/vmmon-only'
make -C /lib/modules/ SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-'
  CC [M]  /tmp/vmware-config1/vmmon-only/linux/driver.o
In file included from /tmp/vmware-config1/vmmon-only/linux/driver.c:80:
/tmp/vmware-config1/vmmon-only/./include/compat_kernel.h:21: error: expected declaration specifiers or ‘...’ before ‘compat_exit’
/tmp/vmware-config1/vmmon-only/./include/compat_kernel.h:21: error: expected declaration specifiers or ‘...’ before ‘exit_code’
/tmp/vmware-config1/vmmon-only/./include/compat_kernel.h:21: warning: type defaults to ‘int’ in declaration of ‘_syscall1’
make[2]: *** [/tmp/vmware-config1/vmmon-only/linux/driver.o] Error 1
make[1]: *** [_module_/tmp/vmware-config1/vmmon-only] Error 2
make[1]: Leaving directory `/usr/src/linux-'
make: *** [vmmon.ko] Error 2
make: Leaving directory `/tmp/vmware-config1/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

You can try this solution. It worked for me on a FC6/2.6.20 kernel

Have a look at this page - ... it's talking about VMWare player, but I had the same error when tried to build the vmmon kernel module under Ubuntu with 2.6.20.

You need to -
* Make a backup of /usr/lib/vmware/modules/source/vmmon.tar

cd /usr/lib/vmware/modules/source/
cp vmmon.tar vmmon.tar.old

* Untar /usr/lib/vmware/modules/source/vmmon.tar into a temporary directory

tar -xvvf vmmon.tar
* Modify vmmon-only/include/compat_kernel.h, and change:

cd vmmon-only/include
vi compat_kernel.h

#define __NR_compat_exit __NR_exit
static inline _syscall1(int, compat_exit, int, exit_code);


#define __NR_compat_exit __NR_exit
static inline _syscall1(int, compat_exit, int, exit_code);

* Finally, tar the modified module source back up, and replace the vmmon.tar in /usr/lib/vmware/modules/source/

cd ../..
tar -cvvf vmmon.tar vmmon-only/

Hope this helps :)

Found at:




I upgraded my FC6 to "Linux hostname #1 SMP Wed Aug 15 11:52:47 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux"

Had this problem, which was quickly resolved thanks to information here. It then went much further, but bailed again:

/tmp/vmware-config5/vmnet-only/userif.c: In function ‘VNetCopyDatagramToUser’: /tmp/vmware-config5/vmnet-only/userif.c:630: error: ‘const struct sk_buff’ has no member named ‘h’ /tmp/vmware-config5/vmnet-only/userif.c:630: error: ‘const struct sk_buff’ has no member named ‘nh’ /tmp/vmware-config5/vmnet-only/userif.c:636: error: ‘const struct sk_buff’ has no member named ‘h’

Now I'm off in search of a second resolution.


I was intending to reply to my previous post which is not posted yet.

I reviewed the patch. It's just a bunch of structure member name changes from cryptic names prior to 2.6.22 to more fully explanatory names. I regard the name changes as an improvement in code clarity. The change is unlikely to bork anything, even if VMWare, as of yet, warns people off this kernel as unsupported.