Die Foren-SW läuft ohne erkennbare Probleme. Sollte doch etwas nicht funktionieren, bitte gerne hier jederzeit melden und wir kümmern uns zeitnah darum. Danke!

Kernel 2.6.20 VMware?

Hilfe bei Problemen mit der Installation und Benutzung der VMware Workstation und VMware Workstation Pro.

Moderatoren: Dayworker, irix

Guru
Beiträge: 3114
Registriert: 27.12.2004, 22:17

Kernel 2.6.20 VMware?

Beitragvon rprengel » 25.01.2007, 09:06

Hallo,

hat jemand schon diese Kombination laufen.
Mein letzter Stand ist "geht noch nicht".

Gruß

Member
Beiträge: 38
Registriert: 12.05.2005, 22:21
Wohnort: Berlin

Beitragvon Christoph Schnauß » 05.02.2007, 19:47

Was genau meinst du? Ich bae auf einem WindowXP-Host Gentoo als virtuelle Maschine laufen, und diesem Guest natürlich einen Kernel 2.6.20 spendiert. Da gibt es absolut keine Probleme.
Umgekehrt auch nicht: wenn ich Gentoo (mit einem 2.6.20er Kernel) als Host nehme, läßt sich VMwar Workstation 5.5.3 problemlos installieren, und man kann beispielsweise WinVista als Guest einrichten.

Wo also liegt dein Problem?

Benutzeravatar
Moderator
Beiträge: 1599
Registriert: 16.10.2002, 20:13
Wohnort: Köln

Beitragvon minimike » 05.02.2007, 20:54

läuft mit 2.6.20-rc6-ck1

Ich habe grosses Interesse an Ecrypt und EXT4. Dazu einige neue Verschlüsselungstechnologieen.

Dazu einige bessere Treiber

Du brauchst den vmware-any-any-update Patch

Guru
Beiträge: 3114
Registriert: 27.12.2004, 22:17

Beitragvon rprengel » 06.02.2007, 07:53

Christoph Schnauß hat geschrieben:Was genau meinst du? Ich bae auf einem WindowXP-Host Gentoo als virtuelle Maschine laufen, und diesem Guest natürlich einen Kernel 2.6.20 spendiert. Da gibt es absolut keine Probleme.
Umgekehrt auch nicht: wenn ich Gentoo (mit einem 2.6.20er Kernel) als Host nehme, läßt sich VMwar Workstation 5.5.3 problemlos installieren, und man kann beispielsweise WinVista als Guest einrichten.

Wo also liegt dein Problem?


Ich hatte erst komische Nebeneffekte die jetzt aber verschwunden sind nachdem ich den Kernel noch mal neu installiert habe.
Die Beta Worstation 6 jetzt bekomme ich mit dem any-any-patch nicht an den Start.
FM patch unterstützt nur Version 2 und 3 .

Gruß

Benutzeravatar
Moderator
Beiträge: 1599
Registriert: 16.10.2002, 20:13
Wohnort: Köln

Beitragvon minimike » 06.02.2007, 16:04

Beim bauen etwas gemeckert aber sonst läuft es stabiel denn wenn nicht gibt es Backups 8)

Code: Alles auswählen

nerd:/usr/src/vmware-any-any-update106# ./runme.pl
Updating /usr/bin/vmware-config.pl ... already patched
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]

Making sure services for VMware Server are stopped.

At least one instance of VMware Server is still running.

Do you want to force a shutdown on the running VMs? [no] yes

Stopping VMware virtual machines...
Stopping VMware services:
   Virtual machine monitor                                             done
   Bridged networking on /dev/vmnet0                                   done
   DHCP server on /dev/vmnet1                                          done
   Host-only networking on /dev/vmnet1                                 done
   DHCP server on /dev/vmnet8                                          done
   NAT service on /dev/vmnet8                                          done
   Host-only networking on /dev/vmnet8                                 done
   Virtual ethernet                                                    done

Configuring fallback GTK+ 2.4 libraries.

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 Server 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.20-rc6-ck1-686/build/include]

Extracting the sources of the vmmon module.

Building the vmmon module.

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.20-rc6-ck1-686/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.20-rc6-ck1-686'
  CC [M]  /tmp/vmware-config0/vmmon-only/linux/driver.o
  CC [M]  /tmp/vmware-config0/vmmon-only/linux/hostif.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 "-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++
