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 10:45:52 +0200 [thread overview]
Message-ID: <533BCE40.8060908@beyond.pl> (raw)
In-Reply-To: <20140402054144.GA31323@onthe.net.au>
> It's looking good so far, after a few migrations (it takes a while to test
> because I'm waiting at least 5 hours between migrations). I'll be happier
> once I've done a couple of weeks of this without any failures!
Does anyone have any hints how to debug this thing? :(
I've tried to put hanged guest under gdb and found it's looped deep
inside kernel time management functions. Disabling kvmclock suggests it
is somehow related to its corruption during migration. It happens on
both old and new versions of guest kernels.
Any hints from developers are welcome:)
--
mg
next prev parent reply other threads:[~2014-04-02 8:46 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 [this message]
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
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=533BCE40.8060908@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).