[Libguestfs] [PATCH] tests: Increase appliance memory when testing 256+ disks.

Daniel P. Berrangé berrange at redhat.com
Wed May 16 11:57:13 UTC 2018


On Wed, May 16, 2018 at 12:51:19PM +0100, Richard W.M. Jones wrote:
> Currently the tests fail on x86 with recent kernels:
> 
>   FAIL: test-255-disks.sh
> 
> This confused me for a while because our other test program
> (utils/max-disks/max-disks.pl) reports that it should be possible to
> add 255 disks.
> 
> Well it turns out that the default amount of appliance memory is
> sufficient if you're just adding disks, but if you try to add _and_
> partition those disks there's insufficient memory and the daemon falls
> over with an out of memory error.
> 
> I considered increasing the default appliance memory, and this is
> certainly one way to fix the problem.  However this penalises every
> user for what is a fairly niche use case.  This takes an alternative
> approach of increasing the appliance memory for the affected tests.

I wonder how much it would really penalize users in practice ? KVM doesn't
fault in memory pages unless the guest OS actually touches them. So increasing
the memory size would mean the guest kernel has to allocate a bit more memory
for page tables, but aside from that the extra RAM would be unused unless the
user did some guestfs operation that needed it. Perhaps most likely cause of
using the extra "free" RAM might be page cache in the guest but not sure how
much that comes into play with guestfs operations ?

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|




More information about the Libguestfs mailing list