vmware 6.0 Beta >> on startup fedora core 6 vmnet8 \[FAILED]

[ardainbox]

After i installed vmware than i finished vmware-config.pl correctly. it finished without any problem. but when i restart X. there write:

vmnet8 \[FAILED]

vmnet1 \[FAILED]

configure vmware, it is installed but not configured corectly.. ?? what is that ?

its 2. configure after restart...

\[aataerkil@dhcppc0 ~]$ su

Password:

\[root@dhcppc0 aataerkil]# vmware-config.pl

Making sure services for VMware Workstation are stopped.

Stopping VMware services:

Virtual machine monitor \[ OK ]

Blocking file system: \[ OK ]

Bridged networking on /dev/vmnet0 \[ OK ]

Host network detection \[ OK ]

DHCP server on /dev/vmnet1 \[ OK ]

Host-only networking on /dev/vmnet1 \[ OK ]

DHCP server on /dev/vmnet8 \[ OK ]

NAT service on /dev/vmnet8 \[ OK ]

Host-only networking on /dev/vmnet8 \[ OK ]

Virtual ethernet \[ OK ]

Configuring fallback GTK+ 2.4 libraries.

In which directory do you want to install the theme icons?

What directory contains your desktop menu entry files? These files have a

.desktop file extension.

In which directory do you want to install the application's icon?

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?

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 /lib/modules/2.6.18-1.2798.fc6/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules

make[1]: Entering directory `/usr/src/kernels/2.6.18-1.2798.fc6-i686'

CC /tmp/vmware-config0/vmmon-only/linux/driver.o

CC /tmp/vmware-config0/vmmon-only/linux/hostif.o

CC /tmp/vmware-config0/vmmon-only/common/comport.o

CC /tmp/vmware-config0/vmmon-only/common/cpuid.o

CC /tmp/vmware-config0/vmmon-only/common/crosstalkContext.o

CC /tmp/vmware-config0/vmmon-only/common/crosstalkDatagram.o

CC /tmp/vmware-config0/vmmon-only/common/crosstalkDriver.o

CC /tmp/vmware-config0/vmmon-only/common/crosstalkDs.o

CC /tmp/vmware-config0/vmmon-only/common/crosstalkGroup.o

CC /tmp/vmware-config0/vmmon-only/common/crosstalkHashtable.o

CC /tmp/vmware-config0/vmmon-only/common/crosstalkProcess.o

CC /tmp/vmware-config0/vmmon-only/common/crosstalkResource.o

CC /tmp/vmware-config0/vmmon-only/common/crosstalkSharedMem.o

CC /tmp/vmware-config0/vmmon-only/common/hash.o

CC /tmp/vmware-config0/vmmon-only/common/memtrack.o

CC /tmp/vmware-config0/vmmon-only/common/phystrack.o

CC /tmp/vmware-config0/vmmon-only/common/task.o

CC /tmp/vmware-config0/vmmon-only/common/vmx86.o

CC /tmp/vmware-config0/vmmon-only/vmcore/moduleloop.o

LD /tmp/vmware-config0/vmmon-only/vmmon.o

Building modules, stage 2.

MODPOST

CC /tmp/vmware-config0/vmmon-only/vmmon.mod.o

LD /tmp/vmware-config0/vmmon-only/vmmon.ko

make[1]: Leaving directory `/usr/src/kernels/2.6.18-1.2798.fc6-i686'

cp -f vmmon.ko ./../vmmon.o

make: Leaving directory `/tmp/vmware-config0/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 vmblock module.

Building the vmblock module.

Using 2.6.x kernel build system.

make: Entering directory `/tmp/vmware-config0/vmblock-only'

make -C /lib/modules/2.6.18-1.2798.fc6/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules

make[1]: Entering directory `/usr/src/kernels/2.6.18-1.2798.fc6-i686'

CC /tmp/vmware-config0/vmblock-only/linux/block.o

CC /tmp/vmware-config0/vmblock-only/linux/control.o

CC /tmp/vmware-config0/vmblock-only/linux/dbllnklst.o

CC /tmp/vmware-config0/vmblock-only/linux/dentry.o

CC /tmp/vmware-config0/vmblock-only/linux/file.o

CC /tmp/vmware-config0/vmblock-only/linux/filesystem.o

CC /tmp/vmware-config0/vmblock-only/linux/inode.o

CC /tmp/vmware-config0/vmblock-only/linux/module.o

CC /tmp/vmware-config0/vmblock-only/linux/stubs.o

CC /tmp/vmware-config0/vmblock-only/linux/super.o

LD /tmp/vmware-config0/vmblock-only/vmblock.o

Building modules, stage 2.

MODPOST

CC /tmp/vmware-config0/vmblock-only/vmblock.mod.o

LD /tmp/vmware-config0/vmblock-only/vmblock.ko

make[1]: Leaving directory `/usr/src/kernels/2.6.18-1.2798.fc6-i686'

cp -f vmblock.ko ./../vmblock.o

make: Leaving directory `/tmp/vmware-config0/vmblock-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/vmnet1, 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]

Extracting the sources of the vmnet module.

Building the vmnet module.

Using 2.6.x kernel build system.

make: Entering directory `/tmp/vmware-config0/vmnet-only'

make -C /lib/modules/2.6.18-1.2798.fc6/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules

make[1]: Entering directory `/usr/src/kernels/2.6.18-1.2798.fc6-i686'

CC /tmp/vmware-config0/vmnet-only/driver.o

CC /tmp/vmware-config0/vmnet-only/hub.o

CC /tmp/vmware-config0/vmnet-only/userif.o

CC /tmp/vmware-config0/vmnet-only/netif.o

CC /tmp/vmware-config0/vmnet-only/bridge.o

CC /tmp/vmware-config0/vmnet-only/filter.o

CC /tmp/vmware-config0/vmnet-only/procfs.o

CC /tmp/vmware-config0/vmnet-only/smac_compat.o

SHIPPED /tmp/vmware-config0/vmnet-only/smac_linux.x386.o

LD /tmp/vmware-config0/vmnet-only/vmnet.o

Building modules, stage 2.

MODPOST

WARNING: could not find /tmp/vmware-config0/vmnet-only/.smac_linux.x386.o.cmd for /tmp/vmware-config0/vmnet-only/smac_linux.x386.o

CC /tmp/vmware-config0/vmnet-only/vmnet.mod.o

LD /tmp/vmware-config0/vmnet-only/vmnet.ko

make[1]: Leaving directory `/usr/src/kernels/2.6.18-1.2798.fc6-i686'

cp -f vmnet.ko ./../vmnet.o

make: Leaving directory `/tmp/vmware-config0/vmnet-only'

The module loads perfectly in the running kernel.

Do you want to install the Eclipse Integrated Virtual Debugger? You must have

the Eclipse IDE installed. \[no]

Starting VMware services:

Virtual machine monitor \[ OK ]

Blocking file system: \[ OK ]

Virtual ethernet \[ OK ]

Bridged networking on /dev/vmnet0 \[ OK ]

Host network detection \[ OK ]

Host-only networking on /dev/vmnet1 (background) \[ OK ]

DHCP server on /dev/vmnet1 \[ OK ]

Host-only networking on /dev/vmnet8 (background) \[ OK ]

DHCP server on /dev/vmnet8 \[ OK ]

NAT service on /dev/vmnet8 \[ OK ]

The configuration of VMware Workstation e.x.p build-39849 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

\[root@dhcppc0 aataerkil]#

Message was edited by:

ardainbox

Message was edited by:

ardainbox

[ardainbox]

\[aataerkil@localhost ~]$ rpm -qa --queryformat %\{NAME}-%\{VERSION}-%\{ARCH}
n | grep kernel | sort

kernel-2.6.18-i686

kernel-devel-2.6.18-i686

kernel-headers-2.6.18-i386

kernel-xen-2.6.18-i686

[ardainbox]

can i run vmvare 6 on my Asus notbook and Fedora Core 6 system ?

is it just config error?

\[aataerkil@dhcppc0 ~]$ rpm -qa --queryformat %\{NAME}-%\{VERSION}-%\{ARCH}
n | grep kernel | sort

kernel-2.6.18-i686

kernel-2.6.19-i686

kernel-devel-2.6.18-i686

kernel-devel-2.6.19-i686

kernel-headers-2.6.19-i386

kernel-xen-2.6.18-i686

\----

---

i onfigured it again:

\[aataerkil@dhcppc0 ~]$ su

Password:

\[root@dhcppc0 aataerkil]# vmware-config.pl

Making sure services for VMware Workstation are stopped.

Stopping VMware services:

Virtual machine monitor \[ OK ]

Blocking file system: \[ OK ]

Bridged networking on /dev/vmnet0 \[ OK ]

Host network detection \[ OK ]

DHCP server on /dev/vmnet1 \[ OK ]

Host-only networking on /dev/vmnet1 \[ OK ]

DHCP server on /dev/vmnet8 \[ OK ]

NAT service on /dev/vmnet8 \[ OK ]

Host-only networking on /dev/vmnet8 \[ OK ]

Virtual ethernet \[ OK ]

Configuring fallback GTK+ 2.4 libraries.

In which directory do you want to install the theme icons?

What directory contains your desktop menu entry files? These files have a

.desktop file extension.

In which directory do you want to install the application's icon?

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?

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 /lib/modules/2.6.19-1.2895.fc6/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules

make[1]: Entering directory `/usr/src/kernels/2.6.19-1.2895.fc6-i686'