/tmp/vmware-config0/vmmon-only/common/task_compat.h: In function 'int Vmx86_RunVM(VMCrossPage*, VMDriver*) [with VMCrossPage = VMCrossPageV321]':
/tmp/vmware-config0/vmmon-only/common/task_compat.h:1522: warning: 'sysenterState$rsp' is used uninitialized in this function
/tmp/vmware-config0/vmmon-only/common/task_compat.h:1523: warning: 'sysenterState$rip' is used uninitialized in this function
/tmp/vmware-config0/vmmon-only/common/task_compat.h:2073: warning: 'sysenterState$validEIP' may be used uninitialized in this function
/tmp/vmware-config0/vmmon-only/common/task_compat.h:2073: warning: 'sysenterState$cs' may be used uninitialized in this function
/tmp/vmware-config0/vmmon-only/common/task_compat.h: In function 'int Vmx86_RunVM(VMCrossPage*, VMDriver*) [with VMCrossPage = VMCrossPageV3]':
/tmp/vmware-config0/vmmon-only/common/task_compat.h:1522: warning: 'sysenterState$rsp' is used uninitialized in this function
/tmp/vmware-config0/vmmon-only/common/task_compat.h:1523: warning: 'sysenterState$rip' is used uninitialized in this function
/tmp/vmware-config0/vmmon-only/common/task_compat.h:2073: warning: 'sysenterState$validEIP' may be used uninitialized in this function
/tmp/vmware-config0/vmmon-only/common/task_compat.h:2073: warning: 'sysenterState$cs' may be used uninitialized in this function
/tmp/vmware-config0/vmmon-only/common/task_compat.h: In function 'int Vmx86_RunVM(VMCrossPage*, VMDriver*) [with VMCrossPage = VMCrossPageGSX1]':
/tmp/vmware-config0/vmmon-only/common/task_compat.h:1522: warning: 'sysenterState$rsp' is used uninitialized in this function
/tmp/vmware-config0/vmmon-only/common/task_compat.h:1523: warning: 'sysenterState$rip' is used uninitialized in this function
/tmp/vmware-config0/vmmon-only/common/task_compat.h:2073: warning: 'sysenterState$validEIP' may be used uninitialized in this function
/tmp/vmware-config0/vmmon-only/common/task_compat.h:2073: warning: 'sysenterState$cs' may be used uninitialized in this function
/tmp/vmware-config0/vmmon-only/common/task_compat.h: In function 'int Vmx86_RunVM(VMCrossPage*, VMDriver*) [with VMCrossPage = VMCrossPageV2]':
/tmp/vmware-config0/vmmon-only/common/task_compat.h:1522: warning: 'sysenterState$rsp' is used uninitialized in this function
/tmp/vmware-config0/vmmon-only/common/task_compat.h:1523: warning: 'sysenterState$rip' is used uninitialized in this function
/tmp/vmware-config0/vmmon-only/common/task_compat.h:2073: warning: 'sysenterState$validEIP' may be used uninitialized in this function
/tmp/vmware-config0/vmmon-only/common/task_compat.h:2073: warning: 'sysenterState$cs' may be used uninitialized in this function
/tmp/vmware-config0/vmmon-only/common/task_compat.h: In function 'int Vmx86_RunVM_V4(VMDriver*, Vcpuid) [with VMCrossPage = VMCrossPageV4]':
/tmp/vmware-config0/vmmon-only/common/task_compat.h:2073: warning: 'sysenterState$validEIP' may be used uninitialized in this function
/tmp/vmware-config0/vmmon-only/common/task_compat.h:2073: warning: 'sysenterState$cs' may be used uninitialized in this function
/tmp/vmware-config0/vmmon-only/common/task_compat.h:2073: warning: 'sysenterState$rsp' may be used uninitialized in this function
/tmp/vmware-config0/vmmon-only/common/task_compat.h:2073: warning: 'sysenterState$rip' may be used uninitialized in this function
/tmp/vmware-config0/vmmon-only/common/task_compat.h: In function 'int Vmx86_RunVM(VMDriver*, Vcpuid)':
/tmp/vmware-config0/vmmon-only/common/task_compat.h:1522: warning: 'sysenterState$rsp' is used uninitialized in this function
/tmp/vmware-config0/vmmon-only/common/task_compat.h:1523: warning: 'sysenterState$rip' is used uninitialized in this function
/tmp/vmware-config0/vmmon-only/common/task_compat.h:2073: warning: 'sysenterState$validEIP' may be used uninitialized in this function
/tmp/vmware-config0/vmmon-only/common/task_compat.h:2073: warning: 'sysenterState$cs' may be used uninitialized in this function
/tmp/vmware-config0/vmmon-only/common/task_compat.h:2073: warning: 'sysenterState$validEIP' may be used uninitialized in this function
/tmp/vmware-config0/vmmon-only/common/task_compat.h:2073: warning: 'sysenterState$cs' may be used uninitialized in this function
/tmp/vmware-config0/vmmon-only/common/task_compat.h:2073: warning: 'sysenterState$rsp' may be used uninitialized in this function
/tmp/vmware-config0/vmmon-only/common/task_compat.h:2073: warning: 'sysenterState$rip' may be used uninitialized in this function
/tmp/vmware-config0/vmmon-only/common/task_compat.h:2073: warning: 'sysenterState$validEIP' may be used uninitialized in this function
/tmp/vmware-config0/vmmon-only/common/task_compat.h:2073: warning: 'sysenterState$cs' may be used uninitialized in this function
/tmp/vmware-config0/vmmon-only/common/task_compat.h:2073: warning: 'sysenterState$rsp' may be used uninitialized in this function
/tmp/vmware-config0/vmmon-only/common/task_compat.h:2073: warning: 'sysenterState$rip' may be used uninitialized in this function
/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:1713: warning: 'sysenterState$validEIP' may be used uninitialized in this function
/tmp/vmware-config0/vmmon-only/common/task_compat.h:1713: warning: 'sysenterState$cs' may be used uninitialized in this function
/tmp/vmware-config0/vmmon-only/common/task_compat.h:1713: warning: 'sysenterState$rsp' may be used uninitialized in this function
/tmp/vmware-config0/vmmon-only/common/task_compat.h:1713: warning: 'sysenterState$rip' may be used uninitialized in this function
  CC [M]  /tmp/vmware-config0/vmmon-only/common/vmx86.o
  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
  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.20-rc6-ck1-686'
