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: Mon, 29 Aug 2011 15:49:11 -0400	[thread overview]
Message-ID: <20110829194911.GC16530@dumpdata.com> (raw)
In-Reply-To: <4E57D745.2080701@leuphana.de>

On Fri, Aug 26, 2011 at 07:26:29PM +0200, Andreas Olsowski wrote:
> >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.
> It would certainly be interesting to know if you experience the same
> thing on your platforms. This may or may not have sth to do with the
> hardware in play.

OK, got my box online.

Getting closer to trying to reproduce the problem.

> 
> 
> >
> >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?
> 
> Allthough i am willing, i probably wont be able to, since i lack the
> neccessary understanding of the low level workings of Xen and i am
> not very experienced at debugging C code/programs.

OK.
> 
> 
> However i did some additional testing, this time with xen4.2 and
> things have gotten worse:

Yeah, xen-unstable past c/s 23379 is doing a lot of weird stuff for me.

> 
> The two servers involved do BOTH have 96GB ram and are both running
> the latest xen 4.2 but are of different hardware (R710 and R610):
> http://pastebin.com/AaSpWZdg
> 
> And this is happens when i throw a 32GB server (PE2950) in the mix:
> http://pastebin.com/7X8t022R
> 
> So with 4.2 there are still migration errors, but whats worse, now i
> cant migrate anything anywhere anymore when the platform is
> different.
> 
> Within the same platform everything works fine (2x R610):
> http://pastebin.com/ZWByjjY5
> 
> What is going on here?

<sigh> Development - and not all developers test everything in the
mix.

  reply	other threads:[~2011-08-29 19:49 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
2011-08-26 17:26           ` Andreas Olsowski
2011-08-29 19:49             ` Konrad Rzeszutek Wilk [this message]
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=20110829194911.GC16530@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.