Vmware2 and FreeBSD 4.4-STABLE network trouble

Vmware2 and FreeBSD 4.4-STABLE network trouble

Post by mike » Thu, 15 Nov 2001 15:56:42



Alright, I'm having issues. To begin with, I'm not finding very many
documents online detailing how to get VMWare 2.0.4 to run on FreeBSD.
The Hints.FreeBSD file doesn't help too much either :(  So here's
what's happening ..

I'm running 4.4-20011111-STABLE, with a modification to the kernel
'option BRIDGE'. among other things.

I've got vmware2 installed from the ports collection,
/usr/ports/emulators/vmware2, with the 'make install' directive. When
asked, I choose to have netgraph enabled, and the interface I specify
is 'dc0' (should I be using /dev/dc0 instead?? this is very unclear. I
actually tried both, and both times failed). dc0 is indeed my ethernet
card. After that's done, I reboot (so any startup scripts are run like
they should..). When that's over, I run vmware:

mikeg on adanac ~ $ vmware
************************************************************
It seems Linux procfs is not mounted on /compat/linux/proc.
VMware does not work without Linux procfs mounted.

For details, see linprocfs(5) manpage.
************************************************************

This isn't good, but through some digging I found someone's suggestion
on this (or another?) newsgroup as follows:

mount_linprocfs linprocfs /compat/linux/proc

Now vmware runs like fine, but it won't boot the vm because it cannot
find a network device for itself. The debug-mode log file states:

Nov 13 22:09:50: Msg_Post Error: msg.ethernet.configFailed
Could not open /dev/vmnet0: No such file or directory
Failed to configure ethernet1.
Nov 13 22:09:53: Poweron failed at module 44

This is in bridged-mode. In another attempt, with host-only
networking, I see:

Nov 13 22:15:03: Msg_Post Error: msg.ethernet.configFailed
Could not get address for /dev/vmnet1: Invalid argument
Failed to configure ethernet0.
Nov 13 22:15:05: Poweron failed at module 44

I feel helpless! I see that:

root on adanac /compat/linux/dev # ls
hda     null    tty0    tty10   tty12   tty3    tty5    tty7    tty9  
 vmnet1
hdb     rtc     tty1    tty11   tty2    tty4    tty6    tty8    vmmon

So why can't it find an address for vmnet1?? My network setup looks as
follows:

root on adanac /etc # ifconfig
dc0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu
1500
        inet 10.0.0.2 netmask 0xffffff00 broadcast 10.0.0.255
        inet6 fe80::2a0:ccff:feda:6451%dc0 prefixlen 64 scopeid 0x1
        ether 00:a0:cc:da:64:51
        media: Ethernet autoselect (10baseT/UTP)
        status: active
lp0: flags=8810<POINTOPOINT,SIMPLEX,MULTICAST> mtu 1500
faith0: flags=8000<MULTICAST> mtu 1500
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
        inet6 ::1 prefixlen 128
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4
        inet 127.0.0.1 netmask 0xff000000
ppp0: flags=8010<POINTOPOINT,MULTICAST> mtu 1500
sl0: flags=c010<POINTOPOINT,LINK2,MULTICAST> mtu 552
vmnet1: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu
1500
        inet 192.168.0.1 netmask 0xffffff00 broadcast 192.168.0.255
        inet6 fe80::2bd:27ff:fe0b:1%vmnet1 prefixlen 64 scopeid 0x7
        ether 00:bd:27:0b:00:01
root on adanac /etc # ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1): 56 data bytes
64 bytes from 192.168.0.1: icmp_seq=0 ttl=64 time=0.072 ms
...

So the interface both exists, and I can ping it. That's a good sign,
right?

Tired of all this, I tried 'make deinstall' and 'make install' on
vmware2, and noted the message that appears after 'make install'. So I
ran:

root on adanac /usr/ports/emulators/vmware2 #
/usr/local/etc/rc.d/vmware.sh start
ngctl: send msg: File exists
ngctl: send msg: Socket is already connected
ngctl: send msg: File exists
ngctl: send msg: File exists
 VMwareroot on adanc ....

Presumably, this is something that was run on startup from the last
install.. Speaking of the startup, pertinent information from dmesg
shows:

