From mboxrd@z Thu Jan  1 00:00:00 1970
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: real physical e820 table for dom0?
Date: Mon, 10 Mar 2014 12:27:02 -0400
Message-ID: <20140310162702.GG4262@phenom.dumpdata.com>
References: <A9667DDFB95DB7438FA9D7D576C3D87E0A9FF00D@SHSMSX104.ccr.corp.intel.com>
	<20140306184507.GB9852@localhost.localdomain>
	<A9667DDFB95DB7438FA9D7D576C3D87E0AA0E12B@SHSMSX104.ccr.corp.intel.com>
	<20140307135634.GA9026@phenom.dumpdata.com>
	<A9667DDFB95DB7438FA9D7D576C3D87E0AA10CAF@SHSMSX104.ccr.corp.intel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <konrad.wilk@oracle.com>) id 1WN32l-0001aY-KR
	for xen-devel@lists.xenproject.org; Mon, 10 Mar 2014 16:27:11 +0000
Content-Disposition: inline
In-Reply-To: <A9667DDFB95DB7438FA9D7D576C3D87E0AA10CAF@SHSMSX104.ccr.corp.intel.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: "Zhang, Yang Z" <yang.z.zhang@intel.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>, "'Ian Campbell (Ian.Campbell@citrix.com)'" <Ian.Campbell@citrix.com>, "'Jan Beulich (JBeulich@suse.com)'" <JBeulich@suse.com>
List-Id: xen-devel@lists.xenproject.org

On Mon, Mar 10, 2014 at 08:22:48AM +0000, Zhang, Yang Z wrote:
> Konrad Rzeszutek Wilk wrote on 2014-03-07:
> > On Fri, Mar 07, 2014 at 01:29:31AM +0000, Zhang, Yang Z wrote:
> > 
> > How do you use the dom0_mem_max= argument? And what version of Xen are
> > you using?
> > 
> 
> I tried it both in Xen and dom0, no help. But adding "dom0_mem=4096M,max:4096M" to xen cmdline helps.
> I am using the latest Xen upstream.

Right. That is how it is suppose to work. What did you have before?
dom0_mem=4G?

That means it will boot with all the memory that Xen sees and balloon down to 4GB.

See http://xenbits.xen.org/docs/unstable/misc/xen-command-line.html
> 
> > There was this patch:
> > 
> > commit d3db728125c4470a2d061ac10fa7395e18237263
> > Author: Ian Campbell <Ian.Campbell@citrix.com>
> > Date:   Wed Dec 14 12:16:08 2011 +0000
> > 
> >     xen: only limit memory map to maximum reservation for domain 0.
> >     
> >     d312ae878b6a "xen: use maximum reservation to limit amount of usable
> >     RAM" clamped the total amount of RAM to the current maximum
> >     reservation. This is correct for dom0 but is not correct for guest
> >     domains. In order to
> > boot a guest
> > 
> > Perhaps you don't have it in the hypervisor?
> 
> Hypervisor? I find the patch in dom0.

In the commit it says: d312ae878b6a "xen: use maximum reservation to limit amount of usable.."

That is the hypervisor one.

> 
> Best regards,
> Yang
>