From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.30) id 1BAqQS-0004e2-5P for qemu-devel@nongnu.org; Tue, 06 Apr 2004 09:15:36 -0400 Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.30) id 1BAqPr-0004P9-0V for qemu-devel@nongnu.org; Tue, 06 Apr 2004 09:15:31 -0400 Received: from [151.189.21.46] (helo=mail-in-06.arcor-online.net) by monty-python.gnu.org with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.30) id 1BAqPq-0004Nx-Jj for qemu-devel@nongnu.org; Tue, 06 Apr 2004 09:14:58 -0400 Received: from rz.zidlicky.org (dialin-145-254-237-228.arcor-ip.net [145.254.237.228]) by mail-in-06.arcor-online.net (Postfix) with ESMTP id D41DBA7274 for ; Tue, 6 Apr 2004 15:14:54 +0200 (CEST) Date: Tue, 6 Apr 2004 14:17:38 +0200 From: Richard Zidlicky Subject: Re: [Qemu-devel] Qemu workstation Message-ID: <20040406121738.GC2774@linux-m68k.org> References: <200404051047.11383.jm@poure.com> <1081156203.3939.10.camel@aragorn> <4071B41F.3040201@bellard.org> <001601c41b57$ed1704f0$6407a8c0@shaggy> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline In-Reply-To: <001601c41b57$ed1704f0$6407a8c0@shaggy> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org On Mon, Apr 05, 2004 at 10:49:51PM +0100, Jamie Burns wrote: > > I am not sure that handling multiple VMs running at the same time is > > very useful (some architectural changes are needed in QEMU). But > > switching easily between VM configurations seems interesting. > > I think that multiple VM's is a worthy goal as long as you can minimise CPU > usage. Having multiple VM's gives you the ability to do some very cool > things. I use VMWARE in Windows and sometimes have both Linux and FreeBSD > running in VM's so I can test software against all 3 OS's at once. I imagine > it would be very useful to developers of cluster software. > > I tried the Win32 port the other day, running Linux, and it sat using 100% > of the CPU whilst doing next to nothing at a command prompt. Using VMWARE, > and waiting at a command prompt uses very little CPU time. > > Is QEMU sat in a busy loop all the time? it is not QEMU but the hosted OS that is in the busy loop. QEMU will have to recognise "idle loops" to fix this - this could be really tricky. Richard