Help installing VMware Server on Ubuntu 10.10

[kwiatu5]

I'm wokring and I think that I'll have a solution this night. Be patient!

[kwiatu5]

So... The problem is that the vmware-server-distrib/bin/vmware-config.pl script doesn't recognize version of our kernel headers. So let help him to pass this test.

I put new line at 2713 line in vmware-config.pl (use VIM or VI).
And I write this, to pass next test of kernel version:

$header_version_uts=$gSystem{'uts_release'};

It looks like that with above line (bolded):

$header_version_uts = direct_command(
shell_string($gHelper{'echo'}) . ' '
. shell_string($uts_headers . $pattern
. ' UTS_RELEASE') . ' | ' . shell_string($gHelper{'gcc'})
. ' ' . shell_string('-I' . $answer) . ' -E - | '
. shell_string($gHelper{'grep'}) . ' ' . shell_string($pattern));
chomp($header_version_uts);
$header_version_uts =~ s/^$pattern \"([^\"]*)\".*$/$1/;
$header_version_uts=$gSystem{'uts_release'};
if (not ($header_version_uts eq $gSystem{'uts_release'})) {
if ($source eq 'user') {
print wrap('The directory of kernel headers (version '
. $header_version_uts . ') does not match your running '
. 'kernel (version ' . $gSystem{'uts_release'} . '). Even '
. 'if the module were to compile successfully, it would not '
. 'load into the running kernel.' . "\n\n", 0);
}
return '';
}
}

Good way is to create symbolic link at /usr/src/linux to /usr/src/linux-headers-2.6.35-22-generic
Save file and run: sudo ./bin/vmware-config.pl

[aaron465]

I have installed linux-headers-2.6.35-22-generic from apt and edited the vmware-config.pl file as you suggested (as well as creating the symbolic link) but now I get this error:

What is the location of the directory of C header files that match your running
kernel? [/usr/src/linux/include]

The path "/usr/src/linux/include" is a kernel header file directory, but it
does not contain the file "linux/autoconf.h" as expected.  This can happen if
the kernel has never been built, or if you have invoked the "make mrproper"
command in your kernel directory.  In any case, you may want to rebuild your
kernel.

Do you have any other ideas?

Thanks,
Aaron

[kwiatu5]

Try:

cp /usr/src/linux-headers-2.6.35-22-generic/include/generated/autoconf.h /usr/src/linux-headers-2.6.35-22-generic/include/linux/autoconf.h

[aaron465]

Hmm it is not happy, the vmmon module is failing to compile now.

root@JohnConnor:/home/aaron/vmware-server-distrib/bin# ./vmware-config.pl
Making sure services for VMware Server are stopped.

Stopping VMware autostart virtual machines:
   Virtual machines                                                   failed
Stopping VMware management services:
   VMware Virtual Infrastructure Web Access
   VMware Server Host Agent                                           failed
Stopping VMware services:
   VMware Authentication Daemon                                        done
   Virtual machine monitor                                             done

None of the pre-built vmmon modules for VMware Server is suitable for your
running kernel.  Do you want this program to try to build the vmmon module for
your system (you need to have a C compiler installed on your system)? [yes]

Using compiler "/usr/bin/gcc". Use environment variable CC to override.

What is the location of the directory of C header files that match your running
kernel? [/usr/src/linux/include] /usr/src/linux-headers-2.6.35-22-generic/include

Extracting the sources of the vmmon module.

Building the vmmon module.

Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config0/vmmon-only'
make -C /usr/src/linux-headers-2.6.35-22-generic/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.35-22-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:72: 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: warning: "__FreeBSD__" is not defined
In file included from /tmp/vmware-config0/vmmon-only/./common/vmx86.h:32,
                 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/x86msr.h:164: warning: "MSR_THERM2_CTL" redefined
