From owner-freebsd-emulation@FreeBSD.ORG Tue Dec 20 22:58:00 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 6BDA516A48F for ; Tue, 20 Dec 2005 22:58:00 +0000 (GMT) (envelope-from per@hedeland.org) Received: from pluto.hedeland.org (1-1-1-13a.mal.sth.bostream.se [82.182.84.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id B7D6643D5C for ; Tue, 20 Dec 2005 22:57:57 +0000 (GMT) (envelope-from per@hedeland.org) Received: from pluto.hedeland.org (localhost [127.0.0.1]) by pluto.hedeland.org (8.13.1/8.13.1) with ESMTP id jBKMvu8Q032320 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 20 Dec 2005 23:57:56 +0100 (CET) (envelope-from per@pluto.hedeland.org) Received: (from per@localhost) by pluto.hedeland.org (8.13.1/8.13.1/Submit) id jBKMvtDf032319; Tue, 20 Dec 2005 23:57:55 +0100 (CET) (envelope-from per) Date: Tue, 20 Dec 2005 23:57:55 +0100 (CET) From: Per Hedeland Message-Id: <200512202257.jBKMvtDf032319@pluto.hedeland.org> To: hueber@riic.at In-Reply-To: <1135086948.2765.6.camel@midori> X-Scanned-By: MIMEDefang 2.48 on 127.0.0.1 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: Tue, 20 Dec 2005 22:58:00 -0000 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