From owner-freebsd-virtualization@FreeBSD.ORG Sat Oct 18 09:43:35 2008 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B29F91065687 for ; Sat, 18 Oct 2008 09:43:35 +0000 (UTC) (envelope-from ilikefbsd@web.de) Received: from fmmailgate03.web.de (fmmailgate03.web.de [217.72.192.234]) by mx1.freebsd.org (Postfix) with ESMTP id 407CA8FC15 for ; Sat, 18 Oct 2008 09:43:35 +0000 (UTC) (envelope-from ilikefbsd@web.de) Received: from smtp06.web.de (fmsmtp06.dlan.cinetic.de [172.20.5.172]) by fmmailgate03.web.de (Postfix) with ESMTP id D0F4DF228A44 for ; Sat, 18 Oct 2008 11:43:33 +0200 (CEST) Received: from [80.244.246.126] (helo=[10.8.0.2]) by smtp06.web.de with asmtp (TLSv1:AES256-SHA:256) (WEB.DE 4.109 #226) id 1Kr8LN-0007uW-00 for freebsd-virtualization@freebsd.org; Sat, 18 Oct 2008 11:43:33 +0200 Message-ID: <48F9AFC4.2090803@web.de> Date: Sat, 18 Oct 2008 11:43:32 +0200 From: Marco User-Agent: Thunderbird 2.0.0.17 (X11/20080930) MIME-Version: 1.0 CC: freebsd-virtualization@freebsd.org References: <48F88B2B.1080700@web.de> <1224245114.75001.7.camel@RabbitsDen> <1224297484.1118.28.camel@RabbitsDen> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sender: ilikefbsd@web.de X-Sender: ilikefbsd@web.de X-Provags-ID: V01U2FsdGVkX1+JrgXH37jLwOz1QQYERaen7tW6i6KJnmY2P4iX SpbVgU8klT8BcE6wuWnWrA3G3xREXWcCyXWV9NT/mqwCLan05X MAa9mPnzA= Subject: Re: Software for virtualisation for FreeBSD needed X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Oct 2008 09:43:35 -0000 >Okay, *now* I'm intrigued ... can you recommend a good 'setup guide' for qemu >under FreeBSD? Or, a good generic one? Actually its pretty simple to setup a qemu machine, what i realy enjoy in qemu is the ability to emulate different architectures, for that however i also have a "guide" i used when setting up a linux arm based system on my fbsd. It's pretty much the same(actually its even easier) to setup a x86 qemu based vm. http://www.aurel32.net/info/debian_arm_qemu.php hth, marco Marc G. Fournier wrote: > > Okay, *now* I'm intrigued ... can you recommend a good 'setup guide' > for qemu > under FreeBSD? Or, a good generic one? > > --On Friday, October 17, 2008 22:38:04 -0400 "Alexandre \"Sunny\" > Kovalenko" > wrote: > > > On Fri, 2008-10-17 at 21:28 -0300, Marc G. Fournier wrote: > >> -----BEGIN PGP SIGNED MESSAGE----- > >> Hash: SHA1 > >> > >> > >> > >> - --On Friday, October 17, 2008 08:05:14 -0400 "Alexandre \"Sunny\" > >> Kovalenko" wrote: > >> > >>> I am using VMware extensively on Linux and Windows hosts and QEMU on > >>> FreeBSD host (with Windows, Linux and OpenSolaris guests) > >> Can you run multiple guest QEMU environments simultaneously? With > >> networking? > > Yes. Yes. ;) > > > I can definitely run multiple QEMU guests simultaneously. Did you have > > any problems doing that? > > > Now, networking part is slightly trickier to answer. Let me try to map > > this into VMware experience: > > > -- assigning IP addresses. I am doing static configurations. It Should > > Not Be Hard (sm) to beat isc-dhcp into serving different address ranges > > to different tapX, but I have not done it. > > > -- guest-to-guest internal networking. Easy: you have separate tapX with > > their separate IP addresses, as long as you have > > net.inet.ip.forwarding=1 set, it "just works". > > > -- nat-to-outside-world. Slightly harder, but doable: > > sunny:RabbitsDen>cat pf.nat.conf > > # Internal interfaces (for QEMU and or Bluetooth clients) > > int_if_0 = "tap0" > > int_if_1 = "tap1" > > > # Private network for QEMU and Bluetooth clients > > private_network_0 = $int_if_0:network > > private_network_1 = $int_if_1:network > > > # External interface (if we are providing NAT for the clients above) > > ext_if = "ath0" > > > # Provide NAT services for private clients > > nat on $ext_if from $private_network_0 to any -> ($ext_if) > > nat on $ext_if from $private_network_1 to any -> ($ext_if) > > > pass from { lo0, $private_network_0 } to any > > pass from { lo0, $private_network_1 } to any > > sunny:RabbitsDen>sudo pfctl -F nat > > sunny:RabbitsDen>sudo pfctl -f pf.nat.conf > > > We are done. Admittedly, if you have many clients which flicker in and > > out of existence, this gets very messy very quickly. Some scripting is > > advised. > > > -- bridging-to-outside world. Have not tried it for the lack of need. > > > HTH, > > > -- > > Alexandre "Sunny" Kovalenko (;5:A0=4@ >20;5=:>) > > > >