Comments on How To Install VMware Server On A Fedora Core 6 Desktop

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 http://ftp.cvut.cz/vmware/vmware-any-any-update109.tar.gz
# wget http://download3.vmware.com/software/vmserver/VMware-server-1.0.3-44356.i386.rpm
# rpm -Uvh VMware-server-1.0.3-44356.i386.rpm
# tar -xvf vmware-any-any-update109.tar.gz
# cd vmware-any-any-update109
# ./run.pl

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/2.6.20.1/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-2.6.20.1'
  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-2.6.20.1'
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 "http://www.vmware.com/download/modules/modules.html" and
"http://www.vmware.com/support/reference/linux/prebuilt_modules_linux.html".

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

Have a look at this page - http://kb.barnoid.com/?p=18 ... it's talking about VMWare player, but I had the same error when vmware-config.pl 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);

to:

#define __NR_compat_exit __NR_exit
#if LINUX_VERSION_CODE < KERNEL_VERSION(2,6,19)
static inline _syscall1(int, compat_exit, int, exit_code);
#endif

* 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: http://www.vmware.com/community/thread.jspa?messageID=629085&#629085

Cheers,

 Pepo

I upgraded my FC6 to "Linux hostname 2.6.22.2-42.fc6 #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.