cp -f vmmon.ko ./../vmmon.o
make: Leaving directory `/tmp/vmware-config0/vmmon-only'
This program previously created the file
/lib/modules/2.6.20-rc6-ck1-686/misc/vmmon.o, and was about to remove it.
Somebody else apparently did it already.

This program previously created the file
/lib/modules/2.6.20-rc6-ck1-686/misc/vmmon.ko, and was about to remove it.
Somebody else apparently did it already.

The module loads perfectly in the running kernel.

This program previously created the file /dev/vmmon, and was about to remove
it.  Somebody else apparently did it already.

This program previously created the file /dev/parport0, and was about to remove
it.  Somebody else apparently did it already.

This program previously created the file /dev/parport1, and was about to remove
it.  Somebody else apparently did it already.

This program previously created the file /dev/parport2, and was about to remove
it.  Somebody else apparently did it already.

This program previously created the file /dev/parport3, and was about to remove
it.  Somebody else apparently did it already.

You have already setup networking.

Would you like to skip networking setup and keep your old settings as they are?
(yes/no) [yes]

Extracting the sources of the vmnet module.

Building the vmnet module.

Building for VMware Server 1.0.0.
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config0/vmnet-only'
make -C /lib/modules/2.6.20-rc6-ck1-686/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.20-rc6-ck1-686'
  CC [M]  /tmp/vmware-config0/vmnet-only/driver.o
  CC [M]  /tmp/vmware-config0/vmnet-only/hub.o
  CC [M]  /tmp/vmware-config0/vmnet-only/userif.o
  CC [M]  /tmp/vmware-config0/vmnet-only/netif.o
  CC [M]  /tmp/vmware-config0/vmnet-only/bridge.o
  CC [M]  /tmp/vmware-config0/vmnet-only/procfs.o
  CC [M]  /tmp/vmware-config0/vmnet-only/smac_compat.o
  CC [M]  /tmp/vmware-config0/vmnet-only/smac_linux.x386.o
  LD [M]  /tmp/vmware-config0/vmnet-only/vmnet.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /tmp/vmware-config0/vmnet-only/vmnet.mod.o
  LD [M]  /tmp/vmware-config0/vmnet-only/vmnet.ko
make[1]: Leaving directory `/usr/src/linux-headers-2.6.20-rc6-ck1-686'
cp -f vmnet.ko ./../vmnet.o
make: Leaving directory `/tmp/vmware-config0/vmnet-only'
This program previously created the file
/lib/modules/2.6.20-rc6-ck1-686/misc/vmnet.o, and was about to remove it.
Somebody else apparently did it already.

This program previously created the file
/lib/modules/2.6.20-rc6-ck1-686/misc/vmnet.ko, and was about to remove it.
Somebody else apparently did it already.

The module loads perfectly in the running kernel.

Please specify a port for remote console connections to use [902]

You already have an entry for "/usr/sbin/vmware-authd" in the "/etc/inetd.conf"
file.  No change will be made to it.

Hit enter to continue.

Configuring the VMware VmPerl Scripting API.

Building the VMware VmPerl Scripting API.

Using compiler "/usr/bin/gcc". Use environment variable CC to override.

Installing the VMware VmPerl Scripting API.

The installation of the VMware VmPerl Scripting API succeeded.

Do you want this program to set up permissions for your registered virtual
machines?  This will be done by setting new permissions on all files found in
the "/etc/vmware/vm-list" file. [no]

Generating SSL Server Certificate

In which directory do you want to keep your virtual machine files?
[/var/lib/vm]

Do you want to enter a serial number now? (yes/no/help) [no]

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
   Starting VMware virtual machines...                                 done

The configuration of VMware Server 1.0.1 build-29996 for Linux for this running
kernel completed successfully.

nerd:/usr/src/vmware-any-any-update106#

Benutzeravatar
Moderator
Beiträge: 1599
Registriert: 16.10.2002, 20:13
Wohnort: Köln

Beitragvon minimike » 08.02.2007, 13:26

rprengel hast du Paravirtualisation an?

Mit der Option konnte ich keine Treiber kompelieren die nicht mit der GPL kompform sind. Linus hat die Kernel Taliban ordentlich zurückgepfiffen, allerdings wurden wohl nicht alle Fallstricke von den besonders Gläubigen geortet :/


Zurück zu „VMware Workstation und VMware Workstation Pro“

Wer ist online?

Mitglieder in diesem Forum: 0 Mitglieder und 4 Gäste