From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1FyokV-0006WN-RS
	for qemu-devel@nongnu.org; Fri, 07 Jul 2006 07:43:55 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1FyokU-0006Te-2e
	for qemu-devel@nongnu.org; Fri, 07 Jul 2006 07:43:55 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1FyokT-0006TI-S1
	for qemu-devel@nongnu.org; Fri, 07 Jul 2006 07:43:53 -0400
Received: from [81.228.11.159] (helo=pne-smtpout2-sn1.fre.skanova.net)
	by monty-python.gnu.org with esmtp (Exim 4.52) id 1Fyoks-00065u-D1
	for qemu-devel@nongnu.org; Fri, 07 Jul 2006 07:44:18 -0400
Received: from neo.armiento.se (83.250.129.152) by
	pne-smtpout2-sn1.fre.skanova.net (7.2.075)
	id 44A135F100237F21 for qemu-devel@nongnu.org;
	Fri, 7 Jul 2006 13:43:52 +0200
Message-ID: <44AE641D.1010608@armiento.net>
Date: Fri, 07 Jul 2006 15:39:41 +0200
From: "R. Armiento" <reply-2006@armiento.net>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] Pentium D with guest Ubuntu 6.06 server kernel panic
	with kqemu
References: <44AD28AA.7050301@armiento.net>
	<22B10AD6-77B0-454C-9719-13E7E19C741B@gmx.de>
In-Reply-To: <22B10AD6-77B0-454C-9719-13E7E19C741B@gmx.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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


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?)

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.

I see; so the issue I reported is in fact the exact same issue as the 
one reported in march. And the situation is that we are waiting for some 
kind soul to implement the monitor/mwait instructions (and according to 
Fabrice in that thread "doing nops should suffice").

(While I am able to boot with idle=halt, I'm still worried that some 
other software than Linux idle function will happen to also use the 
wrongly declared MONITOR feautre and crash the emulated host...)

Best regards,
Rickard