From: Steve Fosdick <lists@pelvoux.nildram.co.uk>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] VM stops responding, 100% CPU, switching to monitor fails
Date: Tue, 03 Feb 2009 18:12:21 +0000 [thread overview]
Message-ID: <1233684741.10837.2.camel@ecrins.fosdick.home.net> (raw)
In-Reply-To: <13f991410902030911v2472a531j64ef717f955b2bf0@mail.gmail.com>
On Tue, 2009-02-03 at 09:11 -0800, Nathan wrote:
> Hi Steve,
>
> This may be the issue I just posted about. To test, in the host, run
> strace on the qemu process.
>
> If the output shows many SIGALRM signals between fewer calls to
> "clone" which return ERESTARTNOINTR, then it's the same issue and I
> can advise you.
>
> Otherwise, I'm not much help (I'm new to qemu).
>
> regards,
> Nathan Wilcox
Interestingly if I attach to the qemu process with strace the guest VM
starts working again and continues to work after I have stopped the
strace command with control-C.
Here is a sample of what strace was giving:
--- SIGALRM (Alarm clock) @ 0 (0) ---
rt_sigreturn(0x63d24020) = 0
select(16, [11 14 15], [], [], {0, 0}) = 0 (Timeout)
gettimeofday({1233684242, 162854}, NULL) = 0
clock_gettime(CLOCK_MONOTONIC, {87714, 363355675}) = 0
clock_gettime(CLOCK_MONOTONIC, {87714, 363373833}) = 0
clock_gettime(CLOCK_MONOTONIC, {87714, 363390595}) = 0
clock_gettime(CLOCK_MONOTONIC, {87714, 363406519}) = 0
clock_gettime(CLOCK_MONOTONIC, {87714, 363421884}) = 0
timer_gettime(0, {it_interval={0, 0}, it_value={0, 0}}) = 0
timer_settime(0, 0, {it_interval={0, 0}, it_value={0, 952000}}, NULL) =
0
ioctl(10, SPIOCSTYPE or VTXIOCGETINFO, 0x7fffba4f51d0) = 0
ioctl(10, SPIOCSTYPE or VTXIOCGETINFO, 0x7fffba4f51d0) = 0
ioctl(10, SPIOCSTYPE or VTXIOCGETINFO, 0x7fffba4f51d0) = 0
ioctl(10, SPIOCSTYPE or VTXIOCGETINFO, 0x7fffba4f51d0) = 0
ioctl(10, SPIOCSTYPE or VTXIOCGETINFO, 0x7fffba4f51d0) = 0
Regards,
Steve.
prev parent reply other threads:[~2009-02-03 18:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-03 13:10 [Qemu-devel] VM stops responding, 100% CPU, switching to monitor fails Steve Fosdick
2009-02-03 17:11 ` Nathan
2009-02-03 18:12 ` Steve Fosdick [this message]
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=1233684741.10837.2.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).