From: Steve Fosdick <lists@pelvoux.nildram.co.uk>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] VM stops responding, 100% CPU, switching to monitor fails
Date: Tue, 03 Feb 2009 13:10:08 +0000 [thread overview]
Message-ID: <1233666609.5644.12.camel@ecrins.fosdick.home.net> (raw)
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.
next reply other threads:[~2009-02-03 13:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-03 13:10 Steve Fosdick [this message]
2009-02-03 17:11 ` [Qemu-devel] VM stops responding, 100% CPU, switching to monitor fails Nathan
2009-02-03 18:12 ` Steve Fosdick
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1233666609.5644.12.camel@ecrins.fosdick.home.net \
--to=lists@pelvoux.nildram.co.uk \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).