From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1FPDyg-0008JQ-JV
	for qemu-devel@nongnu.org; Fri, 31 Mar 2006 02:23:26 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1FPDyf-0008HX-6i
	for qemu-devel@nongnu.org; Fri, 31 Mar 2006 02:23:26 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1FPDyf-0008HP-0O
	for qemu-devel@nongnu.org; Fri, 31 Mar 2006 02:23:25 -0500
Received: from [64.233.166.177] (helo=pproxy.gmail.com)
	by monty-python.gnu.org with esmtp (Exim 4.52) id 1FPE10-0008Pb-Da
	for qemu-devel@nongnu.org; Fri, 31 Mar 2006 02:25:50 -0500
Received: by pproxy.gmail.com with SMTP id i49so277927pye
	for <qemu-devel@nongnu.org>; Thu, 30 Mar 2006 23:23:23 -0800 (PST)
Message-ID: <46d6db660603302323r47622a92l7b2da9bd69e21dc5@mail.gmail.com>
Date: Fri, 31 Mar 2006 09:23:23 +0200
From: "Christian MICHON" <christian.michon@gmail.com>
Subject: Re: [Qemu-devel] kqemu version 1.3.0pre5
In-Reply-To: <44285974.9040003@bellard.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <44285974.9040003@bellard.org>
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

I tried various guests today on winXP host.

* No crash and good speed for std kqemu (no kernel-kqemu)
* Crash of winXP host systematically on all guests (linux + ms)

It's hard to debug what is the problem. The only thing I have the
time to see is a BSOD (blue screen of d**th) and the error
message, informative ?

"TRAP_CAUSE_UNKNOWN"

Good job overall :) Kudos to the developpers.

Maybe we can make it a bartpe plugin one day, automatically
started with kqemu on ? That would be nice to promote
qemu virtualization features...

On 3/27/06, Fabrice Bellard <fabrice@bellard.org> wrote:
> Hi,
>
> I just released a new version of kqemu which fixes some recently
> discovered issues. The fixes are the following:
>
> - Workaround for full virtualization on Windows host (more tests needed).
>

--
Christian