On Thu, 17 Apr 2014 14:17:37 +0800
Hu Tao wrote:
> max ram shouldn't exceed unused memory range above 4g
> (UINT64_MAX - 0x1 - above_4g_mem_size), that is:
"max_ram" is not amount of RAM after initial RAM, but rather
RAM limit including initial RAM.
There should be check at somewhere in
On Wed, Apr 16, 2014 at 04:23:44PM +0200, Igor Mammedov wrote:
> On Wed, 16 Apr 2014 16:59:25 +0800
> Hu Tao wrote:
>
> > On Fri, Apr 04, 2014 at 03:36:38PM +0200, Igor Mammedov wrote:
> > > initialize and map hotplug memory address space container
> > > into guest's RAM address space.
> > >
> >
On Wed, 16 Apr 2014 16:59:25 +0800
Hu Tao wrote:
> On Fri, Apr 04, 2014 at 03:36:38PM +0200, Igor Mammedov wrote:
> > initialize and map hotplug memory address space container
> > into guest's RAM address space.
> >
> > Signed-off-by: Igor Mammedov
> > ---
> > hw/i386/pc.c | 19 +++
On Fri, Apr 04, 2014 at 03:36:38PM +0200, Igor Mammedov wrote:
> initialize and map hotplug memory address space container
> into guest's RAM address space.
>
> Signed-off-by: Igor Mammedov
> ---
> hw/i386/pc.c | 19 +--
> include/hw/i386/pc.h | 10 ++
> 2 files c
initialize and map hotplug memory address space container
into guest's RAM address space.
Signed-off-by: Igor Mammedov
---
hw/i386/pc.c | 19 +--
include/hw/i386/pc.h | 10 ++
2 files changed, 27 insertions(+), 2 deletions(-)
diff --git a/hw/i386/pc.c b/hw/i386/p
