From owner-freebsd-emulation@FreeBSD.ORG Thu Jul 1 13:24:39 2004 Return-Path: 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 1478716A4CE for ; Thu, 1 Jul 2004 13:24:38 +0000 (GMT) Received: from pluto.hedeland.org (c0172a.mael.bostream.se [194.236.4.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 43DFF43D2F for ; Thu, 1 Jul 2004 13:24:38 +0000 (GMT) (envelope-from per@hedeland.org) Received: from pluto.hedeland.org (localhost [127.0.0.1]) i61DNhBH000680 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 1 Jul 2004 15:23:43 +0200 (CEST) Received: (from per@localhost)i61DNhZ6000679; Thu, 1 Jul 2004 15:23:43 +0200 (CEST) Date: Thu, 1 Jul 2004 15:23:43 +0200 (CEST) From: Per Hedeland Message-Id: <200407011323.i61DNhZ6000679@pluto.hedeland.org> To: Sean_Welch@alum.wofford.org In-Reply-To: <20040701130406.GA1134@NitroPhys.welchsmnet.net> X-Scanned-By: MIMEDefang 2.39 cc: freebsd-emulation@freebsd.org Subject: Re: Patches to allow running multiple vmware3 instances X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.1 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: Thu, 01 Jul 2004 13:24:39 -0000 Sean Welch wrote: > >I added in your patches and recompiled. I do indeed get multiple >vmnet interfaces but I don't seem able to configure them as you show >in your example. Specifically, I cannot configure the interfaces to >be on the same subnet with the same netmask. That's right - FreeBSD doesn't allow this AFAIK (it doesn't "make sense" from a routing perspective). So that's a limitation that follows from the use of one vmnet interface per vmware instance: Each vmware instance must be in its own subnet. Unless you use bridged mode, of course... > Your example file suggests you used this >(snip): > >vmnet1.Bridged = "NO" >vmnet1.BridgeInterface = "" >vmnet1.HostOnlyAddress = "172.31.254.1" >vmnet1.HostOnlyNetMask = "255.255.255.240" >vmnet2.Bridged = "NO" >vmnet2.BridgeInterface = "" >vmnet2.HostOnlyAddress = "172.31.254.17" >vmnet2.HostOnlyNetMask = "255.255.255.240" Yes - note that those are two different subnets, .1-.15 and .17-.31, given the netmask. >My config file looks like this: > >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" >vmnet1.Bridged = "NO" >vmnet1.BridgeInterface = "" >vmnet1.HostOnlyAddress = "172.19.20.40" >vmnet1.HostOnlyNetMask = "255.255.255.0" >vmnet2.Bridged = "NO" >vmnet2.BridgeInterface = "" >vmnet2.HostOnlyAddress = "172.19.20.41" >vmnet2.HostOnlyNetMask = "255.255.255.0" And that won't work. As to why, lets say that your vmware instance has the IP address 172.19.20.42 - how can the FreeBSD stack know whether packets for it should be sent via the vmnet1 or the vmnet2 interface? So it's simply not allowed - the interface configs are considered conflicting. --Per Hedeland per@hedeland.org