All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Keir Fraser <keir@xensource.com>
Cc: xen-devel@lists.xensource.com, Steven Hand <Steven.Hand@cl.cam.ac.uk>
Subject: Re: 3.0.5 rc3 paravirt save failures ?
Date: Tue, 1 May 2007 14:04:07 +0100	[thread overview]
Message-ID: <20070501130407.GA3995@redhat.com> (raw)
In-Reply-To: <C25CF8C9.E333%keir@xensource.com>

On Tue, May 01, 2007 at 02:01:45PM +0100, Keir Fraser wrote:
> On 1/5/07 13:47, "Steven Hand" <Steven.Hand@cl.cam.ac.uk> wrote:
> 
> > Looks like you're running off the top of the p2m ; your domain has 800Mb
> > 'maxmem' and hence should have a p2m covering 800 + 8 (slack) = 808Mb.
> > However entry 206868 is for the physical page just beyond that.
> > 
> > Can you check the value you're getting for p2m_size in xc_domain_save.c,
> > e.g. apply the following?
> 
> And is your Xen precisely matched against libxc? I fixed XENMEM_maximum_gpfn
> to really return the last gpfn known to the guest, rather than the last plus
> one. Hence we now add one to that value to get p2m_size in xc_domain_save().
> But if this fixed xc_domain_save() was run against older Xen, you would have
> p2m_size too big by one.

Ahh, that could well be the problem. It looks like my HV / libxc are just
straddling your changeset :-(

Dan.
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=| 

  reply	other threads:[~2007-05-01 13:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-01 11:55 3.0.5 rc3 paravirt save failures ? Daniel P. Berrange
2007-05-01 12:47 ` Steven Hand
2007-05-01 13:01   ` Keir Fraser
2007-05-01 13:04     ` Daniel P. Berrange [this message]
2007-05-01 15:01   ` Daniel P. Berrange
2007-05-01 15:09     ` Keir Fraser

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=20070501130407.GA3995@redhat.com \
    --to=berrange@redhat.com \
    --cc=Steven.Hand@cl.cam.ac.uk \
    --cc=keir@xensource.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.