BRIDGE 011031, have 2 interfaces
-- index 1  type 6 phy 0 addrl 6 addr 00.a0.cc.da.64.51
/dev/vmmon: Module vmmon: registered with major=200 minor=0 tag=$Name:
build-570 $
/dev/vmmon: Module vmmon: initialized
BRIDGE 011031, have 7 interfaces
-- index 1 dc0:1 type 6 phy 0 addrl 6 addr 00.a0.cc.da.64.51
-- index 7  type 6 phy 0 addrl 6 addr 00.bd.27.0b.00.01
dc0: promiscuous mode enabled
vmnet1: promiscuous mode enabled
/dev/vmmon: Vmx86_DestroyVM: unlocked pages: 0, unlocked dirty pages:
0
/dev/vmmon: Vmx86_DestroyVM: unlocked pages: 0, unlocked dirty pages:
0
/dev/vmmon: Vmx86_DestroyVM: unlocked pages: 0, unlocked dirty pages:
0
/dev/vmmon: Vmx86_DestroyVM: unlocked pages: 0, unlocked dirty pages:
0
/dev/vmmon: Vmx86_DestroyVM: unlocked pages: 0, unlocked dirty pages:
0

So, what can anyone suggest? Should I just start over from scratch?
Short of reinstalling the entire OS, how do I know that all traces of
vmwareness are gone?

I have the possibility to install Linux instead (this intallation is
only a few days old, so nothing big would be lost, except time)
because VMWare seems to be catered for it. But I really prefer
FreeBSD, so can anyone help?

Thanks!

--
~ Michal

 
 
 

Vmware2 and FreeBSD 4.4-STABLE network trouble

Post by John Nielse » Thu, 15 Nov 2001 20:29:39



Quote:> Alright, I'm having issues. To begin with, I'm not finding very many
> documents online detailing how to get VMWare 2.0.4 to run on FreeBSD.
> The Hints.FreeBSD file doesn't help too much either :(  So here's
> what's happening ..

> I'm running 4.4-20011111-STABLE, with a modification to the kernel
> 'option BRIDGE'. among other things.

> I've got vmware2 installed from the ports collection,
> /usr/ports/emulators/vmware2, with the 'make install' directive. When
> asked, I choose to have netgraph enabled, and the interface I specify
> is 'dc0' (should I be using /dev/dc0 instead?? this is very unclear. I
> actually tried both, and both times failed). dc0 is indeed my ethernet
> card. After that's done, I reboot (so any startup scripts are run like
> they should..). When that's over, I run vmware:
<snip>
> Now vmware runs like fine, but it won't boot the vm because it cannot
> find a network device for itself. The debug-mode log file states:

> Nov 13 22:09:50: Msg_Post Error: msg.ethernet.configFailed
> Could not open /dev/vmnet0: No such file or directory
> Failed to configure ethernet1.
> Nov 13 22:09:53: Poweron failed at module 44

> This is in bridged-mode. In another attempt, with host-only
> networking, I see:

> Nov 13 22:15:03: Msg_Post Error: msg.ethernet.configFailed
> Could not get address for /dev/vmnet1: Invalid argument
> Failed to configure ethernet0.
> Nov 13 22:15:05: Poweron failed at module 44

