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!

CenOS 4.2: VMware beim Starten jedesmal nicht konfiguriert

Hilfe bei Problemen mit der Installation oder Benutzung des VMware GSX Server und VMware Server 1.

Moderatoren: Dayworker, irix

Member
Beiträge: 49
Registriert: 20.07.2003, 08:18

CenOS 4.2: VMware beim Starten jedesmal nicht konfiguriert

Beitragvon gbl » 27.10.2005, 19:24

... wil heissen:

nachdem ich vmware-config.pl durchgeführt habe startet der GSX Server korrekt.
Nachdem der HOST jedoch neu gestartet wird, meint der GSX Server, daß er für den Kernel 2.6.9-22.ELsmp nicht korrekt eingerichtet sei und ich vmware-config.pl ausführen soll.

Code: Alles auswählen

[root@mainframe ~]# vmware-config.pl
Making sure services for VMware GSX Server are stopped.

Stopping VMware services:
   Virtual machine monitor                                 [  OK  ]
   Bridged networking on /dev/vmnet0                       [  OK  ]
   DHCP server on /dev/vmnet8                              [  OK  ]
   NAT service on /dev/vmnet8                              [  OK  ]
   Host-only networking on /dev/vmnet8                     [  OK  ]
   Virtual ethernet                                        [  OK  ]

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

None of the pre-built vmmon modules for VMware GSX 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.9-22.ELsmp/build/include]

Extracting the sources of the vmmon module.

Building the vmmon module.

Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config1/vmmon-only'
make -C /lib/modules/2.6.9-22.ELsmp/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/kernels/2.6.9-22.EL-smp-i686'
  CC [M]  /tmp/vmware-config1/vmmon-only/linux/driver.o
  CC [M]  /tmp/vmware-config1/vmmon-only/linux/hostif.o
  CC [M]  /tmp/vmware-config1/vmmon-only/common/cpuid.o
  CC [M]  /tmp/vmware-config1/vmmon-only/common/memtrack.o
  CC [M]  /tmp/vmware-config1/vmmon-only/common/phystrack.o
  CC [M]  /tmp/vmware-config1/vmmon-only/common/task.o
  CC [M]  /tmp/vmware-config1/vmmon-only/common/vmx86.o
  LD [M]  /tmp/vmware-config1/vmmon-only/vmmon.o
  Building modules, stage 2.
  MODPOST
  CC      /tmp/vmware-config1/vmmon-only/vmmon.mod.o
  LD [M]  /tmp/vmware-config1/vmmon-only/vmmon.ko
make[1]: Leaving directory `/usr/src/kernels/2.6.9-22.EL-smp-i686'
cp -f vmmon.ko ./../vmmon.o
make: Leaving directory `/tmp/vmware-config1/vmmon-only'
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.

Extracting the sources of the vmnet module.

Building the vmnet module.

Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config1/vmnet-only'
make -C /lib/modules/2.6.9-22.ELsmp/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/kernels/2.6.9-22.EL-smp-i686'
  CC [M]  /tmp/vmware-config1/vmnet-only/driver.o
  CC [M]  /tmp/vmware-config1/vmnet-only/hub.o
  CC [M]  /tmp/vmware-config1/vmnet-only/userif.o
  CC [M]  /tmp/vmware-config1/vmnet-only/netif.o
  CC [M]  /tmp/vmware-config1/vmnet-only/bridge.o
  CC [M]  /tmp/vmware-config1/vmnet-only/procfs.o
  LD [M]  /tmp/vmware-config1/vmnet-only/vmnet.o
  Building modules, stage 2.
  MODPOST
  CC      /tmp/vmware-config1/vmnet-only/vmnet.mod.o
  LD [M]  /tmp/vmware-config1/vmnet-only/vmnet.ko
make[1]: Leaving directory `/usr/src/kernels/2.6.9-22.EL-smp-i686'
cp -f vmnet.ko ./../vmnet.o
make: Leaving directory `/tmp/vmware-config1/vmnet-only'
The module loads perfectly in the running kernel.

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

This program previously created the file /dev/vmnet8, 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]

   Shutting down http.vmware:                              [  OK  ]
   Starting httpd.vmware:                                  [  OK  ]
Please specify a port for remote console connections to use [902]

xinetd beenden:                                            [  OK  ]
xinetd starten:                                            [  OK  ]
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/vmware/Virtual Machines]

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

Starting VMware services:
   Virtual machine monitor                                 [  OK  ]
   Virtual ethernet                                        [  OK  ]
   Bridged networking on /dev/vmnet0                       [  OK  ]
   Host-only networking on /dev/vmnet8 (background)        [  OK  ]
   NAT service on /dev/vmnet8                              [  OK  ]
   Starting VMware virtual machines...                     [  OK  ]

The configuration of VMware GSX Server 3.1.0 build-9089 for Linux for this
running kernel completed successfully.

[root@mainframe ~]# uname -r
2.6.9-22.ELsmp


Wer weis Rat?

Member
Beiträge: 141
Registriert: 03.02.2005, 19:20
Wohnort: NRW

Beitragvon chexma » 29.10.2005, 21:57

Bei SuSE tritt das Problem auf wenn die Kernel-Sourcen nicht zum laufenden Kernel passen.
Versuch mal folgendes :

cd /usr/src/linux
make cloneconfig
make prepare

Wenn das nicht reicht ist hier noch eine Beschreibung aus dem CentOS Forum wie es auch klappen könnte :

up2date kernel-source
cd /usr/src
ln -s linux-2.6.9-11.EL linux
cd linux
make oldconfig
vi Makefile
^^ edit your EXTRAVERSION and take out the "custom", mine: "EXTRAVERSION = -11.EL"
make -j2 bzImage
vmware-config-tools.pl


Bei dem Softlink mit ln -s... musst du natürlich deine neuen Kernel Sourcen angeben, ich denke mal nicht das das auch 2.6.9.11 sein wird.

mfg

Andre

Member
Beiträge: 49
Registriert: 20.07.2003, 08:18

Beitragvon gbl » 30.10.2005, 08:42

Danke für Deine Antwort.
In meinem Fall war einfach ein Update auf GSX 3.2 nötig. Nun läufts.


Zurück zu „VMserver 1 und GSX“

Wer ist online?

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