VMWare Server 1.0.10

prppedro · 09-21-2011, 08:42 PM

Hi, folks!

I know that might sound absolutely horrible and deprecated, but I used to emulate a Win2k3 in VMWare, to get some Wine-proof apps working. That VMWare was VMWare Server 1.0.8, that used to work flawlessly with Debian Lenny (Kernel version 2.6.32-4-686 or so). But, when I upgraded my system to Squeeze, VMWare Server stopped to work. I tried to uninstall it, and downloaded V1.0.10, as well as 2.0.2. None of them worked, but I didn't managed to get 2.0.2 working as I tried with 1.x. Doesn't tried because 2.0.2 is like a mammoth installed on my PC.

I've applied a patch to my 1.x modules (VMware-specific-specific, that was written originally for VMWare Workstation 5.x). In the site (insecure.ws), some people reported that the patch works well with VMware Server 1.x, however, my kernel doesn't support init_mm, so, I had problems with the compiled module.

Now, I need to get this working, because it's very important to my 'academic' works. And no, I don't want to "try VirtualBox" or something else, because I never had great problems on getting VMware Server to work and that version (1.x) does a great working on managing host's hardware (At least on this jurassic machine), so, I don't want to switch it.

If someone knows what's happening, please give me some light on how to solve this.

Thanks, Pedro Pinheiro
And sorry for my bad english...

P.S.: The output:

Code:

Building for VMware Server 1.0.0.
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config0/vmmon-only'
make -C /lib/modules/2.6.32-5-686/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.32-5-686'
  CC [M]  /tmp/vmware-config0/vmmon-only/linux/driver.o
/tmp/vmware-config0/vmmon-only/linux/driver.c: In function ‘__LinuxDriver_Ioctl’:
/tmp/vmware-config0/vmmon-only/linux/driver.c:1768: warning: ‘new’ may be used uninitialized in this function
  CC [M]  /tmp/vmware-config0/vmmon-only/linux/driverLog.o
  CC [M]  /tmp/vmware-config0/vmmon-only/linux/hostif.o
/tmp/vmware-config0/vmmon-only/linux/hostif.c: In function ‘HostIF_SetFastClockRate’:
/tmp/vmware-config0/vmmon-only/linux/hostif.c:3462: warning: passing argument 2 of ‘send_sig’ discards qualifiers from pointer target type
  CC [M]  /tmp/vmware-config0/vmmon-only/common/comport.o
  CC [M]  /tmp/vmware-config0/vmmon-only/common/cpuid.o
  CC [M]  /tmp/vmware-config0/vmmon-only/common/hash.o
  CC [M]  /tmp/vmware-config0/vmmon-only/common/memtrack.o
  CC [M]  /tmp/vmware-config0/vmmon-only/common/phystrack.o
  CC [M]  /tmp/vmware-config0/vmmon-only/common/task.o
cc1plus: warning: command line option "-Werror-implicit-function-declaration" is valid for C/ObjC but not for C++
cc1plus: warning: command line option "-Wdeclaration-after-statement" is valid for C/ObjC but not for C++
cc1plus: warning: command line option "-Wno-pointer-sign" is valid for C/ObjC but not for C++
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for Ada/C/ObjC but not for C++
In file included from /tmp/vmware-config0/vmmon-only/common/task.c:1195:
/tmp/vmware-config0/vmmon-only/common/task_compat.h: In function ‘void Task_Switch_V45(VMDriver*, Vcpuid)’:
/tmp/vmware-config0/vmmon-only/common/task_compat.h:2667: warning: ‘sysenterState.SysenterStateV45::validEIP’ may be used uninitialized in this function
/tmp/vmware-config0/vmmon-only/common/task_compat.h:2667: warning: ‘sysenterState.SysenterStateV45::cs’ may be used uninitialized in this function
/tmp/vmware-config0/vmmon-only/common/task_compat.h:2667: warning: ‘sysenterState.SysenterStateV45::rsp’ may be used uninitialized in this function
/tmp/vmware-config0/vmmon-only/common/task_compat.h:2667: warning: ‘sysenterState.SysenterStateV45::rip’ may be used uninitialized in this function
  CC [M]  /tmp/vmware-config0/vmmon-only/common/vmciContext.o
  CC [M]  /tmp/vmware-config0/vmmon-only/common/vmciDatagram.o
  CC [M]  /tmp/vmware-config0/vmmon-only/common/vmciDriver.o
  CC [M]  /tmp/vmware-config0/vmmon-only/common/vmciDs.o
  CC [M]  /tmp/vmware-config0/vmmon-only/common/vmciGroup.o
  CC [M]  /tmp/vmware-config0/vmmon-only/common/vmciHashtable.o
  CC [M]  /tmp/vmware-config0/vmmon-only/common/vmciProcess.o
  CC [M]  /tmp/vmware-config0/vmmon-only/common/vmciResource.o
  CC [M]  /tmp/vmware-config0/vmmon-only/common/vmciSharedMem.o
  CC [M]  /tmp/vmware-config0/vmmon-only/common/vmx86.o
