VMW 5.5.1 Suse 10.0 wollen nicht

[TPol]

Moin Leutz.

Wenn ich VMWare Workstation 5.5.1 versuche zu konfigurieren (vmware-config.pl) dann kommts ganz am Ende zu folgender Fehlermeldung:


VMware 2 or VMware Express detected, building for VMware 2, VMware Express and VMware Workstation 4.0.x.
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config2/vmnet-only'
make -C /lib/modules/2.6.13-15.7-default/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-2.6.13-15.7-obj/i386/default'
make -C ../../../linux-2.6.13-15.7 O=../linux-2.6.13-15.7-obj/i386/default modules
CC [M] /tmp/vmware-config2/vmnet-only/driver.o
CC [M] /tmp/vmware-config2/vmnet-only/hub.o
CC [M] /tmp/vmware-config2/vmnet-only/userif.o
CC [M] /tmp/vmware-config2/vmnet-only/netif.o
CC [M] /tmp/vmware-config2/vmnet-only/bridge.o
CC [M] /tmp/vmware-config2/vmnet-only/procfs.o
CC [M] /tmp/vmware-config2/vmnet-only/smac_compat.o
CC [M] /tmp/vmware-config2/vmnet-only/smac_linux.x386.o
LD [M] /tmp/vmware-config2/vmnet-only/vmnet.o
Building modules, stage 2.
MODPOST
CC /tmp/vmware-config2/vmnet-only/vmnet.mod.o
LD [M] /tmp/vmware-config2/vmnet-only/vmnet.ko
make[1]: Leaving directory `/usr/src/linux-2.6.13-15.7-obj/i386/default'
cp -f vmnet.ko ./../vmnet.o
make: Leaving directory `/tmp/vmware-config2/vmnet-only'
Unable to make a vmnet module that can be loaded in the running kernel:
insmod: error inserting '/tmp/vmware-config2/vmnet.o': -1 File exists
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.

linux:/home/tpol/vmware-distrib/vmware-any-any-update96/vmware-any-any-update96 #

