On Fri, Jun 24, 2016 at 07:46:23AM +0200, Gerd Hoffmann wrote:
> On Do, 2016-06-23 at 17:18 +0100, Anthony PERARD wrote:
> > On Thu, Jun 23, 2016 at 04:57:54PM +0200, Gerd Hoffmann wrote:
> > > Hi,
> > >
> > > > How could xen_ram_init() find out if the value of max-ram-below-4g is
> > > > the de
On Do, 2016-06-23 at 17:18 +0100, Anthony PERARD wrote:
> On Thu, Jun 23, 2016 at 04:57:54PM +0200, Gerd Hoffmann wrote:
> > Hi,
> >
> > > How could xen_ram_init() find out if the value of max-ram-below-4g is
> > > the default or if a user have set it? Is there another way we could fix
> > > thi
On Thu, Jun 23, 2016 at 04:57:54PM +0200, Gerd Hoffmann wrote:
> Hi,
>
> > How could xen_ram_init() find out if the value of max-ram-below-4g is
> > the default or if a user have set it? Is there another way we could fix
> > this?
>
> Attached patch should fix it. Patch survived a quick smoke
Hi,
> How could xen_ram_init() find out if the value of max-ram-below-4g is
> the default or if a user have set it? Is there another way we could fix
> this?
Attached patch should fix it. Patch survived a quick smoke test on kvm
so far, need to do some more testing tomorrow. Can you give it a
Hi,
> How could xen_ram_init() find out if the value of max-ram-below-4g is
> the default or if a user have set it? Is there another way we could fix
> this?
I guess we'll need a separate variable for that then, something along
the lines of "max-ram-below-4g-default". I'll have a look tomorrow
Hi,
following commit 8156d48 (pc: allow raising low memory via
max-ram-below-4g option), guest under Xen fail to boot. This is due to
the initial value of max-ram-below-4g been change from 4G to 3.5G.
Unfortunately, a Xen guest have a higher default split, at 3.75G, but
can be change via the -mach
