vmnet1 problem in vmware2-2.0.4.1142
Yasuhito KAMINAGA
Recently, I upgraded vmware from vmware2-2.0.3.799_1 to
vmware2-2.0.4.1142. The upgrading procedure was as follows.
First, I uninstalled the old port, and then installed the
new port. The procedure went on successfully and I could
start vmware. However, when I click the "power on" button
to start the guest OS (WinNT4.0), I met a problem. Namely,
my vmware complains as follows.
Could not get address for /dev/vmnet1: Invalid argument
Failed to configure ehthernet0.
When I was a user of the old port, I never encounter the
problem. When installing the new port, I followed exactly
the same procedure needed for the old port to work, in which
I enabled netgraph bridging. I do not change any items in
"configuration editor."
How can I solve the problem? Any hints are welcome.
Y. Kaminaga
Gunma National College of Technology
REFERENCES
I am using 4.4-STABLE (with source on Nov. 11 2001) and
rtc-2001.09.16.1.
% dmesg
/dev/vmmon: Module vmmon: registered with major=200 minor=0 tag=$Name: build-570 $
/dev/vmmon: Module vmmon: initialized
fxp0: promiscuous mode enabled
vmnet1: promiscuous mode enabled
/dev/vmmon: Vmx86_DestroyVM: unlocked pages: 0, unlocked dirty pages: 0
/dev/vmmon: Module vmmon: unloaded
% kldstat
Id Refs Address Size Name
1 11 0xc0100000 386484 kernel
2 1 0xc120e000 7000 linprocfs.ko
3 3 0xc126f000 14000 linux.ko
5 1 0xc146c000 2000 rtc.ko
7 1 0xc1487000 4000 if_tap.ko
8 4 0xc148d000 9000 netgraph.ko
9 1 0xc149a000 3000 ng_ether.ko
10 1 0xc149e000 4000 ng_bridge.ko
11 1 0xc14a3000 3000 ng_socket.ko
12 1 0xc147b000 9000 vmmon_up.ko
# ngctl show vmnet_bridge:
Name: vmnet_bridge Type: bridge ID: 00000010 Num hooks: 3
Local hook Peer name Peer type Peer ID Peer hook
---------- --------- --------- ------- ---------
link2 fxp0 ether 00000001 upper
link1 fxp0 ether 00000001 lower
link0 vmnet1 ether 00000002 lower
% ifconfig vmnet1
vmnet1: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
inet6 fe80::2bd:cbff:fe0b:1%vmnet1 prefixlen 64 scopeid 0x7
inet 172.16.66.62 netmask 0xfffff800 broadcast 172.16.71.255
ether 00:bd:cb:0b:00:01
% ls -l /usr/compat/linux/dev
total 0
brw-rw-r-- 1 root wheel 0, 0x00010002 11/19 13:39 hda
brw-r--r-- 1 root wheel 0, 0x0001000a 11/19 13:39 hdb
crw-rw-rw- 1 root wheel 2, 2 11/19 13:39 null
crw-r--r-- 1 root wheel 202, 0 11/19 13:33 rtc
lrwxr-xr-x 1 root wheel 22 11/19 13:39 tty0 -> /compat/linux/dev/tty1
lrwxr-xr-x 1 root wheel 10 11/19 13:39 tty1 -> /dev/ttyv0
lrwxr-xr-x 1 root wheel 10 11/19 13:39 tty10 -> /dev/ttyv9
lrwxr-xr-x 1 root wheel 10 11/19 13:39 tty11 -> /dev/ttyva
lrwxr-xr-x 1 root wheel 10 11/19 13:39 tty12 -> /dev/ttyvb
lrwxr-xr-x 1 root wheel 10 11/19 13:39 tty2 -> /dev/ttyv1
lrwxr-xr-x 1 root wheel 10 11/19 13:39 tty3 -> /dev/ttyv2
lrwxr-xr-x 1 root wheel 10 11/19 13:39 tty4 -> /dev/ttyv3
lrwxr-xr-x 1 root wheel 10 11/19 13:39 tty5 -> /dev/ttyv4
lrwxr-xr-x 1 root wheel 10 11/19 13:39 tty6 -> /dev/ttyv5
lrwxr-xr-x 1 root wheel 10 11/19 13:39 tty7 -> /dev/ttyv6
lrwxr-xr-x 1 root wheel 10 11/19 13:39 tty8 -> /dev/ttyv7
lrwxr-xr-x 1 root wheel 10 11/19 13:39 tty9 -> /dev/ttyv8
crw-r--r-- 1 root wheel 200, 0 11/19 13:39 vmmon
crw-r--r-- 1 root wheel 149, 0x00010001 11/19 13:39 vmnet1
% cat /usr/local/etc/vmware/config
vmware.fullpath = "/usr/local/lib/vmware/bin/vmware"
wizard.fullpath = "/usr/local/lib/vmware/bin/vmware-wizard"
dhcpd.fullpath = "/usr/local/lib/vmware/bin/vmnet-dhcpd"
loop.fullpath = ""/usr/local/lib/vmware/bin/vmware-loop"
libdir = "/usr/local/lib/vmware/lib"
vmnet1.HostOnlyAddress = "172.16.66.62"
vmnet1.HostOnlyNetMask = "255.255.248.0"
To Unsubscribe: send mail to majo...@FreeBSD.org
with "unsubscribe freebsd-emulation" in the body of the message
Garance A Drosihn
>However, when I click the "power on" button to start the guest
>OS (WinNT4.0), I met a problem. Namely, my vmware complains as
>follows.
>
> Could not get address for /dev/vmnet1: Invalid argument
> Failed to configure ehthernet0.
The problem is not in the new port, it's in changes made to other
parts of the operating system.
Please see recent messages in the freebsd-emulation mailing list
about "Linuxulator MFC and VMware". Particularly the message
from Ian Dowse from Fri, 16 Nov 2001. It includes a patch that
you would need to apply to src/sys/compat/linux/linux_ioctl.c .
--
Garance Alistair Drosehn = g...@eclipse.acs.rpi.edu
Senior Systems Programmer or g...@freebsd.org
Rensselaer Polytechnic Institute or dro...@rpi.edu