CC /tmp/vmware-config0/vmmon-only/linux/driver.o

CC /tmp/vmware-config0/vmmon-only/linux/hostif.o

CC /tmp/vmware-config0/vmmon-only/common/comport.o

CC /tmp/vmware-config0/vmmon-only/common/cpuid.o

CC /tmp/vmware-config0/vmmon-only/common/crosstalkContext.o

CC /tmp/vmware-config0/vmmon-only/common/crosstalkDatagram.o

CC /tmp/vmware-config0/vmmon-only/common/crosstalkDriver.o

CC /tmp/vmware-config0/vmmon-only/common/crosstalkDs.o

CC /tmp/vmware-config0/vmmon-only/common/crosstalkGroup.o

CC /tmp/vmware-config0/vmmon-only/common/crosstalkHashtable.o

CC /tmp/vmware-config0/vmmon-only/common/crosstalkProcess.o

CC /tmp/vmware-config0/vmmon-only/common/crosstalkResource.o

CC /tmp/vmware-config0/vmmon-only/common/crosstalkSharedMem.o

CC /tmp/vmware-config0/vmmon-only/common/hash.o

CC /tmp/vmware-config0/vmmon-only/common/memtrack.o

CC /tmp/vmware-config0/vmmon-only/common/phystrack.o

CC /tmp/vmware-config0/vmmon-only/common/task.o

CC /tmp/vmware-config0/vmmon-only/common/vmx86.o

CC /tmp/vmware-config0/vmmon-only/vmcore/moduleloop.o

LD /tmp/vmware-config0/vmmon-only/vmmon.o

Building modules, stage 2.

MODPOST 1 modules

CC /tmp/vmware-config0/vmmon-only/vmmon.mod.o

LD /tmp/vmware-config0/vmmon-only/vmmon.ko

make[1]: Leaving directory `/usr/src/kernels/2.6.19-1.2895.fc6-i686'

cp -f vmmon.ko ./../vmmon.o

make: Leaving directory `/tmp/vmware-config0/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 vmblock module.

Building the vmblock module.

Using 2.6.x kernel build system.

make: Entering directory `/tmp/vmware-config0/vmblock-only'

make -C /lib/modules/2.6.19-1.2895.fc6/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules

make[1]: Entering directory `/usr/src/kernels/2.6.19-1.2895.fc6-i686'

CC /tmp/vmware-config0/vmblock-only/linux/block.o

CC /tmp/vmware-config0/vmblock-only/linux/control.o

CC /tmp/vmware-config0/vmblock-only/linux/dbllnklst.o

CC /tmp/vmware-config0/vmblock-only/linux/dentry.o

CC /tmp/vmware-config0/vmblock-only/linux/file.o

CC /tmp/vmware-config0/vmblock-only/linux/filesystem.o

CC /tmp/vmware-config0/vmblock-only/linux/inode.o

CC /tmp/vmware-config0/vmblock-only/linux/module.o

