From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Nathan March <nathan@gt.net>
Cc: xen-devel@lists.xensource.com
Subject: Re: Live migration bug introduced in 2.6.32.16?
Date: Thu, 27 Jan 2011 15:36:09 -0500 [thread overview]
Message-ID: <20110127203609.GC4194@dumpdata.com> (raw)
In-Reply-To: <4D41D3BA.7090602@gt.net>
On Thu, Jan 27, 2011 at 12:21:14PM -0800, Nathan March wrote:
> Hi All,
>
> It looks like a live migration bug may have been introduced in 2.6.32.16...
Whoa.. nice job figuring out what is wrong. One question: did you
try to use the git branch from Jeremy's tree as a DomU?
> Anyone have any ideas on what might be going on here or how I can
> debug it further? I'm completely stumped at this point, don't want
> to just try applying every patch in 2.6.32.16 to see which one is
> doing it. Compiling + testing all these kernels is time consuming =)
git bisect is a great tool for this. You can fetch Linus's tree and
the tools for this - takes only about a day to find the culprit.
next prev parent reply other threads:[~2011-01-27 20:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-27 20:21 Live migration bug introduced in 2.6.32.16? Nathan March
2011-01-27 20:36 ` Konrad Rzeszutek Wilk [this message]
2011-01-27 20:42 ` Nathan March
2011-01-27 20:57 ` Ian Campbell
2011-01-27 22:54 ` Nathan March
2011-01-27 23:27 ` Konrad Rzeszutek Wilk
2011-01-28 8:53 ` Pasi Kärkkäinen
2011-01-28 0:51 ` Nathan March
2011-01-28 6:47 ` Philipp Hahn
2011-01-28 8:44 ` Ian Campbell
2011-01-28 18:44 ` Nathan March
2011-02-04 14:17 ` Ian Campbell
2011-02-04 14:46 ` [Xen-devel] " Greg KH
2011-02-04 14:51 ` Ian Campbell
2011-02-16 21:47 ` Greg KH
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=20110127203609.GC4194@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=nathan@gt.net \
--cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.