From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1LUL2N-0005FY-0l
	for qemu-devel@nongnu.org; Tue, 03 Feb 2009 08:09:59 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1LUL2K-0005DV-T1
	for qemu-devel@nongnu.org; Tue, 03 Feb 2009 08:09:58 -0500
Received: from [199.232.76.173] (port=33248 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1LUL2K-0005Cr-Ef
	for qemu-devel@nongnu.org; Tue, 03 Feb 2009 08:09:56 -0500
Received: from pelvoux.gotadsl.co.uk ([81.6.248.91]:50287)
	by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32)
	(Exim 4.60) (envelope-from <lists@pelvoux.nildram.co.uk>)
	id 1LUL2K-0004t2-0k
	for qemu-devel@nongnu.org; Tue, 03 Feb 2009 08:09:56 -0500
Received: from fozzy by ecrins.fosdick.home.net with local (Exim 4.69)
	(envelope-from <lists@pelvoux.nildram.co.uk>) id 1LUL2X-0002eE-NF
	for qemu-devel@nongnu.org; Tue, 03 Feb 2009 13:10:09 +0000
From: Steve Fosdick <lists@pelvoux.nildram.co.uk>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Date: Tue, 03 Feb 2009 13:10:08 +0000
Message-Id: <1233666609.5644.12.camel@ecrins.fosdick.home.net>
Mime-Version: 1.0
Subject: [Qemu-devel] VM stops responding, 100% CPU,
	switching to monitor fails
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 am currently experiencing an issue where the guest VM stops
responding, attempting to switch to the monitor does not do anything
either and the host CPU usage shows as 100% system.

So far the only solution I have found is to kill the qemu process.  A
normal SIGTERM signal seems to be sufficient.

This is with kernel 2.6.28.2, kqmeu 1.3.0~pre11 and qemu 0.9.1.

Do you have any tips on what I can do to get to the bottom of this?

I am thinking as the CPU usage is all system time that there maybe an
infinite loop running within kqemu though I would not know if the loop
was in code that is part of kqemu itself or the guest OS.  If the guest
had got stuck in an infinite loop though I would have hoped the monitor
would still work.

Regards,
Steve.