All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Andreas Olsowski <andreas.olsowski@leuphana.de>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: xen/stable-2.6.32.x xen-4.1.1 live migration	fails with kernels 2.6.39, 3.0.3 and 3.1-rc2
Date: Fri, 26 Aug 2011 11:00:54 -0400	[thread overview]
Message-ID: <20110826150054.GA1793@dumpdata.com> (raw)
In-Reply-To: <4E55F682.8060405@leuphana.de>

On Thu, Aug 25, 2011 at 09:15:14AM +0200, Andreas Olsowski wrote:
> 
> > Which sounds like the patch above should have fixed. Again, did you
> > check your binary and source tree to see if you have the mentioned
> > patch?
> 
> Yes at the time i tested it the patch was in 4.1-testing and 4.2, so
> i do have the patch applied. It had the desired effect, i can
> migrate TO the host with more RAM, but i still cannot migrate guests
> that have been created on it FROM that host.

Ok, so you do have a workaround for that right now - and we kind of
know that is something still amiss with the MFN calculations when
migrating.

My todo list is not getting any shorter sadly so not sure when I will
get to try this out. But let me do that when I get my 32GB machine
working again.

> 
> I can however create the guest somewhere else, migrate it there and
> then migrate it back.

Yeah, that really points to either the tools not liking the
MFN being too high or the hypervisor. Or the save/resume path in the
Linux kernel is failing silently and sticking in invalid MFNs
as it can't deal with higher MFNs.

In other words - need to run this to figure out.

Unless you are up for helping out by debugging the code a bit and
seeing if you can come with a fix?

  reply	other threads:[~2011-08-26 15:00 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-19 17:56 xen/stable-2.6.32.x xen-4.1.1 live migration fails with kernels 2.6.39, 3.0.3 and 3.1-rc2 Andreas Olsowski
2011-08-22  7:32 ` Jan Beulich
2011-08-22 13:56   ` Andreas Olsowski
2011-08-24 20:34     ` Konrad Rzeszutek Wilk
2011-08-25  7:15       ` Andreas Olsowski
2011-08-26 15:00         ` Konrad Rzeszutek Wilk [this message]
2011-08-26 17:26           ` Andreas Olsowski
2011-08-29 19:49             ` Konrad Rzeszutek Wilk
2011-08-31 13:07               ` Andreas Olsowski
2011-09-07 13:50                 ` Konrad Rzeszutek Wilk
2011-09-08 17:32                   ` Konrad Rzeszutek Wilk
2011-09-08 18:12                     ` Konrad Rzeszutek Wilk
2011-09-08 19:50                       ` Konrad Rzeszutek Wilk
2011-09-09  5:59                         ` Andreas Olsowski
2011-09-12 16:47                           ` xen/stable-2.6.32.x xen-4.1.1 live migration fails with kernels 2.6.39, 3.0.3 and 3.1-rc2.. between different physical machines and CPUs Konrad Rzeszutek Wilk
     [not found]                         ` <19825_1315548082_p8961G08009635_4E69AB53.5010702@leuphana.de>
2011-09-09  9:18                           ` xen/stable-2.6.32.x xen-4.1.1 live migration fails with kernels 2.6.39, 3.0.3 and 3.1-rc2 Andreas Olsowski
     [not found] <1676_1313776768_p7JHxMh3027661_4E4EA3E2.2040809@leuphana.de>
2011-08-20  2:37 ` Andreas Olsowski
     [not found] ` <1676_1313808015_p7K2e91M024610_4E4F1DFC.2000909@leuphana.de>
2011-08-20  3:49   ` Andreas Olsowski

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=20110826150054.GA1793@dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=andreas.olsowski@leuphana.de \
    --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.