* Asias He wrote:
> On 05/11/2011 11:17 PM, levinsasha...@gmail.com wrote:
> > From: Sasha Levin
> >
> > e820 is expected to leave a memory gap within the low 32
> > bits of RAM space. From the documentation of e820_setup_gap():
> > /*
> > * Search for the biggest gap in the low 32 bits of th
On 05/11/2011 11:17 PM, levinsasha...@gmail.com wrote:
> From: Sasha Levin
>
> e820 is expected to leave a memory gap within the low 32
> bits of RAM space. From the documentation of e820_setup_gap():
> /*
> * Search for the biggest gap in the low 32 bits of the e820
> * memory space. We pass
* levinsasha...@gmail.com wrote:
> @@ -225,7 +266,18 @@ struct kvm *kvm__init(const char *kvm_dev, unsigned long
> ram_size)
>
> self->ram_size = ram_size;
>
> - self->ram_start = mmap(NULL, ram_size, PROT_READ | PROT_WRITE,
> MAP_PRIVATE | MAP_ANONYMOUS | MAP_NORESERVE,
On Wed, 11 May 2011, Ingo Molnar wrote:
Ok, with your fixes applied i can boot a 10 GB RAM guest just fine - both the
hang and the later IO errors and IO corruptions are gone:
[root@aldebaran ~]# free
total used free sharedbuffers cached
Mem: 10019972
From: Sasha Levin
e820 is expected to leave a memory gap within the low 32
bits of RAM space. From the documentation of e820_setup_gap():
/*
* Search for the biggest gap in the low 32 bits of the e820
* memory space. We pass this space to PCI to assign MMIO resources
* for hotplug or unconfig
* Ingo Molnar wrote:
> I'll test your series.
Ok, with your fixes applied i can boot a 10 GB RAM guest just fine - both the
hang and the later IO errors and IO corruptions are gone:
[root@aldebaran ~]# free
total used free sharedbuffers cached
Mem:
