PDA

Archiv verlassen und diese Seite im Standarddesign anzeigen : Problem mit vmware-config



MiNe
05.11.05, 11:17
Servus,
ich bin gerade dabei Vmware 5 zu installieren.
Während ich vmware-config.pl ausgeführt habe, bekam ich folgende Fehlermeldung:

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

The header files in /usr/include are generally for C libraries, not for the
running kernel. If you do not have kernel header files in your /usr/src
directory, you probably do not have the kernel-source package installed. Are you
sure that /usr/include contains the header files associated with your running
kernel? [no]

What is the location of the directory of C header files that match your running
kernel? [/usr/src/linux/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/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-2.6.13-15'
Makefile:494: .config: Datei oder Verzeichnis nicht gefunden

WARNING: Symbol version dump /usr/src/linux-2.6.13-15/Module.symvers
is missing; modules will have no dependencies and modversions.

CC [M] /tmp/vmware-config0/vmmon-only/linux/driver.o
In file included from /tmp/vmware-config0/vmmon-only/./include/vmware.h:24,
from /tmp/vmware-config0/vmmon-only/linux/driver.c:44:
/tmp/vmware-config0/vmmon-only/./include/vm_basic_defs.h:208:5: warning: "_MSC_VER" is not defined
In file included from /tmp/vmware-config0/vmmon-only/./include/vcpuset.h:56,
from /tmp/vmware-config0/vmmon-only/./include/modulecall.h:23,
from /tmp/vmware-config0/vmmon-only/./common/vmx86.h:18,
from /tmp/vmware-config0/vmmon-only/linux/driver.h:15,
from /tmp/vmware-config0/vmmon-only/linux/driver.c:45:
/tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:54:5: warning: "_MSC_VER" is not defined
In file included from /tmp/vmware-config0/vmmon-only/./include/vm_asm.h:23,
from /tmp/vmware-config0/vmmon-only/linux/driver.c:48:
/tmp/vmware-config0/vmmon-only/./include/vm_basic_asm.h:48:5: warning: "_MSC_VER" is not defined
/bin/sh: scripts/basic/fixdep: Datei oder Verzeichnis nicht gefunden
make[2]: *** [/tmp/vmware-config0/vmmon-only/linux/driver.o] Fehler 1
make[1]: *** [_module_/tmp/vmware-config0/vmmon-only] Fehler 2
make[1]: Leaving directory `/usr/src/linux-2.6.13-15'
make: *** [vmmon.ko] Fehler 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/download/modules/modules.html" and
"http://www.vmware.com/support/reference/linux/prebuilt_modules_linux.html".

Execution aborted.

michi:/home/michael/VMware-workstation-5.0.0-13124-linux/vmware-distrib #
--------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------

Danach hab ich im Threat weiter unten gelesen, dass ich das "any-any Patch" benötige.
Also hab ich mir "vmware-any-any-update94" heruntergeladen und ausgeführt.

--------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------
michi:/home/michael/vmware-any-any-update94/vmware-any-any-update94 # perl 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? [yes] yes

Making sure services for VMware Workstation are stopped.

Stopping VMware services:
Virtual machine monitor done

Configuring fallback GTK+ 2.4 libraries.

***
* Updating MIME database in /usr/share/mime...
***
In which directory do you want to install the mime type icons?
[/usr/share/icons]

What directory contains your desktop menu entry files? These files have a
.desktop file extension. [/usr/share/applications]

In which directory do you want to install the application's icon?
[/usr/share/pixmaps]

Trying to find a suitable vmmon module for your running kernel.

None of the pre-built vmmon modules for VMware Workstation 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] 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]

Extracting the sources of the vmmon module.

Building the vmmon module.

VMware 2 or VMware Express detected, building for VMware 2, VMware Express and VMware Workstation 4.0.x.
*** Your sources installation is broken:
*** /usr/src/linux/include/.. does not contain .config file
*** vmmon/vmnet build may fail, or built vmmon/vmnet may crash.

*** Hit ENTER to continue, or ^C to stop build.

Using standalone build system.
make: Entering directory `/tmp/vmware-config1/vmmon-only'
make[1]: Entering directory `/tmp/vmware-config1/vmmon-only'
make[2]: Entering directory `/tmp/vmware-config1/vmmon-only/driver-2.6.13-15-default'
make[2]: Leaving directory `/tmp/vmware-config1/vmmon-only/driver-2.6.13-15-default'
make[2]: Entering directory `/tmp/vmware-config1/vmmon-only/driver-2.6.13-15-default'
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for Ada/C/ObjC but not for C++
/usr/src/linux/include/asm/bitops.h: In function ‘int find_first_bit(const long unsigned int*, unsigned int)’:
/usr/src/linux/include/asm/bitops.h:334: warning: comparison between signed and unsigned integer expressions
.././common/task_compat.h: In function ‘void Task_Switch_V45(VMDriver*, Vcpuid)’:
.././common/task_compat.h:1143: warning: ‘sysenterState$validEIP’ may be used uninitialized in this function
.././common/task_compat.h:1143: warning: ‘sysenterState$cs’ may be used uninitialized in this function
.././common/task_compat.h:1143: warning: ‘sysenterState$rsp’ may be used uninitialized in this function
.././common/task_compat.h:1143: warning: ‘sysenterState$rip’ may be used uninitialized in this function
.././common/task_compat.h: In function ‘int Vmx86_RunVM_V4(VMDriver*, Vcpuid) [with VMCP = VMCrossPageV4]’:
.././common/task_compat.h:1498: warning: ‘sysenterState$validEIP’ may be used uninitialized in this function
.././common/task_compat.h:1498: warning: ‘sysenterState$cs’ may be used uninitialized in this function
.././common/task_compat.h:1498: warning: ‘sysenterState$rsp’ may be used uninitialized in this function
.././common/task_compat.h:1498: warning: ‘sysenterState$rip’ may be used uninitialized in this function
.././common/task_compat.h: In function ‘int Vmx86_RunVM(VMCP*, VMDriver*) [with VMCP = VMCrossPageV321]’:
.././common/task_compat.h:1498: warning: ‘sysenterState$validEIP’ may be used uninitialized in this function
.././common/task_compat.h:1498: warning: ‘sysenterState$cs’ may be used uninitialized in this function
.././common/task_compat.h: In function ‘int Vmx86_RunVM(VMCP*, VMDriver*) [with VMCP = VMCrossPageV32]’:
.././common/task_compat.h:1498: warning: ‘sysenterState$validEIP’ may be used uninitialized in this function
.././common/task_compat.h:1498: warning: ‘sysenterState$cs’ may be used uninitialized in this function
.././common/task_compat.h: In function ‘int Vmx86_RunVM(VMCP*, VMDriver*) [with VMCP = VMCrossPageGSX25]’:
.././common/task_compat.h:1498: warning: ‘sysenterState$validEIP’ may be used uninitialized in this function
.././common/task_compat.h:1498: warning: ‘sysenterState$cs’ may be used uninitialized in this function
.././common/task_compat.h:1498: warning: ‘sysenterState$rsp’ may be used uninitialized in this function
.././common/task_compat.h:1498: warning: ‘sysenterState$rip’ may be used uninitialized in this function
.././common/task_compat.h: In function ‘int Vmx86_RunVM(VMCP*, VMDriver*) [with VMCP = VMCrossPageGSX2]’:
.././common/task_compat.h:1498: warning: ‘sysenterState$validEIP’ may be used uninitialized in this function
.././common/task_compat.h:1498: warning: ‘sysenterState$cs’ may be used uninitialized in this function
.././common/task_compat.h:1498: warning: ‘sysenterState$rsp’ may be used uninitialized in this function
.././common/task_compat.h:1498: warning: ‘sysenterState$rip’ may be used uninitialized in this function
.././common/task_compat.h: In function ‘int Vmx86_RunVM(VMDriver*, Vcpuid)’:
.././common/task_compat.h:1498: warning: ‘sysenterState$validEIP’ may be used uninitialized in this function
.././common/task_compat.h:1498: warning: ‘sysenterState$cs’ may be used uninitialized in this function
.././common/task_compat.h:1498: warning: ‘sysenterState$validEIP’ may be used uninitialized in this function
.././common/task_compat.h:1498: warning: ‘sysenterState$cs’ may be used uninitialized in this function
.././common/task_compat.h:1498: warning: ‘sysenterState$validEIP’ may be used uninitialized in this function
.././common/task_compat.h:1498: warning: ‘sysenterState$cs’ may be used uninitialized in this function
make[2]: Leaving directory `/tmp/vmware-config1/vmmon-only/driver-2.6.13-15-default'
make[1]: Leaving directory `/tmp/vmware-config1/vmmon-only'
make: Leaving directory `/tmp/vmware-config1/vmmon-only'
Unable to make a vmmon module that can be loaded in the running kernel:
insmod: error inserting '/tmp/vmware-config1/vmmon.o': -1 Invalid module format
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.

michi:/home/michael/vmware-any-any-update94/vmware-any-any-update94 #
--------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------

Dann hab ich unter
http://www.opensuse.org/Setting_up_VMware_on_SUSE_Linux
gelesen, dass ich auch noch das Pecket "kernel-syms" benötige, nur kann ich das Packet mittels yast nicht installieren. Es ist einfach nicht zum Auswählen da.
Mein verwendetes Suse ist version 10.0

MfG,
MiNe

Martin Ament
05.11.05, 11:23
Hi,

hast Du Folgendes von http://www.opensuse.org/Setting_up_VMware_on_SUSE_Linux hier gemacht?


Prepare the Host System for Building Kernel Modules

To make kernel source files usable so that the kernel modules can be compiled, follow these steps.

1. Open a Terminal window

2. Use su to become root

3. Change to /usr/src/linux directory, and run the following command:

make cloneconfig

4. Run the following command:

make modules_prepare



vmware-config.pl beschwert sich nämlich:


*** /usr/src/linux/include/.. does not contain .config file

Also ich hab auch Suse10, und da geht vmware problemlos. Wenn dann ist in Deinem Fall
make cloneconfig
schief gegangen.

Und hier evtl. nachlesen:
http://www.novell.com/coolsolutions/feature/15963.html

MiNe
05.11.05, 11:53
Genau das wars. Vielen dank!

MfG,
MiNe