This patch extends the functionality of the max-ram-below-4g option
to also allow increasing lowmem. Use case: Give as much memory as
possible to legacy non-PAE guests.
While being at it also rework the lowmem calculation logic and add a
longish comment describing how it works and what the compat
On Fri, Jan 22, 2016 at 11:51:54AM +0100, Gerd Hoffmann wrote:
> Hi,
>
> > > > I wonder whether we should just bite the bullet and ask management to
> > > > maintain the physical memory map for us, instead of trying to give us
> > > > hints.
> > >
> > > I doubt this simplified things, given the
Hi,
> > > I wonder whether we should just bite the bullet and ask management to
> > > maintain the physical memory map for us, instead of trying to give us
> > > hints.
> >
> > I doubt this simplified things, given the backward compatibility
> > constrains we have.
> >
> > cheers,
> > Gerd
>
On Thu, Jan 21, 2016 at 08:48:53AM +0100, Gerd Hoffmann wrote:
> On Mi, 2016-01-20 at 19:25 +0200, Michael S. Tsirkin wrote:
> > On Wed, Jan 20, 2016 at 03:15:04PM -0200, Eduardo Habkost wrote:
> > > On Wed, Jan 20, 2016 at 01:34:29PM -0200, Eduardo Habkost wrote:
> > > [...]
> > > > Considering th
On Mi, 2016-01-20 at 19:25 +0200, Michael S. Tsirkin wrote:
> On Wed, Jan 20, 2016 at 03:15:04PM -0200, Eduardo Habkost wrote:
> > On Wed, Jan 20, 2016 at 01:34:29PM -0200, Eduardo Habkost wrote:
> > [...]
> > > Considering that we never supported
> > > gigabyte_align && max_ram_below_4g > 3G ||
On Wed, Jan 20, 2016 at 03:15:04PM -0200, Eduardo Habkost wrote:
> On Wed, Jan 20, 2016 at 01:34:29PM -0200, Eduardo Habkost wrote:
> [...]
> > Considering that we never supported
> > gigabyte_align && max_ram_below_4g > 3G ||
> > max_ram_below_4g > 3.5G
> > before, we could simply remove the M
On Wed, Jan 20, 2016 at 01:34:29PM -0200, Eduardo Habkost wrote:
[...]
> Considering that we never supported
> gigabyte_align && max_ram_below_4g > 3G ||
> max_ram_below_4g > 3.5G
> before, we could simply remove the MachineClass::gigabyte_align
> field from pc_piix, and just do the following:
On Wed, Jan 20, 2016 at 03:55:33PM +0100, Gerd Hoffmann wrote:
> Hi,
>
> > > + *qemu -M pc,max-ram-below-4g=2G -m 4G -> 2048M low, 2048M
> > > high
>
> > I assume max-ram-below-4g > 3.5G was unsupported before, and we
> > are breaking compatibility intentionally.
>
> max-ram-below
Hi,
> > + *qemu -M pc,max-ram-below-4g=2G -m 4G -> 2048M low, 2048M high
> I assume max-ram-below-4g > 3.5G was unsupported before, and we
> are breaking compatibility intentionally.
max-ram-below-4g did only reduce memory, so max-ram-below-4g > 3.5G (or
max-ram-below-4g > 3G with
On Fri, Jan 08, 2016 at 01:58:03PM +0100, Gerd Hoffmann wrote:
> This patch extends the functionality of the max-ram-below-4g option
> to also allow increasing lowmem. Use case: Give as much memory as
> possible to legacy non-PAE guests.
>
> While being at it also rework the lowmem calculation lo
On 01/08/2016 05:58 AM, Gerd Hoffmann wrote:
> This patch extends the functionality of the max-ram-below-4g option
> to also allow increasing lowmem. Use case: Give as much memory as
> possible to legacy non-PAE guests.
>
> While being at it also rework the lowmem calculation logic and add a
> lo
On 01/08/2016 02:58 PM, Gerd Hoffmann wrote:
This patch extends the functionality of the max-ram-below-4g option
to also allow increasing lowmem. Use case: Give as much memory as
possible to legacy non-PAE guests.
While being at it also rework the lowmem calculation logic and add a
longish comm
On 01/11/16 09:26, Gerd Hoffmann wrote:
> On Fr, 2016-01-08 at 19:32 +0100, Laszlo Ersek wrote:
>> On 01/08/16 18:45, Igor Mammedov wrote:
>>> On Fri, 8 Jan 2016 13:58:03 +0100
>>> Gerd Hoffmann wrote:
>>>
This patch extends the functionality of the max-ram-below-4g option
to also allow
On Fr, 2016-01-08 at 19:32 +0100, Laszlo Ersek wrote:
> On 01/08/16 18:45, Igor Mammedov wrote:
> > On Fri, 8 Jan 2016 13:58:03 +0100
> > Gerd Hoffmann wrote:
> >
> >> This patch extends the functionality of the max-ram-below-4g option
> >> to also allow increasing lowmem. Use case: Give as muc
On 01/08/16 18:45, Igor Mammedov wrote:
> On Fri, 8 Jan 2016 13:58:03 +0100
> Gerd Hoffmann wrote:
>
>> This patch extends the functionality of the max-ram-below-4g option
>> to also allow increasing lowmem. Use case: Give as much memory as
>> possible to legacy non-PAE guests.
>>
>> While bein
On Fri, 8 Jan 2016 13:58:03 +0100
Gerd Hoffmann wrote:
> This patch extends the functionality of the max-ram-below-4g option
> to also allow increasing lowmem. Use case: Give as much memory as
> possible to legacy non-PAE guests.
>
> While being at it also rework the lowmem calculation logic a
This patch extends the functionality of the max-ram-below-4g option
to also allow increasing lowmem. Use case: Give as much memory as
possible to legacy non-PAE guests.
While being at it also rework the lowmem calculation logic and add a
longish comment describing how it works and what the compat
This patch extends the functionality of the max-ram-below-4g option
to also allow increasing lowmem. While being at it also rework the
lowmem calculation logic and add a longish comment describing how it
works and what the compatibility constrains are.
Signed-off-by: Gerd Hoffmann
---
hw/i386/p
18 matches
Mail list logo