This would appear to be a bug.  Something in the newer -stable linux
stuff doesn't jive with th vmnet stuff.  Whether the but is in -stable
or in vmnet I can't say, but it works fine in 4.4-RELEASE.  I tried this
on my machine running -stable (today's build) with both linux_base-6.1
and linux_base-7.1 with the same result.

<snip>

Quote:> So, what can anyone suggest? Should I just start over from scratch?
> Short of reinstalling the entire OS, how do I know that all traces of
> vmwareness are gone?

pkg_delete vmware-whatever and a make clean in the vmware2 port
directory should do it.  But like I say, I tried this today with a clean
build and had the same problem you did.

Quote:> I have the possibility to install Linux instead (this intallation is
> only a few days old, so nothing big would be lost, except time)
> because VMWare seems to be catered for it. But I really prefer
> FreeBSD, so can anyone help?

Either go back to 4.4-RELEASE, run Linux, or wait for the bug to be
fixed.  If you want to be proactive about it then post messages to
the -stable and -ports mailing lists, e-mail Vladimir Silaev (the port
maintainer--he does check his mail), and/or submit a PR.

JN

 
 
 

Vmware2 and FreeBSD 4.4-STABLE network trouble

Post by mike » Fri, 16 Nov 2001 04:41:27





> > Alright, I'm having issues. To begin with, I'm not finding very many
> > documents online detailing how to get VMWare 2.0.4 to run on FreeBSD.
> > The Hints.FreeBSD file doesn't help too much either :(  So here's
> > what's happening ..

> > I'm running 4.4-20011111-STABLE, with a modification to the kernel
> > 'option BRIDGE'. among other things.

<snip>

Quote:

> > Nov 13 22:15:03: Msg_Post Error: msg.ethernet.configFailed
> > Could not get address for /dev/vmnet1: Invalid argument
> > Failed to configure ethernet0.
> > Nov 13 22:15:05: Poweron failed at module 44

> This would appear to be a bug.  Something in the newer -stable linux
> stuff doesn't jive with th vmnet stuff.  Whether the but is in -stable
> or in vmnet I can't say, but it works fine in 4.4-RELEASE.  I tried this
> on my machine running -stable (today's build) with both linux_base-6.1
> and linux_base-7.1 with the same result.

> <snip>

I see.. how unfortunate. I'll revert to using 4.4-RELEASE, I suppose.
So you think this has to do with the changes (?) to the linux package,
or the FreeBSD RELEASE->STABLE change?

Quote:> > So, what can anyone suggest? Should I just start over from scratch?
> > Short of reinstalling the entire OS, how do I know that all traces of
> > vmwareness are gone?

> pkg_delete vmware-whatever and a make clean in the vmware2 port
> directory should do it.  But like I say, I tried this today with a clean
> build and had the same problem you did.

I think I'll settle for rm -rf /  (-;

Quote:> > I have the possibility to install Linux instead (this intallation is
> > only a few days old, so nothing big would be lost, except time)
> > because VMWare seems to be catered for it. But I really prefer
> > FreeBSD, so can anyone help?

> Either go back to 4.4-RELEASE, run Linux, or wait for the bug to be
> fixed.  If you want to be proactive about it then post messages to
> the -stable and -ports mailing lists, e-mail Vladimir Silaev (the port
> maintainer--he does check his mail), and/or submit a PR.

Alright, thanks for the quick reply! (:

--
~ Michal

 
 
 

Vmware2 and FreeBSD 4.4-STABLE network trouble

Post by Ian Dow » Tue, 20 Nov 2001 21:24:01



>Nov 13 22:15:03: Msg_Post Error: msg.ethernet.configFailed
>Could not get address for /dev/vmnet1: Invalid argument
>Failed to configure ethernet0.
>Nov 13 22:15:05: Poweron failed at module 44

This is the result of some changes to the Linux emulation code that
was recently merged into -stable. Check the freebsd-emulation
mailing list archives for patches. A workaround for this is likely
to make it to -stable within the next few days.

Ian

 
 
 

1. vmware2 and latest freebsd 4.4 stable

Hello,

After running cvsup to obtain latest stable of freebsd 4.4. My vmware2 under
linux emulation no longer work.

vmnet1 interface is up and running and I can ping it:
vmnet1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        inet 192.168.254.1 netmask 0xffffff00 broadcast 192.168.254.255
        ether 00:bd:eb:08:00:01

Each time I startup vmware from command line, after a series of windows, I get
the error:

Could not get address for /dev/vmnet1: Invalid argument.
Failed to configure ethernet0.

I noticed that the cvsup of the latest stable checked out some linux source
files. I don't know where the linux emulation breaks so any help or pointers
are greatly appreciated.

--
Camson Huynh

BioLateral

2. How to install new applications???

3. Network bug in FreeBSD 4.4 STABLE

4. New channel: FIDO

5. Network bug - FreeBSD 4.4 STABLE

6. Multiple Default Gateways

7. FreeBSD 4.4-20011111-STABLE bug?

8. CDROM burning

9. XFree86 4.1 Problem with FreeBSD 4.4-STABLE

10. FreeBSD 4.4 - STABLE lockup

11. New FreeBSD-stable 4.4 release?

12. problems with FreeBSD 4.4-stable- HELP