CC /tmp/vmware-config0/vmblock-only/linux/stubs.o

CC /tmp/vmware-config0/vmblock-only/linux/super.o

LD /tmp/vmware-config0/vmblock-only/vmblock.o

Building modules, stage 2.

MODPOST 1 modules

CC /tmp/vmware-config0/vmblock-only/vmblock.mod.o

LD /tmp/vmware-config0/vmblock-only/vmblock.ko

make[1]: Leaving directory `/usr/src/kernels/2.6.19-1.2895.fc6-i686'

cp -f vmblock.ko ./../vmblock.o

make: Leaving directory `/tmp/vmware-config0/vmblock-only'

The module loads perfectly in the running kernel.

You have already setup networking.

Would you like to skip networking setup and keep your old settings as they are?

(yes/no) \[no]

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

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/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) \[editor]

The following virtual networks have been defined:

. vmnet0 is bridged to eth0

. vmnet1 is a host-only network on private subnet 172.16.199.0.

. vmnet8 is a NAT network on private subnet 172.16.243.0.

Do you wish to make any changes to the current virtual networks settings?

(yes/no) \[no]

Extracting the sources of the vmnet module.

Building the vmnet module.

Using 2.6.x kernel build system.

make: Entering directory `/tmp/vmware-config0/vmnet-only'

make -C /lib/modules/2.6.19-1.2895.fc6/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules

make[1]: Entering directory `/usr/src/kernels/2.6.19-1.2895.fc6-i686'

CC /tmp/vmware-config0/vmnet-only/driver.o

CC /tmp/vmware-config0/vmnet-only/hub.o

CC /tmp/vmware-config0/vmnet-only/userif.o

CC /tmp/vmware-config0/vmnet-only/netif.o

CC /tmp/vmware-config0/vmnet-only/bridge.o

CC /tmp/vmware-config0/vmnet-only/filter.o

CC /tmp/vmware-config0/vmnet-only/procfs.o

CC /tmp/vmware-config0/vmnet-only/smac_compat.o

SHIPPED /tmp/vmware-config0/vmnet-only/smac_linux.x386.o

LD /tmp/vmware-config0/vmnet-only/vmnet.o

Building modules, stage 2.

MODPOST 1 modules

WARNING: could not find /tmp/vmware-config0/vmnet-only/.smac_linux.x386.o.cmd for /tmp/vmware-config0/vmnet-only/smac_linux.x386.o

CC /tmp/vmware-config0/vmnet-only/vmnet.mod.o

LD /tmp/vmware-config0/vmnet-only/vmnet.ko

make[1]: Leaving directory `/usr/src/kernels/2.6.19-1.2895.fc6-i686'

cp -f vmnet.ko ./../vmnet.o

make: Leaving directory `/tmp/vmware-config0/vmnet-only'

The module loads perfectly in the running kernel.

Do you want to install the Eclipse Integrated Virtual Debugger? You must have

the Eclipse IDE installed. \[no]

Starting VMware services:

Virtual machine monitor \[ OK ]

Blocking file system: \[ OK ]

Virtual ethernet \[ OK ]

Bridged networking on /dev/vmnet0 \[ OK ]

Host network detection \[ OK ]

Host-only networking on /dev/vmnet1 (background) \[ OK ]

DHCP server on /dev/vmnet1 \[ OK ]

Host-only networking on /dev/vmnet8 (background) \[ OK ]

DHCP server on /dev/vmnet8 \[ OK ]

NAT service on /dev/vmnet8 \[ OK ]

The configuration of VMware Workstation e.x.p build-39849 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

\[root@dhcppc0 aataerkil]#

than restart and same..

NAT error

Message was edited by:

ardainbox

[ardainbox]

nobody any idea about that? wy vmnat8 faild?

[peter39]

I have same problems:

on Fedora 6 kernel 2.6.19.2911 && vmware6 beta, at the restart of the system virtual machine can't block filesystem (Blocking filesystem failed)

Also the application panel on the desktop is blocked when virtual machine is on.

[RDPetruska]

You will get much better responses to your questions about Workstation 6 beta in the Workstation 6 beta forum http://www.vmware.com/community/forum.jspa?forumID=372