PDA

Archiv verlassen und diese Seite im Standarddesign anzeigen : VMWare Module in Arch Linux backen



sim4000
18.05.2008, 14:20
Hallo.
Ich bin gerade dabei mir mal Arch Linux einzurichten. Dabei bin ich im Moment bei VMWare stehen geblieben. Und zwar bekomme ich die Module nicht gebacken.

Bei der Installation habe ich mich an folgende Anleitung gehalten:
http://wiki.archlinux.org/index.php/Installing_VMware
Ich habe alles genau so gemacht, wie dort beschrieben. Wenn ich nun vmware-config.pl ausführe, bekomme ich folgenden Output:

<root> (/opt/) vmware-config.pl
Making sure services for VMware Workstation are stopped.

Stopping VMware services:
Virtual machine monitor done

Configuring fallback GTK+ 2.4 libraries.

In which directory do you want to install the theme 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]

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? [/lib/modules/2.6.24-ARCH/build/include]

Extracting the sources of the vmmon module.

Building the vmmon module.

Unknown VMware Workstation 6.0.2 build 59824 detected. Building for Workstation 6.0.0.
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config4/vmmon-only'
make -C /lib/modules/2.6.24-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-2.6.24-ARCH'
CC [M] /tmp/vmware-config4/vmmon-only/linux/driver.o
CC [M] /tmp/vmware-config4/vmmon-only/linux/driverLog.o
CC [M] /tmp/vmware-config4/vmmon-only/linux/hostif.o
CC [M] /tmp/vmware-config4/vmmon-only/common/comport.o
CC [M] /tmp/vmware-config4/vmmon-only/common/cpuid.o
In file included from include/asm/bitops.h:2,
from /tmp/vmware-config4/vmmon-only/./include/vcpuset.h:74,
from /tmp/vmware-config4/vmmon-only/./include/modulecall.h:23,
from /tmp/vmware-config4/vmmon-only/common/vmx86.h:19,
from /tmp/vmware-config4/vmmon-only/common/hostif.h:18,
from /tmp/vmware-config4/vmmon-only/common/cpuid.c:15:
include/asm/bitops_32.h:9:2: error: #error only <linux/bitops.h> can be included directly
make[2]: *** [/tmp/vmware-config4/vmmon-only/common/cpuid.o] Error 1
make[1]: *** [_module_/tmp/vmware-config4/vmmon-only] Error 2
make[1]: Leaving directory `/usr/src/linux-2.6.24-ARCH'
make: *** [vmmon.ko] Error 2
make: Leaving directory `/tmp/vmware-config4/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.Distri: Arch Linux 2008
Kernel: 2.6.24-ARCH
Any-Any-Patch ist installiert.
Header und Sourcen sind installiert.

Woran kann es liegen, das er nicht sauber durchläuft?
Lg, sim.

defcon
18.05.2008, 14:25
Probiers mal mit dem vmware-any-to-any patch.
So hats bei mir funktioniert.

sim4000
18.05.2008, 14:29
Den hab ich bereits installiert.
Sry. hab ich vergessen mit hinzuschreiben.

defcon
18.05.2008, 14:35
Achso, ok.

Mike1
18.05.2008, 14:36
http://communities.vmware.com/docs/DOC-3850


fixing it is quite easy.

1. untar /usr/lib/vmware/modules/source/vmmon.tar in somewhere like /tmp
2. edit vmmon-only/include/vcpuset.h

change line 74 from asm/bitops.h to linux/bitops.h

3. tar cvf vmmon.tar vmmon-only
4. mv /usr/lib/vmware/modules/source/vmmon.tar /usr/lib/vmware/modules/source/vmmon.tar.orig
5. cp vmmon.tar /usr/lib/vmware/modules/source

and try vmware-config.pl again.

It works for me.

sim4000
18.05.2008, 14:55
Ich hab ne Lösung.
Und zwar is wohl so wie es aussieht die any-any-patch version zu alt gewesen.

Vorher: any-any-patch115
Nacher: any-any-patch116

Nach der installation des neueren ging es.
Herzlichen Dank!
Lg, sim.

//edit
Da ist der Patch her: http://www.nabble.com/VMware-server-problems-with-the-new-F8-kernel-td15892089.html
Direktlink: http://blog.creonfx.com/temp/vmware-any-any-update-116.tgz