From: Andrey Korolyov <andrey@xdel.ru>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] qemu process stuck in Rl state
Date: Thu, 18 Sep 2014 15:21:08 +0400 [thread overview]
Message-ID: <CABYiri9ypZW+oKwK3ofk-v9r+YVO54sqCUfoEJFS1w6LPN3Yqw@mail.gmail.com> (raw)
In-Reply-To: <20140918104922.GF8847@stefanha-thinkpad.redhat.com>
On Thu, Sep 18, 2014 at 2:49 PM, Stefan Hajnoczi <stefanha@gmail.com> wrote:
> On Wed, Sep 17, 2014 at 11:56:57PM +0400, Andrey Korolyov wrote:
>> I`ve faced an issue with qemu VMs with very large uptime spans - half
>> of year or so. They are hanging in running state forever and are not
>> killable in any imaginable fashion. Tried to freeze it via freezer cg
>> without any luck. VM itself went unresponsive with zero cpu
>> consumption after reaching 'forever running' point.
>>
>> I am going to reset the host in a couple of hours, so any timed ideas
>> for debugging this state will be very appreciated.
>
> A couple of shots at figuring out what the process is doing:
>
> cat /proc/$PID/stack
> cat /proc/$PID/syscall
> gdb $PID
> (gdb) thread apply all bt
Thanks Stefan,
of course any attempts to attach to the process or dump core failed at
very beginning. I compared proc contents with live VM and found
nothing suspicious. The question is about what I should try to do
facing supposedly kernel bug, if no possibility to determine which
code is currently executing by emulator is available. Also if it may
help, both affected VMs on different hosts has a simular process
uptime (from end of May). Just to repeat - the process is not reacting
to any signal, have zero CPU consumption immediately after bug
appearance and therefore cannot be stopped/frozen.
next prev parent reply other threads:[~2014-09-18 11:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-17 19:56 [Qemu-devel] qemu process stuck in Rl state Andrey Korolyov
2014-09-18 10:49 ` Stefan Hajnoczi
2014-09-18 11:21 ` Andrey Korolyov [this message]
2014-09-24 8:54 ` Stefan Hajnoczi
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=CABYiri9ypZW+oKwK3ofk-v9r+YVO54sqCUfoEJFS1w6LPN3Yqw@mail.gmail.com \
--to=andrey@xdel.ru \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
/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).