On 05/30/2011 03:20 PM, Ingo Molnar wrote:
How does this work in practice - i thought we memset() all of RAM during guest kernel bootup. That might have changed with the memblock allocator ... So the guest kernel does not touch all of that 64 GB of RAM, so your box wont OOM straight away?
IIRC there never was a memset() of all RAM, at least since kvm started booting Linux. Windows has a zeroing thread which causes all of RAM to be committed shortly after boot, though.
-- error compiling committee.c: too many arguments to function -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