/usr/src/linux-headers-2.6.35-22-generic/arch/x86/include/asm/msr-index.h:236: note: this is the location of the previous definition
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: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:333: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:401: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:407: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h: In function âAtomic_ReadIfEqualWrite64â:
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:460: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h: In function âAtomic_Andâ:
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:506: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h: In function âAtomic_And64â:
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:551: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h: In function âAtomic_Orâ:
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:595: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h: In function âAtomic_Or64â:
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:640: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h: In function âAtomic_Xorâ:
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:684: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h: In function âAtomic_Xor64â:
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:729: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h: In function âAtomic_Addâ:
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:773: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:775: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h: In function âAtomic_Add64â:
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:816: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h: In function âAtomic_Subâ:
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:860: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:862: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h: In function âAtomic_Sub64â:
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:903: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h: In function âAtomic_Incâ:
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:945: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:947: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h: In function âAtomic_Inc64â:
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:986: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h: In function âAtomic_Decâ:
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:1028: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:1030: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h: In function âAtomic_Dec64â:
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:1069: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h: At top level:
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:1223: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:1227: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h: In function âAtomic_ReadAdd64â:
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:1313: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h: At top level:
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:1536: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:1663: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h: In function âAtomic_ReadWrite64â:
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:1796: 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: At top level:
/tmp/vmware-config0/vmmon-only/./include/vm_asm_x86.h:486: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_asm_x86.h:779: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_asm_x86.h:820: warning: "_MSC_VER" is not defined
/tmp/vmware-config0/vmmon-only/./include/vm_asm_x86.h:922: 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: 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: 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.35-22-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 "http://www.vmware.com/go/unsup-linux-products" and
"http://www.vmware.com/go/unsup-linux-tools".

Execution aborted.

I assume that vmware will fix this themselves eventually with an update or patch of some kind?

[kwiatu5]

This is for you aaron465: http://www.saarlinux.de/blog/?p=5


So I've solved this problem, but now I don' know how many patches I used to do it. I think that useful pathes are:
http://www.saarlinux.de/blog/?p=5
and this one: http://www.jwh.me.uk/2009/10/03/comp...t-2-6-kernels/

I'm reminding that I use:
VMware-server-2.0.2-203138.i386.tar.gz
Ubuntu 10.10 x86 Desktop with 2.6.35-22-generic Kernel

You can overvrite your modules at /usr/lib/vmware/modules/source by using my patched modules, but remember that you do it for your own risk and I'm not take care and rensponsibility for any damages.

Download:
vmci.tar vmmon.tar vmnet.tar vsock.tar

I paste it only for education need and I can delete if I trespass copyrights.

[aaron465]

Fantastic, this worked a treat!

Thank you very much for your help,
Aaron

UPDATE: It installed but vmci does not seem to work, and I cannot start any virtual machines! This is starting to annoy me now! Sort it out vmware!

[kwiatu5]

aaron465, paste here a information from debugger why vmci won't start.

I worked around problem with vsock.tar with VMware Player 3.1.2 build-301548 which wasn't able to start. I applied to my /usr/lib/vmware/modules/source/vsock.tar (you can download it from second post above) this how-to -> https://bbs.archlinux.org/viewtopic.php?pid=836641 and it's works perfectly.
VMPlayer 3.1.2 on Ubuntu 10.10 with 2.6.35-22-generic works perfectly!!!

I just uninstalled VMWare Server 2.0.2 where I had also problems with remote control plugin to firefox 3.6.10... VMWare Player gives functions to create wirtual machines so I have all what I want. Many hours with Server 2.0.2... damn... but ok. If somebody want to start VMWare Server on ubuntu 10.10 can do it

regards,
Piotr Kwiatek

[aaron465]

Thanks for your help, I am using Virtualbox with cli now, vmware has caused too much hassle!

Aaron

[fjgaude]

My feelings as of now is that VMware Server is dead in the water, with little VMware support. Their Player takes its place and if that isn't good enough go to Workstation. For a real server requirement they wish us to go to ESXi.

Player 3.1.2 is all I need in my present situation.