All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olaf Hering <olaf@aepfle.de>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Re: migration of pv guest fails from small to large host
Date: Thu, 7 Jul 2011 23:02:25 +0200	[thread overview]
Message-ID: <20110707210225.GA32628@aepfle.de> (raw)
In-Reply-To: <20110707183624.GA16619@dumpdata.com>

On Thu, Jul 07, Konrad Rzeszutek Wilk wrote:

> On Thu, Jul 07, 2011 at 06:20:42AM -0700, Olaf Hering wrote:
> > On Tue, Jul 05, Konrad Rzeszutek Wilk wrote:
> > 
> > > On Fri, Jul 01, 2011 at 06:20:23PM +0200, Olaf Hering wrote:
> > > > 
> > > > The situation with Linux 3.0 is different, crashes on target. With SLES11
> > > > kernel I can not attach to the console, the guest is appearently running.
> > > 
> > > What happens if you 'xl save', 'xl restore' on the same machine? Does that work?
> > 
> > save/restore on the same system works, just any form of transit from
> > small to large fails.
> 
> I am not sure what 'small' to 'large' means in this context? As in the
> migration from a machine with less memory than than the other? What happens
> if you migratte the other way? Does it work if you use the old style 'xm' commands?

xm or xl make no difference, they call the same helper function.
If the guest is started on a large system (>64GB), then migrated to a
small system (<64GB) and back to the large system nothing bad happens.
But if the guest is started on the small system, then migrated to the
large system the guest either crashes or hangs, depending on the guest
kernel. So far I have no handle what actually happens. Doing a dump
fails because the p2m stuff is not yet configured by the guest.

Today I wrote some debug code to get some tracing info, which I need to
test.

Olaf

  reply	other threads:[~2011-07-07 21:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-01 10:41 migration of pv guest fails from small to large host Olaf Hering
2011-07-01 16:20 ` Olaf Hering
2011-07-05 13:46   ` Konrad Rzeszutek Wilk
2011-07-07 13:20     ` Olaf Hering
2011-07-07 18:36       ` Konrad Rzeszutek Wilk
2011-07-07 21:02         ` Olaf Hering [this message]
2011-07-12 16:43 ` [PATCH] xen: update machine_to_phys_order on resume Olaf Hering
2011-07-12 18:11   ` [Xen-devel] " Konrad Rzeszutek Wilk
2011-07-13  9:12     ` Ian Campbell
2011-07-13 13:20       ` Konrad Rzeszutek Wilk
2011-07-15  8:56         ` Jan Beulich
2011-07-15 16:05       ` Jan Beulich

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=20110707210225.GA32628@aepfle.de \
    --to=olaf@aepfle.de \
    --cc=konrad.wilk@oracle.com \
    --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.