From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1FOJ7U-0007ZM-67
	for qemu-devel@nongnu.org; Tue, 28 Mar 2006 13:40:44 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1FOJ7P-0007V6-OH
	for qemu-devel@nongnu.org; Tue, 28 Mar 2006 13:40:43 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1FOJ7P-0007Uy-H5
	for qemu-devel@nongnu.org; Tue, 28 Mar 2006 13:40:39 -0500
Received: from [195.184.98.160] (helo=virtualhost.dk)
	by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_3DES_EDE_CBC_SHA:24) (Exim 4.52) id 1FOJ9B-0007yo-TI
	for qemu-devel@nongnu.org; Tue, 28 Mar 2006 13:42:30 -0500
Date: Tue, 28 Mar 2006 20:40:44 +0200
From: Jens Axboe <qemu@kernel.dk>
Subject: Re: [Qemu-devel] kqemu version 1.3.0pre5
Message-ID: <20060328184037.GJ8186@suse.de>
References: <44285974.9040003@bellard.org>
	<c1bf1cf0603281019i66c3acc7k98f8f805b617b5a5@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <c1bf1cf0603281019i66c3acc7k98f8f805b617b5a5@mail.gmail.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
Cc: Andre Pech <andre.pech@gmail.com>

On Tue, Mar 28 2006, Ed Swierk wrote:
> I'm still getting a kernel panic running a Linux guest kernel with
> -kernel-qemu. I'm using kqemu-1.3.0pre5 and
> qemu-snapshot-2006-03-27_23.
> 
> The guest kernel is a precompiled Fedora Core 4 kernel, version
> 2.6.14-1.1656_FC4. It works fine with kqemu in non-kernel-kqemu mode.
> 
> Any hints for how to track this problem down?

[snip]

> monitor/mwait feature present.
> using mwait in idle threads.

[snip]

> invalid operand: 0000 [#1]
> Modules linked in:
> CPU:    0
> EIP:    0060:[<c0101147>]    Not tainted VLI
> EFLAGS: 00010246   (2.6.14-1.1656_FC4)
> EIP is at mwait_idle+0x2f/0x41

I don't think qemu supports PNI, which includes the monitor/mwait
additions. I wonder why Linux detects that. You can probably get around
it for now by either passing idle=poll as a boot parameter, or compile
your kernel for plain i586 for instance.

-- 
Jens Axboe