From owner-freebsd-emulation@FreeBSD.ORG Wed Dec 21 12:44:21 2005 Return-Path: X-Original-To: freebsd-emulation@freebsd.org Delivered-To: freebsd-emulation@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 00C0516A41F for ; Wed, 21 Dec 2005 12:44:21 +0000 (GMT) (envelope-from hueber@riic.at) Received: from proxy.riic.at (www.riic.uni-linz.ac.at [140.78.161.123]) by mx1.FreeBSD.org (Postfix) with ESMTP id 476C443D5D for ; Wed, 21 Dec 2005 12:44:19 +0000 (GMT) (envelope-from hueber@riic.at) Received: from hawkings ([140.78.161.82]) by proxy.riic.at (8.12.3/8.12.3/Debian-6.6) with ESMTP id jBLCIYvU030358; Wed, 21 Dec 2005 13:18:34 +0100 From: Gernot Hueber To: Per Hedeland In-Reply-To: <200512202257.jBKMvtDf032319@pluto.hedeland.org> References: <200512202257.jBKMvtDf032319@pluto.hedeland.org> Content-Type: text/plain; charset=iso8859-1 Organization: RIIC Date: Wed, 21 Dec 2005 13:44:17 +0100 Message-Id: <1135169057.1153.4.camel@hawkings> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 8bit Cc: freebsd-emulation@freebsd.org Subject: Re: vmware3 on freebsd5.4 fails networking X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Dec 2005 12:44:21 -0000 Thanks for your response. At least I found out what was going wrong, there was still a /compat/linux/dev/vmnet1 from a very old vmware installation ... After removing that one and linking to the current everything works. Gernot On Tue, 2005-12-20 at 23:57 +0100, Per Hedeland wrote: > Gernot Hueber wrote: > > > >I can't get vmware3 networking up and running :-( > >(While installing the port I have tried both, with and without bridging > >mode) > > Have you installed from a current version of the port? The Makefile has > been broken for the better part of the year, resulting in a rc script > that fails to do the needed network setup. Should be fixed in port > revision 12 on October 14th. > > >vmware starts but I get errors regarding the vmnet > > > >1) When config is set to bridging mode > > > >"Could not query bridging status on device /dev/vmnet0. Please update > >your vmnet driver." > > > >VM starts and I can use it (without networkging) > > VMware itself must always be configured for "Host-Only" mode on FreeBSD. > The choice between really doing that, or bridging via netgraph, is done > by the rc script based on the config that is created when you build the > port. I.e. the above will never work. > > >2) When config is set to host-only mode > > > >"Could not open /dev/vmnet1: No such device or address > >Failed to configure ethernet0." > > > >VM does not start. > > This might possibly be the result of the broken rc script per above, I > don't remember the exact symptom when you actually try to start VMware. > > >In both cases vmnet0 and vmnet1 devices are available. > > Hm, you don't need vmnet0 (which VMware wants to use when configured for > bridging like above), and the rc script won't create it - if you created > the devices yourself you may have done something wrong... > > >What is going wrong here, I have googled around, no luck yet. > > There is some discussion on the gory details of VMware3 networking on > FreeBSD in the MultipleInstances.FreeBSD file that comes with the port > (gets installed in /usr/local/share/doc/vmware) - most of it is probably > overkill if you just want to run a single VMware instance, but it might > give some hints. > > --Per Hedeland > -- DI Gernot Hueber Institut für Integrierte Schaltungen Altenbergerstr. 69 4040 Linz Tel +43 732 2468 7120 Fax +43 732 2468 7126 Email hueber@riic.at Web www.riic.at