Diese Website existiert nur weil wir Werbung mit AdSense ausliefern.
Bitte den AdBlocker daher auf dieser Website ausschalten! Danke.

/dev/vmnet3 nach Neustart weg

Alles rund um die Systemverwaltung, die Administration und Konfiguration Eures Linuxsystems

Moderator: Moderatoren

Antworten
Fried_Chicken
Newbie
Newbie
Beiträge: 33
Registriert: 20. Mär 2006, 18:57

/dev/vmnet3 nach Neustart weg

Beitrag von Fried_Chicken » 12. Nov 2006, 12:17

Hallo!

Ich habe in meiner VMware 2 PC die über /dev/vmnet2 miteinander sprechen und 2 PC's die über /dev/vmnet3 reden.

Habe Suse 10.1 und VMware 5.5. Und die VMware läuft mit obiger Konfig bestens... jedoch das Problem ist, wenn ich den Host-PC neu starte, sind alle /dev/vmnet*, bis auf /dev/vmnet2 entfernt worden.
Ich lasse dann jeweils die vmware-config.pl neu durchlaufen und dann sind die /dev/vmnets alle wieder da und ich kann die Gast-PC's auf vmnet3 laufen lassen.


Wenn ich vmware-config.pl nach jedem Neustart des Host-PC's laufen lasse, sieht es so aus:

Code: Alles auswählen

vmware-config.pl
Making sure services for VMware Workstation are stopped.

Stopping VMware services:
   Virtual machine monitor                                             done
   Bridged networking on /dev/vmnet0                                   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 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.16.21-0.25-smp/build/include]

Extracting the sources of the vmmon module.

Building the vmmon module.

Building for VMware Workstation 5.5.0 or 5.5.1.
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config1/vmmon-only'
make -C /lib/modules/2.6.16.21-0.25-smp/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-2.6.16.21-0.25-obj/x86_64/smp'
make -C ../../../linux-2.6.16.21-0.25 O=../linux-2.6.16.21-0.25-obj/x86_64/smp modules
  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/hash.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
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++
/tmp/vmware-config1/vmmon-only/common/task_compat.h: In function ‘void Task_Switch_V45(VMDriver*, Vcpuid)’:
/tmp/vmware-config1/vmmon-only/common/task_compat.h:1713: warning: ‘sysenterState$validEIP’ may be used uninitialized in this function
/tmp/vmware-config1/vmmon-only/common/task_compat.h:1713: warning: ‘sysenterState$cs’ may be used uninitialized in this function
/tmp/vmware-config1/vmmon-only/common/task_compat.h:1713: warning: ‘sysenterState$rsp’ may be used uninitialized in this function
/tmp/vmware-config1/vmmon-only/common/task_compat.h:1713: warning: ‘sysenterState$rip’ may be used uninitialized in this function
  CC [M]  /tmp/vmware-config1/vmmon-only/common/vmx86.o
  CC [M]  /tmp/vmware-config1/vmmon-only/vmcore/compat.o
  CC [M]  /tmp/vmware-config1/vmmon-only/vmcore/moduleloop.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/linux-2.6.16.21-0.25-obj/x86_64/smp'
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.

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] no

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

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

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

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

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

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

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

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

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

Would you prefer to modify your existing networking configuration using the
wizard or the editor? (wizard/editor/help) [wizard]

The following bridged networks have been defined:

All your ethernet interfaces are already bridged.

Do you want to be able to use NAT networking in your virtual machines? (yes/no)
[yes] no

Do you want to be able to use host-only networking in your virtual machines?
[no]

Extracting the sources of the vmnet module.

Building the vmnet module.

Building for VMware Workstation 5.5.0 or 5.5.1.
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config1/vmnet-only'
make -C /lib/modules/2.6.16.21-0.25-smp/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-2.6.16.21-0.25-obj/x86_64/smp'
make -C ../../../linux-2.6.16.21-0.25 O=../linux-2.6.16.21-0.25-obj/x86_64/smp modules
  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
  CC [M]  /tmp/vmware-config1/vmnet-only/smac_compat.o
  CC [M]  /tmp/vmware-config1/vmnet-only/smac_linux.x86_64.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/linux-2.6.16.21-0.25-obj/x86_64/smp'
cp -f vmnet.ko ./../vmnet.o
make: Leaving directory `/tmp/vmware-config1/vmnet-only'
The module loads perfectly in the running kernel.

Starting VMware services:
   Virtual machine monitor                                             done
   Virtual ethernet                                                    done
   Bridged networking on /dev/vmnet0                                   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


Danke!!

Werbung:
rob40
Member
Member
Beiträge: 59
Registriert: 15. Aug 2005, 12:34
Wohnort: Rheinland

Beitrag von rob40 » 14. Nov 2006, 14:38


Antworten

Wer ist online?

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