VMware Communities
clive_long
Contributor
Contributor
‎10-16-2007 04:26 PM

VM WS 6.0 Linux FC7, kernel 2.6.21. Lost vmnet wireless network

Hi,

I was running Linux Fedora 5 successfully as VM WS 6.0 host with a VM guest of Win XP SP2. I had to upgrade Linux to Fedora 7 because of Gnome issues.

The laptop has a built in ethernet card (eth0) and a Netgear MA401 PCMCIA wireless network card (eth1)

After running vmware-config.pl under Fedora 7 I successfully ran Win XP SP2 guest and connected to network over eth1/vmnet1, the wireless card (the ethernet cable was disconnected at this time).

Later I was trying and failing to use a ZyDAS USB 2.0 WLAN card . So I decided to fall back to the original config of eth0=vmnet0=onboard ethernet cabled, eth1=vmnet1=wireless LAN card. I cannot get this configuration to work over the wireless card. The Win XP guest does connect to the network when the ethernet cable eth0 is plugged in. When the wireless card is in, it searches for an ethernet address, fails, times out and is assigned a local network address. I cannot connect the Win XP guest to the network when only the wireless card is connected.

The Win XP virtual machine is configured to map vmnet0 as "Bridged" and vmnet1 as "custom".

The Linux Fedora 7 host can connect to the network over either ethernet cable or wireless card.

See messages from running vmware-config.pl below

So how can I get the Win XP guest to run over the wireless card?

Thanks

<<<<< >>>>>>

# cd /usr/lib

# ifconfig eth0

eth0 Link encap:Ethernet HWaddr 00:90:F5:29:27:FC

BROADCAST MULTICAST MTU:1500 Metric:1

RX packets:0 errors:0 dropped:0 overruns:0 frame:0

TX packets:0 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

Interrupt:11

# ifconfig eth1

eth1 Link encap:Ethernet HWaddr 00:09:5B:54:7D:44

inet addr:192.168.1.65 Bcast:192.168.1.255 Mask:255.255.255.0

inet6 addr: fe80::209:5bff:fe54:7d44/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

RX packets:154 errors:0 dropped:0 overruns:0 frame:0

TX packets:177 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:52326 (51.0 KiB) TX bytes:28811 (28.1 KiB)

Interrupt:4 Base address:0x100

# vmware-config.pl

Making sure services for VMware Workstation are stopped.

Stopping VMware services:

Virtual machine monitor

Blocking file system:

Bridged networking on /dev/vmnet0

Host network detection

DHCP server on /dev/vmnet1

Host-only networking on /dev/vmnet1

Bridged networking on /dev/vmnet2

DHCP server on /dev/vmnet8

NAT service on /dev/vmnet8

Host-only networking on /dev/vmnet8

Virtual ethernet

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)?

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-config2/vmmon-only'

make -C /lib/modules/2.6.21-1.3194.fc7/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules

make[1]: Entering directory `/usr/src/kernels/2.6.21-1.3194.fc7-i686'

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

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

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

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

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

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

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

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

CC /tmp/vmware-config2/vmmon-only/common/vmciContext.o

CC /tmp/vmware-config2/vmmon-only/common/vmciDatagram.o

CC /tmp/vmware-config2/vmmon-only/common/vmciDriver.o

CC /tmp/vmware-config2/vmmon-only/common/vmciDs.o

CC /tmp/vmware-config2/vmmon-only/common/vmciGroup.o

CC /tmp/vmware-config2/vmmon-only/common/vmciHashtable.o

CC /tmp/vmware-config2/vmmon-only/common/vmciProcess.o

CC /tmp/vmware-config2/vmmon-only/common/vmciResource.o

CC /tmp/vmware-config2/vmmon-only/common/vmciSharedMem.o

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

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

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

Building modules, stage 2.

MODPOST 1 modules

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

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

make[1]: Leaving directory `/usr/src/kernels/2.6.21-1.3194.fc7-i686'

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

