[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] real physical e820 table for dom0?
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@xxxxxxxxxx> > > 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 > _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |