On Tue, Mar 21, 2017 at 01:01:44PM +0100, Juergen Gross wrote:
> On 21/03/17 11:05, Jan Beulich wrote:
> On 21.03.17 at 06:14, wrote:
> >> On 20/03/17 20:03, Alex Thorlton wrote:
> >>> Hey everyone,
> >>>
> >>> Recently, I've been working with Boris Ostrovsky to get Xen running on
> >>> some
On 21/03/17 11:05, Jan Beulich wrote:
On 21.03.17 at 06:14, wrote:
>> On 20/03/17 20:03, Alex Thorlton wrote:
>>> Hey everyone,
>>>
>>> Recently, I've been working with Boris Ostrovsky to get Xen running on
>>> some of our larger systems, and we've run into a few problems with the
>>> amount
>>> On 21.03.17 at 06:14, wrote:
> On 20/03/17 20:03, Alex Thorlton wrote:
>> Hey everyone,
>>
>> Recently, I've been working with Boris Ostrovsky to get Xen running on
>> some of our larger systems, and we've run into a few problems with the
>> amount of space that Xen sets aside for the E820 ma
>>> On 20.03.17 at 20:03, wrote:
> --- xen.orig/arch/x86/e820.c
> +++ xen/arch/x86/e820.c
> @@ -134,7 +134,7 @@ static struct change_member *change_poin
> static struct e820entry *overlap_list[E820MAX] __initdata;
> static struct e820entry new_bios[E820MAX] __initdata;
>
> -static int __init sa
On 20/03/17 20:03, Alex Thorlton wrote:
> Hey everyone,
>
> Recently, I've been working with Boris Ostrovsky to get Xen running on
> some of our larger systems, and we've run into a few problems with the
> amount of space that Xen sets aside for the E820 map.
>
> The first problem that I hit was
Hey everyone,
Recently, I've been working with Boris Ostrovsky to get Xen running on
some of our larger systems, and we've run into a few problems with the
amount of space that Xen sets aside for the E820 map.
The first problem that I hit was that E820MAX is far too small, at 128
entries, for the