In file included from /tmp/vmware-config0/vmmon-only/common/vmx86.c:40:
/tmp/vmware-config0/vmmon-only/./include/x86svm.h:37:1: warning: "MSR_VM_CR" redefined
In file included from /usr/src/linux-headers-2.6.32-5-common/arch/x86/include/asm/msr.h:4,
                 from /usr/src/linux-headers-2.6.32-5-common/arch/x86/include/asm/processor.h:21,
                 from /usr/src/linux-headers-2.6.32-5-common/arch/x86/include/asm/thread_info.h:22,
                 from /usr/src/linux-headers-2.6.32-5-common/include/linux/thread_info.h:56,
                 from /usr/src/linux-headers-2.6.32-5-common/include/linux/preempt.h:9,
                 from /usr/src/linux-headers-2.6.32-5-common/include/linux/spinlock.h:50,
                 from /usr/src/linux-headers-2.6.32-5-common/include/linux/seqlock.h:29,
                 from /usr/src/linux-headers-2.6.32-5-common/include/linux/time.h:8,
                 from /usr/src/linux-headers-2.6.32-5-common/include/linux/timex.h:56,
                 from /usr/src/linux-headers-2.6.32-5-common/include/linux/sched.h:56,
                 from /tmp/vmware-config0/vmmon-only/common/vmx86.c:18:
/usr/src/linux-headers-2.6.32-5-common/arch/x86/include/asm/msr-index.h:396:1: warning: this is the location of the previous definition
In file included from /tmp/vmware-config0/vmmon-only/common/vmx86.c:40:
/tmp/vmware-config0/vmmon-only/./include/x86svm.h:40:1: warning: "MSR_VM_HSAVE_PA" redefined
In file included from /usr/src/linux-headers-2.6.32-5-common/arch/x86/include/asm/msr.h:4,
                 from /usr/src/linux-headers-2.6.32-5-common/arch/x86/include/asm/processor.h:21,
                 from /usr/src/linux-headers-2.6.32-5-common/arch/x86/include/asm/thread_info.h:22,
                 from /usr/src/linux-headers-2.6.32-5-common/include/linux/thread_info.h:56,
                 from /usr/src/linux-headers-2.6.32-5-common/include/linux/preempt.h:9,
                 from /usr/src/linux-headers-2.6.32-5-common/include/linux/spinlock.h:50,
                 from /usr/src/linux-headers-2.6.32-5-common/include/linux/seqlock.h:29,
                 from /usr/src/linux-headers-2.6.32-5-common/include/linux/time.h:8,
                 from /usr/src/linux-headers-2.6.32-5-common/include/linux/timex.h:56,
                 from /usr/src/linux-headers-2.6.32-5-common/include/linux/sched.h:56,
                 from /tmp/vmware-config0/vmmon-only/common/vmx86.c:18:
/usr/src/linux-headers-2.6.32-5-common/arch/x86/include/asm/msr-index.h:398:1: warning: this is the location of the previous definition
  CC [M]  /tmp/vmware-config0/vmmon-only/vmcore/compat.o
  CC [M]  /tmp/vmware-config0/vmmon-only/vmcore/moduleloop.o
  LD [M]  /tmp/vmware-config0/vmmon-only/vmmon.o
  Building modules, stage 2.
  MODPOST 1 modules
WARNING: /tmp/vmware-config0/vmmon-only/vmmon.o (.properties): unexpected non-allocatable section.
Did you forget to use "ax"/"aw" in a .S file?
Note that for example <linux/init.h> contains
section definitions for use in .S files.

WARNING: "init_mm" [/tmp/vmware-config0/vmmon-only/vmmon.ko] undefined!
  CC      /tmp/vmware-config0/vmmon-only/vmmon.mod.o
  LD [M]  /tmp/vmware-config0/vmmon-only/vmmon.ko
make[1]: Leaving directory `/usr/src/linux-headers-2.6.32-5-686'
cp -f vmmon.ko ./../vmmon.o
make: Leaving directory `/tmp/vmware-config0/vmmon-only'
Unable to make a vmmon module that can be loaded in the running kernel:
insmod: error inserting '/tmp/vmware-config0/vmmon.o': -1 Unknown symbol in module
There is probably a slight difference in the kernel configuration between the
set of C header files you specified and your running kernel.  You may want to
rebuild a kernel based on that directory, or specify another directory.

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".

Execution aborted.

ashish_neekhra · 10-21-2011, 07:21 AM

Are you sure you upgraded your system correctly ? I mean check your kernel version & Kernel Headers package.