On Tue, Feb 02, 2016 at 01:15:13PM +, Li, Liang Z wrote:
> > >> We found dom0 will crash when booing on HSW-EX server, the dom0
> > >> kernel version is v4.4. By debugging I found the your patch '
> > >> x86/xen: discard RAM regions above the maximum reservation' , which
> > the commit ID is :
On Tue, Feb 02, 2016 at 01:34:38PM +, David Vrabel wrote:
> On 02/02/16 13:15, Li, Liang Z wrote:
> We found dom0 will crash when booing on HSW-EX server, the dom0
> kernel version is v4.4. By debugging I found the your patch '
> x86/xen: discard RAM regions above the maximum res
On 02/02/16 13:15, Li, Liang Z wrote:
We found dom0 will crash when booing on HSW-EX server, the dom0
kernel version is v4.4. By debugging I found the your patch '
x86/xen: discard RAM regions above the maximum reservation' , which
>> the commit ID is : f5775e0b6116b7e2425ccf535243b2
> >> We found dom0 will crash when booing on HSW-EX server, the dom0
> >> kernel version is v4.4. By debugging I found the your patch '
> >> x86/xen: discard RAM regions above the maximum reservation' , which
> the commit ID is : f5775e0b6116b7e2425ccf535243b21 caused the regression.
> The debug me
> This is a -EBUSY. Is there anything magic about mfn 188d903? It just looks
> like plain RAM in the E820 table.
> Have you got dom0 configured to use linear p2m mode? Without it, dom0 can
> only have a maximum of 512GB of RAM.
> ~Andrew
No special configuration for dom0, actually, the ser
On 02/02/16 10:11, Andrew Cooper wrote:
> On 02/02/16 07:40, Li, Liang Z wrote:
>> Hi David,
>>
>> We found dom0 will crash when booing on HSW-EX server, the dom0 kernel
>> version is v4.4. By debugging I found the your patch
>> ' x86/xen: discard RAM regions above the maximum reservation' , which
On 02/02/16 07:40, Li, Liang Z wrote:
> Hi David,
>
> We found dom0 will crash when booing on HSW-EX server, the dom0 kernel
> version is v4.4. By debugging I found the your patch
> ' x86/xen: discard RAM regions above the maximum reservation' , which the
> commit ID is : f5775e0b6116b7e2425ccf53