make: Leaving directory `/tmp/vmware-config2/vmmon-only'

The module loads perfectly in the running kernel.

Extracting the sources of the vmblock module.

Building the vmblock module.

Using 2.6.x kernel build system.

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

make -C /lib/modules/2.6.21-1.3194.fc7/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules

make[1]: Entering directory `/usr/src/kernels/2.6.21-1.3194.fc7-i686'

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

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

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

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

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

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

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

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

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

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

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

Building modules, stage 2.

MODPOST 1 modules

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

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

make[1]: Leaving directory `/usr/src/kernels/2.6.21-1.3194.fc7-i686'

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

make: Leaving directory `/tmp/vmware-config2/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)

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

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)

The following virtual networks have been defined:

. vmnet0 is bridged to eth0

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

. vmnet2 is bridged to eth1

. vmnet8 is a NAT network on private subnet 172.16.61.0.

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

(yes/no) yes

Which virtual network do you wish to configure? (0-99) 0

The network vmnet0 has been reserved for a bridged network. You may change it,

but it is highly recommended that you use it as a bridged network. Are you

sure you want to modify it? (yes/no)

The following virtual networks have been defined:

. vmnet0 is bridged to eth0

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

. vmnet2 is bridged to eth1

. vmnet8 is a NAT network on private subnet 172.16.61.0.

Do you wish to make additional changes to the current virtual networks

settings? (yes/no)

Which virtual network do you wish to configure? (0-99) 1

The network vmnet1 has been reserved for a host-only network. You may change

it, but it is highly recommended that you use it as a host-only network. Are

you sure you want to modify it? (yes/no) yes

What type of virtual network do you wish to set vmnet1?

(bridged,hostonly,nat,none) none

Removing a host-only network for vmnet1.

The following virtual networks have been defined:

. vmnet0 is bridged to eth0

. vmnet2 is bridged to eth1

. vmnet8 is a NAT network on private subnet 172.16.61.0.

Do you wish to make additional changes to the current virtual networks

settings? (yes/no)

Which virtual network do you wish to configure? (0-99) 2

What type of virtual network do you wish to set vmnet2?

(bridged,hostonly,nat,none)

Configuring a bridged network for vmnet2.

The following virtual networks have been defined:

. vmnet0 is bridged to eth0

. vmnet2 is bridged to eth1

. vmnet8 is a NAT network on private subnet 172.16.61.0.

Do you wish to make additional changes to the current virtual networks

settings? (yes/no)

Which virtual network do you wish to configure? (0-99) 2

What type of virtual network do you wish to set vmnet2?

(bridged,hostonly,nat,none) none

Removing a bridged network for vmnet2.

The following virtual networks have been defined:

. vmnet0 is bridged to eth0

. vmnet8 is a NAT network on private subnet 172.16.61.0.

Do you wish to make additional changes to the current virtual networks

settings? (yes/no)

Which virtual network do you wish to configure? (0-99) 1

The network vmnet1 has been reserved for a host-only network. You may change

it, but it is highly recommended that you use it as a host-only network. Are

you sure you want to modify it? (yes/no) yes

What type of virtual network do you wish to set vmnet1?

(bridged,hostonly,nat,none) bridged

Configuring a bridged network for vmnet1.

The following virtual networks have been defined:

. vmnet0 is bridged to eth0

. vmnet1 is bridged to eth1

. vmnet8 is a NAT network on private subnet 172.16.61.0.

Do you wish to make additional changes to the current virtual networks

settings? (yes/no)

Which virtual network do you wish to configure? (0-99) 8

The network vmnet8 has been reserved for a NAT network. You may change it, but

it is highly recommended that you use it as a NAT network. Are you sure you

want to modify it? (yes/no) yes

What type of virtual network do you wish to set vmnet8?

(bridged,hostonly,nat,none) none

Removing a NAT network for vmnet8.

