Re: [Xen-devel] 3.2 PVOPs Intel Crash

[Tom Goetz <tom.goetz@xxxxxxxxxxxxxxxxxxx>]

On Jan 18, 2012, at 11:51 AM, Konrad Rzeszutek Wilk wrote:

> On Wed, Jan 18, 2012 at 11:41:22AM -0500, Tom Goetz wrote:
> 
> CC-ing xen-devel and David.
> 
>> We have dom0_mem=672MB for Xen and mem=672MB for linux.
> 
> Ok, if you don't have the mem=X and have the "('x86: use 'dom0_mem' to limit
> the number of pages for dom0') (c/s 23790) in your hypervisor what happens?
> 
> And also have 'dom0_mem=max:672MB' do you get the same issue?

With dom0_mem= and no mem=, it boots fine.

>> 
>> but we have the same mem opt for 2.6.38 and 3.2 and the mem code still has 
>> the e820_remove_range in 3.2. Dom0 is showing the right amount of mem when 
>> booted on other machines, so I don't think the mem= option is failing. 
> 
> The 'mem=X' argument I remember being a work-around. The original bug had 
> been fixed in both
> hypervisor and in the kernel.

I checked with the guy who added the mem= option and he doesn't remember why. I 
going to remove and go from there. Thanks!






_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel