From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Fymla-0006DP-Fw for qemu-devel@nongnu.org; Fri, 07 Jul 2006 05:36:54 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1FymlZ-0006Bn-7o for qemu-devel@nongnu.org; Fri, 07 Jul 2006 05:36:53 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FymlZ-0006Bg-5o for qemu-devel@nongnu.org; Fri, 07 Jul 2006 05:36:53 -0400 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 1Fymlw-0004iV-VT for qemu-devel@nongnu.org; Fri, 07 Jul 2006 05:37:17 -0400 Date: Fri, 7 Jul 2006 11:39:12 +0200 From: Jens Axboe Subject: Re: [Qemu-devel] Pentium D with guest Ubuntu 6.06 server kernel panic with kqemu Message-ID: <20060707093912.GQ4188@suse.de> References: <44AD28AA.7050301@armiento.net> <22B10AD6-77B0-454C-9719-13E7E19C741B@gmx.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <22B10AD6-77B0-454C-9719-13E7E19C741B@gmx.de> 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 Cc: "R. Armiento" On Fri, Jul 07 2006, Joachim Henke wrote: > Yes, this patch was included, but it doesn't solve that problem. As > this message [http://www.mail-archive.com/qemu-devel@nongnu.org/ > msg03972.html] states, the 'monitor' and the 'mwait' instructions > have not been added. But your guest OS assumes them to be present, > because your host cpu has the MONITOR flag set in CPUID. > > Jo. > > R. Armiento wrote: > >The error looks very similar to the one reported here: > > http://www.mail-archive.com/qemu-devel@nongnu.org/msg03964.html > >But I believe that reported issue should not appear in recent qemu, > >since SSE3 is now emulated (right?). (At least the patch in the end > >of that thread seems to already be included in the sources?) > > > >So, my hypothesis is that there is some other feature that appears > >in my host CPUID, which the booting linux image tries to make use > >of, but which qemu does not emulate. Until that gets fixed up, you can boot with idle=halt. -- Jens Axboe