The following virtual networks have been defined:

. vmnet0 is bridged to eth0

. vmnet1 is bridged to eth1

Do you wish to make additional 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-config2/vmnet-only'

make -C /lib/modules/2.6.21-1.3194.fc7/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules

make[1]: Entering directory `/usr/src/kernels/2.6.21-1.3194.fc7-i686'

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

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

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

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

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

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

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

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

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

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

Building modules, stage 2.

MODPOST 1 modules

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

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

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

make[1]: Leaving directory `/usr/src/kernels/2.6.21-1.3194.fc7-i686'

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

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

Starting VMware services:

Virtual machine monitor

Blocking file system:

Virtual ethernet

Bridged networking on /dev/vmnet0

Host network detection

Bridged networking on /dev/vmnet1

The configuration of VMware Workstation 6.0.0 build-45731 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

#

<<< >>>>

0 Kudos
5 Replies
clive_long
Contributor
Contributor
‎10-19-2007 02:23 AM

Hello,

Can anyone come up with a suggestion that I can try? I have re-read the instructions in the WS 6.0 User Guide for setting up a second ethernet connection. I have also read my earlier thread on setting up this wifi card alongside built-in ethernet. I cannot think what I am doing wrong. Currently I'm running the guest connection through eth0 (builtin ethernet) but this restricts severely where I can use my laptop.

Regards

Clive

0 Kudos
clive_long
Contributor
Contributor
‎10-24-2007 01:11 AM

Hi,

I tried in the Workstation settings putting

ethernet 1 (onboard ethernet cable) as custom pointing to /dev/vmnet1

ethernet 2 (wireless lan) as custom pointing to /dev/vmnet0

for a Fedora 7 guest.

Still the only interface able to get an IP Address was the cabled ethernet interface.

So currently I can't bridge a virtual machine to a wireless LAN using VM WS 6.0.0 or 6.0.2 . Wireless LAN works with no problems on Fedora 7 host.

As in earlier posts, I had this working under Fedora Core 5. Has anyone got wireless LAN working on machine running Fedora 7 and VM WS 6.0.x?

As in earlier posts, I have rerun vmware-config.pl several times and tried various ethernet device mappings to vmnetx.

Thanks

Clive

0 Kudos
clive_long
Contributor
Contributor
‎10-24-2007 01:20 AM

Hi,

I have just re-run vmware-config.pl to try to alter the mappings between eth and vmnet.

I saw the following messages. Is the highlighted text significant?

The following virtual networks have been defined:

. vmnet0 is bridged to eth0

. vmnet3 is bridged to eth1

Do you wish to make additional changes to the current virtual networks

settings? (yes/no) no

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

None of the pre-built vmnet modules for VMware Workstation is suitable for your

running kernel. Do you want this program to try to build the vmnet module for

your system (you need to have a C compiler installed on your system)?

Extracting the sources of the vmnet module.

Building the vmnet module.

Using 2.6.x kernel build system.

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

make -C /lib/modules/2.6.21-1.3194.fc7/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules

make[1]: Entering directory `/usr/src/kernels/2.6.21-1.3194.fc7-i686'

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

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

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

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

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

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

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

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

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

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

Building modules, stage 2.

MODPOST 1 modules

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

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

make[1]: Leaving directory `/usr/src/kernels/2.6.21-1.3194.fc7-i686'

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

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

The module loads perfectly in the running kernel.

0 Kudos
clive_long
Contributor
Contributor
‎10-24-2007 04:20 AM

Hello

Can someone please explain the warning (above) from the configuration script

tmp/vmware-config2/vmnet-only/.smac_linux.x386.o.cmd

?

Could this be relevant to my wireless ethernet problem?

Thanks

Clive

0 Kudos
clive_long
Contributor
Contributor
‎10-26-2007 01:55 AM

This problem is now fixed.

Please look in this thread >> http://communities.vmware.com/message/779055

Clive

0 Kudos