qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Marcin Gibuła" <m.gibula@beyond.pl>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Unresponsive linux guest once migrated
Date: Wed, 02 Apr 2014 12:18:21 +0200	[thread overview]
Message-ID: <533BE3ED.8070305@beyond.pl> (raw)
In-Reply-To: <20140402093938.GB2586@work-vm>

On 02.04.2014 11:39, Dr. David Alan Gilbert wrote:
> * Marcin Gibu??a (m.gibula@beyond.pl) wrote:
>>> Can you give:
>>>    1) A backtrace from the guest
>>>       thread apply all bt full
>>>       in gdb
>>
>> You mean from gdb attached to hanged guest? I'll try to get it. From
>> what I remember it looks rather "normal" - busy executing guest
>> code.
>
> yes; if you can send it a sysrq to trigger a backtrace it might also
> be worth a try - I'm just trying to find what the guest is really doing
> when it's apparentyly 'hung'.

IIRC VM doesn't respond to sysrq key sequence. It doesn't respond to 
anything actually but NMI. I tried to do inject-nmi. VMs kernel 
responded with timestamped message "Uhhuh. NMI received. Dazed and 
confused, but trying to continue". That timestamp never changes - its 
like time is frozen on VM.

I'll try to find my notes from this gdb session.

-- 
mg

  reply	other threads:[~2014-04-02 10:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-27 22:52 [Qemu-devel] Unresponsive linux guest once migrated Chris Dunlop
2014-03-27 23:29 ` Marcin Gibuła
2014-03-27 23:59   ` Chris Dunlop
2014-03-31  8:39     ` Marcin Gibuła
2014-04-02  5:41       ` Chris Dunlop
2014-04-02  8:45         ` Marcin Gibuła
2014-04-02  9:04           ` Dr. David Alan Gilbert
2014-04-02  9:30             ` Marcin Gibuła
2014-04-02  9:39               ` Dr. David Alan Gilbert
2014-04-02 10:18                 ` Marcin Gibuła [this message]
2014-04-02 17:05                 ` Marcin Gibuła

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=533BE3ED.8070305@beyond.pl \
    --to=m.gibula@beyond.pl \
    --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).