Wie am Prompt zu erkennen hah ich den neuesten any-any-Patch auch schon (vorm ausführen von vmware-config.pl) eingespielt, ist doesnt work... :(

Woran kann es denn nun liegen? Das make cloneconfig und prepare wurde auch ausgeführt...


EDIT:
Wer kann mir mal verständlich erklären was das heissen soll?

Q: Why does vmware-config.pl report "There is probably a light difference of kernel configuration between the set of C header files you specified and your running kernel"?

A: This error message is displayed when the configuration program successfully builds custom VMware Workstation modules but they are incompatible with your running kernel. This happens when there is a mismatch between your running kernel and the directory of header files. Some distribution vendors ship a directory of header files that exhibits this problem. We encourage them to fix it. In the meantime, please consider recompiling your Linux kernel. This is the only way to ensure that the directory of header files will match your Linux kernel exactly.

Ich hab meinen Kernel noch nie selber kompiliert und habs auch, ehrlich gesagt NICHT vor... Wenn denn doch nötig, wie gehts denn am einfachsten???

[who-is]

Hi,

Q: Why does vmware-config.pl report "There is probably a light difference of kernel configuration between the set of C header files you specified and your running kernel"?

A: This error message is displayed when the configuration program successfully builds custom VMware Workstation modules but they are incompatible with your running kernel. This happens when there is a mismatch between your running kernel and the directory of header files. Some distribution vendors ship a directory of header files that exhibits this problem. We encourage them to fix it. In the meantime, please consider recompiling your Linux kernel. This is the only way to ensure that the directory of header files will match your Linux kernel exactly.

Deine "Header-Files" entsprechen nicht dem laufenden Kernel.

Entweder Du kompilierst den Kernel neu, oder probier folgendes:

cd usr/src/linux (sollten deine Kernelquellen liegen)
make cloneconfig && make prepare-all

vmware-any-any-patch runterladen und entpacken
Quelle:(ftp://platen.vc.cvut.cz/pub/vmware)

in das neue Verzeichnis wechseln

./runme.pl ausführen

Dann vmware-config.pl noch einmal ausführen.

So ging es bei mir.

[TPol]

Du schlägst genau das vor was ich schon längst gemacht hab...
Probiere es aber trotzdem mal aus, denn.
Ich hatte "nur"
make cloneconfig
make prepare
gemacht und nicht prepare-all, vielleicht hilfts ja was...


linux:/home/tpol/vmware-distrib/vmware-any-any-update96/vmware-any-any-update96 # ./runme.pl
Updating /usr/bin/vmware ... No patch needed/available
Updating /usr/bin/vmnet-bridge ... No patch needed/available
Updating /usr/lib/vmware/bin/vmware-vmx ... No patch needed/available
Updating /usr/lib/vmware/bin-debug/vmware-vmx ... No patch needed/available
VMware modules in "/usr/lib/vmware/modules/source" has been updated.

Before running VMware for the first time after update, you need to configure it
for your running kernel by invoking the following command:
"/usr/bin/vmware-config.pl". Do you want this script to invoke the command for
you now? [no]

Vielleicht hilft das ja eher weiter:


Building the vmmon module.

VMware 2 or VMware Express detected, building for VMware 2, VMware Express and VMware Workstation 4.0.x.
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config3/vmmon-only'
make -C /lib/modules/2.6.13-15.7-default/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-2.6.13-15.7-obj/i386/default'
make -C ../../../linux-2.6.13-15.7 O=../linux-2.6.13-15.7-obj/i386/default modules
CC [M] /tmp/vmware-config3/vmmon-only/linux/driver.o
CC [M] /tmp/vmware-config3/vmmon-only/linux/hostif.o
CC [M] /tmp/vmware-config3/vmmon-only/common/cpuid.o
CC [M] /tmp/vmware-config3/vmmon-only/common/hash.o
CC [M] /tmp/vmware-config3/vmmon-only/common/memtrack.o
CC [M] /tmp/vmware-config3/vmmon-only/common/phystrack.o
CC [M] /tmp/vmware-config3/vmmon-only/common/task.o
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for Ada/C/ObjC but not for C++
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++
cc1plus: warning: command line option "-ffreestanding" is valid for C/ObjC but not for C++
include2/asm/bitops.h: In function ‘int find_first_bit(const long unsigned int*, unsigned int)’:
include2/asm/bitops.h:334: warning: comparison between signed and unsigned integer expressions
/tmp/vmware-config3/vmmon-only/common/task_compat.h: In function ‘void Task_Switch_V45(VMDriver*, Vcpuid)’:
/tmp/vmware-config3/vmmon-only/common/task_compat.h:1143: warning: ‘sysenterState$validEIP’ may be used uninitialized in this function
/tmp/vmware-config3/vmmon-only/common/task_compat.h:1143: warning: ‘sysenterState$cs’ may be used uninitialized in this function
/tmp/vmware-config3/vmmon-only/common/task_compat.h:1143: warning: ‘sysenterState$rsp’ may be used uninitialized in this function
/tmp/vmware-config3/vmmon-only/common/task_compat.h:1143: warning: ‘sysenterState$rip’ may be used uninitialized in this function
/tmp/vmware-config3/vmmon-only/common/task_compat.h: In function ‘int Vmx86_RunVM_V4(VMDriver*, Vcpuid) [with VMCP = VMCrossPageV4]’:
/tmp/vmware-config3/vmmon-only/common/task_compat.h:1499: warning: ‘sysenterState$validEIP’ may be used uninitialized in this function
/tmp/vmware-config3/vmmon-only/common/task_compat.h:1499: warning: ‘sysenterState$cs’ may be used uninitialized in this function
/tmp/vmware-config3/vmmon-only/common/task_compat.h:1499: warning: ‘sysenterState$rsp’ may be used uninitialized in this function
/tmp/vmware-config3/vmmon-only/common/task_compat.h:1499: warning: ‘sysenterState$rip’ may be used uninitialized in this function
/tmp/vmware-config3/vmmon-only/common/task_compat.h: In function ‘int Vmx86_RunVM(VMCP*, VMDriver*) [with VMCP = VMCrossPageV321]’:
/tmp/vmware-config3/vmmon-only/common/task_compat.h:1499: warning: ‘sysenterState$validEIP’ may be used uninitialized in this function
/tmp/vmware-config3/vmmon-only/common/task_compat.h:1499: warning: ‘sysenterState$cs’ may be used uninitialized in this function
/tmp/vmware-config3/vmmon-only/common/task_compat.h: In function ‘int Vmx86_RunVM(VMCP*, VMDriver*) [with VMCP = VMCrossPageV32]’:
/tmp/vmware-config3/vmmon-only/common/task_compat.h:1499: warning: ‘sysenterState$validEIP’ may be used uninitialized in this function
/tmp/vmware-config3/vmmon-only/common/task_compat.h:1499: warning: ‘sysenterState$cs’ may be used uninitialized in this function
/tmp/vmware-config3/vmmon-only/common/task_compat.h: In function ‘int Vmx86_RunVM(VMCP*, VMDriver*) [with VMCP = VMCrossPageGSX25]’:
/tmp/vmware-config3/vmmon-only/common/task_compat.h:1499: warning: ‘sysenterState$validEIP’ may be used uninitialized in this function
/tmp/vmware-config3/vmmon-only/common/task_compat.h:1499: warning: ‘sysenterState$cs’ may be used uninitialized in this function
/tmp/vmware-config3/vmmon-only/common/task_compat.h:1499: warning: ‘sysenterState$rsp’ may be used uninitialized in this function
/tmp/vmware-config3/vmmon-only/common/task_compat.h:1499: warning: ‘sysenterState$rip’ may be used uninitialized in this function
/tmp/vmware-config3/vmmon-only/common/task_compat.h: In function ‘int Vmx86_RunVM(VMCP*, VMDriver*) [with VMCP = VMCrossPageGSX2]’:
/tmp/vmware-config3/vmmon-only/common/task_compat.h:1499: warning: ‘sysenterState$validEIP’ may be used uninitialized in this function
/tmp/vmware-config3/vmmon-only/common/task_compat.h:1499: warning: ‘sysenterState$cs’ may be used uninitialized in this function
/tmp/vmware-config3/vmmon-only/common/task_compat.h:1499: warning: ‘sysenterState$rsp’ may be used uninitialized in this function
/tmp/vmware-config3/vmmon-only/common/task_compat.h:1499: warning: ‘sysenterState$rip’ may be used uninitialized in this function
/tmp/vmware-config3/vmmon-only/common/task_compat.h: In function ‘int Vmx86_RunVM(VMDriver*, Vcpuid)’:
/tmp/vmware-config3/vmmon-only/common/task_compat.h:1499: warning: ‘sysenterState$validEIP’ may be used uninitialized in this function
/tmp/vmware-config3/vmmon-only/common/task_compat.h:1499: warning: ‘sysenterState$cs’ may be used uninitialized in this function
/tmp/vmware-config3/vmmon-only/common/task_compat.h:1499: warning: ‘sysenterState$validEIP’ may be used uninitialized in this function
/tmp/vmware-config3/vmmon-only/common/task_compat.h:1499: warning: ‘sysenterState$cs’ may be used uninitialized in this function
/tmp/vmware-config3/vmmon-only/common/task_compat.h:1499: warning: ‘sysenterState$validEIP’ may be used uninitialized in this function
/tmp/vmware-config3/vmmon-only/common/task_compat.h:1499: warning: ‘sysenterState$cs’ may be used uninitialized in this function
CC [M] /tmp/vmware-config3/vmmon-only/common/vmx86.o
CC [M] /tmp/vmware-config3/vmmon-only/vmcore/compat.o
CC [M] /tmp/vmware-config3/vmmon-only/vmcore/moduleloop.o
LD [M] /tmp/vmware-config3/vmmon-only/vmmon.o
Building modules, stage 2.
MODPOST
CC /tmp/vmware-config3/vmmon-only/vmmon.mod.o
LD [M] /tmp/vmware-config3/vmmon-only/vmmon.ko
make[1]: Leaving directory `/usr/src/linux-2.6.13-15.7-obj/i386/default'
cp -f vmmon.ko ./../vmmon.o
make: Leaving directory `/tmp/vmware-config3/vmmon-only'
The module loads perfectly in the running kernel.

Do you want networking for your virtual machines? (yes/no/help) [yes]

Scheint nun aber doch zu klappen:


Starting VMware services:
Virtual machine monitor done
Virtual ethernet done
Bridged networking on /dev/vmnet0 done
Host-only networking on /dev/vmnet1 (background) done
Host-only networking on /dev/vmnet8 (background) done
NAT service on /dev/vmnet8 done

The configuration of VMware Workstation 5.5.1 build-19175 for Linux for this
running kernel completed successfully.

You can now run VMware Workstation by invoking the following command:
"/usr/bin/vmware".

Enjoy,

--the VMware team

linux:/home/tpol/vmware-distrib/vmware-any-any-update96/vmware-any-any-update96 #

DAS PASSIERT WENN ICH NUN EINE VIRTUELLE MASCHINE STARTEN FEHL, ES KOMMT EINE FEHLERMELDUNG:

Version mismatch with vmmon module: expecting 137.0, got 116.0.
You have an incorrect version of the `vmmon' kernel module.
Try reinstalling VMware Workstation.

Des weiteren:
Failed to initialize monitor device.

Dann kommt noch:
Unable to change virtual machine power state: Cannot find a valid peer process to connect to.

Und nur für den Fall dass man noch dem Glauben anheimfallen könnte dass es evtl. doch noch klappen könnte kommt zu guter Letzt:
Failed to reply to the dialog: Pipe: Read failed

Sehr erfreulich dass das installieren und konfigurieren praktisch fehlerlos gelaufen ist und man eine Erfolgsmeldung vom Script bekommt... :(

[who-is]

Hi,

welchen gcc benutzt Du?

[who-is]

Hast Du diese Anleitung genutzt?

http://www.novell.com/coolsolutions/feature/15963.html

[stefan.becker]

Wie am Prompt zu erkennen hah ich den neuesten any-any-Patch auch schon (vorm ausführen von vmware-config.pl) eingespielt, ist doesnt work...

Genau das ist der Fehler. Bei der neuen Version 5.51 ist der Patch nicht erforderlich.

VMWARE komplett löschen, neu installieren, konfigurieren, aber ohne Patch!

[who-is]

Ok, bei mir läuft´s trotz patch!?:confused:

[TPol]

Sorry, mit dem patch war ich wohl zu eifrig...

Es geht! Guter Hinweis stefan.becker ;)

1. cd /usr/src/linux
2. make cloneconfig && make prepare-all
3. cd /XYZ/vmware
4. ./vmware-install.pl

So hab ichs gemacht, wie man sieht diesesmal an 4. nicht abgebrochen und any-any-Patch installiert, ES GEHT... *froi*

Also in Zukunft immer erst ohne Pätsch testen ;)