From owner-freebsd-questions@FreeBSD.ORG Thu Jun 7 04:24:18 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E1A7616A46B for ; Thu, 7 Jun 2007 04:24:18 +0000 (UTC) (envelope-from youshi10@u.washington.edu) Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mx1.freebsd.org (Postfix) with ESMTP id BF88513C483 for ; Thu, 7 Jun 2007 04:24:18 +0000 (UTC) (envelope-from youshi10@u.washington.edu) Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.141] (may be forged)) by mxout5.cac.washington.edu (8.13.7+UW06.06/8.13.7+UW07.05) with ESMTP id l574OIO6029869 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 6 Jun 2007 21:24:18 -0700 X-Auth-Received: from [192.168.10.45] (c-67-166-149-71.hsd1.ca.comcast.net [67.166.149.71]) (authenticated authid=youshi10) by smtp.washington.edu (8.13.7+UW06.06/8.13.7+UW07.03) with ESMTP id l574OHLP021124 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 6 Jun 2007 21:24:17 -0700 Message-ID: <46678873.6090505@u.washington.edu> Date: Wed, 06 Jun 2007 21:24:19 -0700 From: Garrett Cooper User-Agent: Thunderbird 2.0.0.0 (Windows/20070326) MIME-Version: 1.0 To: r17fbsd@xxiii.com References: <46674717.6020105@calarts.edu> <6.2.3.4.2.20070606235806.029d5960@mailsvr.xxiii.com> In-Reply-To: <6.2.3.4.2.20070606235806.029d5960@mailsvr.xxiii.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-PMX-Version: 5.3.1.294258, Antispam-Engine: 2.5.1.298604, Antispam-Data: 2007.6.6.210738 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __USER_AGENT 0' Cc: Sean Murphy , freebsd-questions@freebsd.org Subject: Re: Virtualization of FreeBSD X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Jun 2007 04:24:19 -0000 r17fbsd@xxiii.com wrote: > At 07:45 PM 6/6/2007, Sean Murphy wrote: >> Is anyone running virtualization of FreeBSD servers on VMware or >> other virtualization software? What experiences have you had, good >> or bad? > > Been wanting to ask the same... I've heard of virt' software for some > time but didn't realize what it could really do. Then on a tip, I > started playing with micros$$ts Virtual PC a couple weeks ago. Wow! > It runs windoze 2000 and FreeBSD apparently fine on a windoze 2000 > host. In the last couple weeks I've been doing a lot of > experimentation with FreeBSD and Samba and windoze that I've been > procrastinating about for lack of a spare box to run things on. Very > impressive for free stuff from the evil empire :) > > But from what I've heard, VMware has better performance. And there > are some things in ports (qemu?) also. For my purposes Billy's > product is working well, but I'd like to hear of better things, esp > those that run on windoze, which I'm stuck with for my desktop boxen. > > -RW The pecking order works like so IMHO under Windows: 1. VMWare. 2. M$ VPC. 3. Qemu. -Vmware has the best performance overall from what I've seen, and has 64-bit support on 64-bit processors, so it wins hands down. -M$ VPC has better performance than Qemu from what I've seen, but only has 32-bit support, so that's out. -Getting Qemu started on Windows (at least for me), was a pain in the a$$. I eventually gave up because it was so slow and the hardware virtualization wasn't that great. I run CURRENT and 6.2-RELEASE on my desktop under Windows because hardware support for all my devices isn't quite there yet, and for development. It's ok, except when I do CPU intensive tasks, where the virtual CPU clock per VM skews a lot/slows down, and this screws up shutting down the VMs (they get stuck before FS syncing's started). Solution is to run ntpdate before shutdown, to update the VM time. I'm running VMware server on XP x64 with 4GB of RAM and a Core 2 Duo 6700 CPU. -Garrett