[MDV2010.0] VMware Server 2, stuck during install - C Header files?
Linux - Virtualization and CloudThis forum is for the discussion of all topics relating to Linux Virtualization and Linux Cloud platforms. Xen, KVM, OpenVZ, VirtualBox, VMware, Linux-VServer and all other Linux Virtualization platforms are welcome. OpenStack, CloudStack, ownCloud, Cloud Foundry, Eucalyptus, Nimbus, OpenNebula and all other Linux Cloud platforms are welcome. Note that questions relating solely to non-Linux OS's should be asked in the General forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
[MDV2010.0] VMware Server 2, stuck during install - C Header files?
During installation of VMware Server 2 from the tarball (VMware-server-2.0.1-156745.i386.tar.gz) provided by VMware proceeds as expected, until we reach this point:
Code:
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/version.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.
What is the location of the directory of C header files that match your running
kernel? [/usr/src/linux/include]
No matter what path you point it at, it is not accepted. 'version.h' is nowhere to be found on the system between the source files.
This system is running:
Code:
uname -r
2.6.31.6-desktop-1mnb
And to be sure I installed the right packages before starting, I checked these items:
I re-checked the already installed packages, and added three more next-best matches:
kernel-desktop-devel-2.6.31.6-1mnb-1-1mnb2.i586
kernel-desktop-devel-latest-2.6.31.6-1mnb2.i586
kernel-source-latest-2.6.31.6-1mnb2.i586
The default path suggested by VMware's installer points to a symlink present on the machine, which in turn points to the wrong kernel sources.
I again tried with the correct path:
Code:
What is the location of the directory of C header files that match your running
kernel? [/usr/src/linux/include] /usr/src/linux-2.6.31.6-desktop-1mnb/include
Extracting the sources of the vmmon module.
Building the vmmon module.
Using 2.6.x kernel build system.
make: Entering directory `/root/tmp/vmware-config0/vmmon-only'
make -C /usr/src/linux-2.6.31.6-desktop-1mnb/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-2.6.31.6-desktop-1mnb'
CC [M] /root/tmp/vmware-config0/vmmon-only/linux/driver.o
In file included from /root/tmp/vmware-config0/vmmon-only/linux/driver.c:31:
/root/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 /root/tmp/vmware-config0/vmmon-only/./include/vmware.h:38,
from /root/tmp/vmware-config0/vmmon-only/linux/driver.c:99:
/root/tmp/vmware-config0/vmmon-only/./include/vm_basic_types.h:108:7: warning: "__FreeBSD__" is not defined
In file included from /root/tmp/vmware-config0/vmmon-only/./include/vcpuset.h:103,
from /root/tmp/vmware-config0/vmmon-only/./include/modulecall.h:37,
from /root/tmp/vmware-config0/vmmon-only/./common/vmx86.h:33,
from /root/tmp/vmware-config0/vmmon-only/linux/driver.h:29,
from /root/tmp/vmware-config0/vmmon-only/linux/driver.c:101:
/root/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:329:7: warning: "_MSC_VER" is not defined
/root/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:333:7: warning: "_MSC_VER" is not defined
/root/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:401:7: warning: "_MSC_VER" is not defined
/root/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:407:7: warning: "_MSC_VER" is not defined
/root/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:506:7: warning: "_MSC_VER" is not defined
/root/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:595:7: warning: "_MSC_VER" is not defined
/root/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:684:7: warning: "_MSC_VER" is not defined
/root/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:773:7: warning: "_MSC_VER" is not defined
/root/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:775:7: warning: "_MSC_VER" is not defined
/root/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:860:7: warning: "_MSC_VER" is not defined
/root/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:862:7: warning: "_MSC_VER" is not defined
/root/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:945:7: warning: "_MSC_VER" is not defined
/root/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:947:7: warning: "_MSC_VER" is not defined
/root/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:1028:7: warning: "_MSC_VER" is not defined
/root/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:1030:7: warning: "_MSC_VER" is not defined
/root/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:1223:7: warning: "_MSC_VER" is not defined
/root/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:1227:7: warning: "_MSC_VER" is not defined
/root/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:1536:7: warning: "_MSC_VER" is not defined
/root/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:1663:7: warning: "_MSC_VER" is not defined
In file included from /root/tmp/vmware-config0/vmmon-only/./include/vm_basic_asm.h:46,
from /root/tmp/vmware-config0/vmmon-only/./include/rateconv.h:45,
from /root/tmp/vmware-config0/vmmon-only/./include/modulecall.h:40,
from /root/tmp/vmware-config0/vmmon-only/./common/vmx86.h:33,
from /root/tmp/vmware-config0/vmmon-only/linux/driver.h:29,
from /root/tmp/vmware-config0/vmmon-only/linux/driver.c:101:
/root/tmp/vmware-config0/vmmon-only/./include/vm_basic_asm_x86.h:62:7: warning: "_MSC_VER" is not defined
/root/tmp/vmware-config0/vmmon-only/./include/vm_basic_asm_x86.h:177:7: warning: "_MSC_VER" is not defined
/root/tmp/vmware-config0/vmmon-only/./include/vm_basic_asm_x86.h:346:7: warning: "_MSC_VER" is not defined
/root/tmp/vmware-config0/vmmon-only/./include/vm_basic_asm_x86.h:453:7: warning: "_MSC_VER" is not defined
In file included from /root/tmp/vmware-config0/vmmon-only/./include/vm_asm.h:43,
from /root/tmp/vmware-config0/vmmon-only/linux/driver.c:103:
/root/tmp/vmware-config0/vmmon-only/./include/vm_asm_x86.h:486:7: warning: "_MSC_VER" is not defined
/root/tmp/vmware-config0/vmmon-only/./include/vm_asm_x86.h:779:7: warning: "_MSC_VER" is not defined
/root/tmp/vmware-config0/vmmon-only/./include/vm_asm_x86.h:820:7: warning: "_MSC_VER" is not defined
/root/tmp/vmware-config0/vmmon-only/./include/vm_asm_x86.h:922:7: warning: "_MSC_VER" is not defined
In file included from /root/tmp/vmware-config0/vmmon-only/linux/driver.c:119:
/root/tmp/vmware-config0/vmmon-only/./common/hostif.h:53:7: warning: "WINNT_DDK" is not defined
/root/tmp/vmware-config0/vmmon-only/linux/driver.c: In function ‘LinuxDriverSyncCallOnEachCPU’:
/root/tmp/vmware-config0/vmmon-only/linux/driver.c:1423: error: too many arguments to function ‘smp_call_function’
/root/tmp/vmware-config0/vmmon-only/linux/driver.c: In function ‘LinuxDriver_Ioctl’:
/root/tmp/vmware-config0/vmmon-only/linux/driver.c:1987: error: ‘struct task_struct’ has no member named ‘euid’
/root/tmp/vmware-config0/vmmon-only/linux/driver.c:1987: error: ‘struct task_struct’ has no member named ‘uid’
/root/tmp/vmware-config0/vmmon-only/linux/driver.c:1988: error: ‘struct task_struct’ has no member named ‘fsuid’
/root/tmp/vmware-config0/vmmon-only/linux/driver.c:1988: error: ‘struct task_struct’ has no member named ‘uid’
/root/tmp/vmware-config0/vmmon-only/linux/driver.c:1989: error: ‘struct task_struct’ has no member named ‘egid’
/root/tmp/vmware-config0/vmmon-only/linux/driver.c:1989: error: ‘struct task_struct’ has no member named ‘gid’
/root/tmp/vmware-config0/vmmon-only/linux/driver.c:1990: error: ‘struct task_struct’ has no member named ‘fsgid’
/root/tmp/vmware-config0/vmmon-only/linux/driver.c:1990: error: ‘struct task_struct’ has no member named ‘gid’
/root/tmp/vmware-config0/vmmon-only/linux/driver.c:2007: error: too many arguments to function ‘smp_call_function’
make[2]: *** [/root/tmp/vmware-config0/vmmon-only/linux/driver.o] Error 1
make[1]: *** [_module_/root/tmp/vmware-config0/vmmon-only] Error 2
make[1]: Leaving directory `/usr/src/linux-2.6.31.6-desktop-1mnb'
make: *** [vmmon.ko] Error 2
make: Leaving directory `/root/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.
This time the installer accepts the path, but fails during build.
reinstall only kernel-source-latest-2.6.31.6-1mnb2.i586 ?
"kernel-source-latest-2.6.31.6-1mnb2.i586" appears to be hidden under the package name "kernel-source-latest" in Mandriva's software management program. I'm glad they at least list the version and release number next to it in separate columns, else I would not have been able to identify it.. because "kernel-source-latest-2.6.31.6-1mnb2.i586" will not appear in a package search even if set to search 'all'.
Result of selecting it:
Code:
The following 2 packages are going to be installed:
- kernel-source-2.6.31.6-1mnb-1-1mnb2.i586
- kernel-source-latest-2.6.31.6-1mnb2.i586
284MB of additional disk space will be used.
50MB of packages will be retrieved.
Is it ok to continue?
Unfortunately, this apparently does not include the 'version.h' file VMware is looking for.
Unfortunately, i can't help you more.
I don't use MDV since 2003 and i usually compile kernel myself... Maybe should you consider it ?
Anyway, i wish you good luck.
That's okay.
I get the feeling Mandriva has gone a bit overboard with their customizations.
Unfortunately I can't afford to make many mistakes learning to compile my own kernel, I need this machine for work purposes, adding VMware to the mix was supposed to be a half day exercise so I could continue studying virtualization.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.