xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Mukesh Rathor <mukesh.rathor@oracle.com>
To: Sander Eikelenboom <linux@eikelenboom.it>
Cc: xen-devel@lists.xenproject.org,
	David Vrabel <david.vrabel@citrix.com>,
	Jan Beulich <jbeulich@suse.com>,
	Roger Pau Monne <roger.pau@citrix.com>
Subject: Re: dom0 PVH: Over-allocation for domain 0: 393217 > 393216
Date: Tue, 3 Jun 2014 16:49:49 -0700	[thread overview]
Message-ID: <20140603164949.74f4eab4@mantra.us.oracle.com> (raw)
In-Reply-To: <20140603122827.47f4e1c2@mantra.us.oracle.com>

On Tue, 3 Jun 2014 12:28:27 -0700
Mukesh Rathor <mukesh.rathor@oracle.com> wrote:

> On Tue, 3 Jun 2014 14:11:17 +0200
> Sander Eikelenboom <linux@eikelenboom.it> wrote:
> 
> > Hi,
> > 
> > I just tried booting with "dom0pvh" and found the following warnings
> > (complete combined xl-dmesg/dmesg attached) which don't show up when
> > booting without dom0pvh:
> 
> Yeah, I see. I'm able to reproduce. Something about
> dom0_mem=1536M,max:1536M ie, specifying max in there. Without it,
> dom0_mem=1536M, its fine. You can do that to play around more while I
> take a look.

Ok, I know whats going on. Basically, we are trying to populate the
pfns removed due to punched holes in the e820, but because max is
specified (same as initial ram), guest_physmap_add_page can't add.

This will be fixed by the e820 work that Roger and David Vrabel are 
doing. Please keep an eye on the thread:

http://www.gossamer-threads.com/lists/xen/devel/332603

thanks
Mukesh

  reply	other threads:[~2014-06-03 23:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-03 12:11 dom0 PVH: Over-allocation for domain 0: 393217 > 393216 Sander Eikelenboom
2014-06-03 19:28 ` Mukesh Rathor
2014-06-03 23:49   ` Mukesh Rathor [this message]
2014-06-04 10:48     ` Roger Pau Monné
2014-06-04 17:29       ` Sander Eikelenboom

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=20140603164949.74f4eab4@mantra.us.oracle.com \
    --to=mukesh.rathor@oracle.com \
    --cc=david.vrabel@citrix.com \
    --cc=jbeulich@suse.com \
    --cc=linux@eikelenboom.it \
    --cc=roger.pau@citrix.com \
    --cc=xen-devel@lists.xenproject.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).