From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1GvLpk-0001Bm-1X
	for qemu-devel@nongnu.org; Fri, 15 Dec 2006 17:47:16 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1GvLpi-0001BO-Ie
	for qemu-devel@nongnu.org; Fri, 15 Dec 2006 17:47:15 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1GvLpi-0001BL-DK
	for qemu-devel@nongnu.org; Fri, 15 Dec 2006 17:47:14 -0500
Received: from [65.74.133.4] (helo=mail.codesourcery.com)
	by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1GvLpi-0008QB-BU
	for qemu-devel@nongnu.org; Fri, 15 Dec 2006 17:47:14 -0500
From: Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] Qemu speed vs vmplayer?
Date: Fri, 15 Dec 2006 22:47:08 +0000
References: <10541fa50612130009s798a1587n4a3d2b8b51baa334@mail.gmail.com>
	<200612152218.12733.paul@codesourcery.com>
	<46d6db660612151434k502de652m91658b2e3b451fab@mail.gmail.com>
In-Reply-To: <46d6db660612151434k502de652m91658b2e3b451fab@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200612152247.10133.paul@codesourcery.com>
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org

> Is qvm86 still active ? if yes, great. if no, what do you need to restart
> it ? (else than dedicated developpers, of course). As far as I can see, no
> qvm86 check-in for 15 months now...

Not really. I haven't had chance to do anything with it for a while, and 
probably won't in the forseeable future. It probably wouldn't take more than 
a couple of weeks work for an experienced coder to get it working properly.

If someone else shows serious interest in qvm86 I've no real objection to 
handing over management of the project to them.

As Anthony mentioned, efforts might be best spent integrating this 
functionality into Xen or KVM. You're more than welcome to use qvm86 code for 
this.

Paul