From owner-freebsd-emulation Sun Nov 18 21:23:20 2001 Delivered-To: freebsd-emulation@freebsd.org Received: from ambrisko.com (adsl-64-174-51-42.dsl.snfc21.pacbell.net [64.174.51.42]) by hub.freebsd.org (Postfix) with ESMTP id 5E2A137B405 for ; Sun, 18 Nov 2001 21:23:17 -0800 (PST) Received: (from ambrisko@localhost) by ambrisko.com (8.11.6/8.11.6) id fAJ5M5u80672; Sun, 18 Nov 2001 21:22:05 -0800 (PST) (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <200111190522.fAJ5M5u80672@ambrisko.com> Subject: Re: FYI, multiple vmwares is possible but is a hack In-Reply-To: To: Garance A Drosihn Date: Sun, 18 Nov 2001 21:22:05 -0800 (PST) Cc: Doug Ambrisko , freebsd-emulation@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL94b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Garance A Drosihn writes: | Way back on June 12/2001, Doug Ambrisko wrote: | >I have 2 vmwares running. I got the second one running by creating another | >vmmon with a different name but same number of characters: FYI a simplier method is to use the latest code at: http://www.mindspring.com/~vsilyaev/vmware/files/FreeBSD-README.html which just does the right thing and doesn't need my hack. | which seemed to do the right thing (I get the same output from 'ls' as | Doug listed). The second machine gets an error at startup though, with | vmware complaining: | "Could not open /dev/vmnet1. Device or resource busy. | Failed to configure ethernet0". | | I expect that's because I don't know what do about the part where Doug | says "I define non-conflicting devices, and use netgraph...". Do I | need to duplicate /usr/local/etc/rc.d/vmware.sh , and have it create | a vmnet2 device? If so, how do I get the second-vmnet device? I tried | duplicating the startup-script, and changing vmnet1 to vmnet2, but that | didn't work because 'ifconfig' doesn't know about a vmnet2 interface. You need more vmnet devices look at such as: a21p% ls -l /compat/linux/dev/vmnet* crw-r--r-- 1 root wheel 149, 0x00010001 Nov 16 15:44 /compat/linux/dev/vmnet1 crw-r--r-- 1 root wheel 149, 0x0001000a Oct 23 13:15 /compat/linux/dev/vmnet10 crw-r--r-- 1 root wheel 149, 0x0001000b Oct 12 16:24 /compat/linux/dev/vmnet11 crw-r--r-- 1 root wheel 149, 0x00010002 Oct 13 21:28 /compat/linux/dev/vmnet2 crw-r--r-- 1 root wheel 149, 0x00010003 Oct 15 08:58 /compat/linux/dev/vmnet3 crw-r--r-- 1 root wheel 149, 0x00010004 Oct 23 13:15 /compat/linux/dev/vmnet4 crw-r--r-- 1 root wheel 149, 0x00010005 Oct 23 13:17 /compat/linux/dev/vmnet5 crw-r--r-- 1 root wheel 149, 0x00010006 Oct 15 08:58 /compat/linux/dev/vmnet6 crw-r--r-- 1 root wheel 149, 0x00010007 Oct 15 08:58 /compat/linux/dev/vmnet7 crw-r--r-- 1 root wheel 149, 0x00010008 Oct 12 17:08 /compat/linux/dev/vmnet8 crw-r--r-- 1 root wheel 149, 0x00010009 Oct 12 12:40 /compat/linux/dev/vmnet9 a21p% If you want to bridge a bunch then you need modify the vmnware script to do that. Define in vmware the Ethernet types as custom and then enter /dev/vmnet name. Doug A. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message