search for: libguestfs_memsize

...pecially compute or RAM intensive. If you are > > running many parallel conversions, then you may consider allocating > > -one CPU core and between 512 MB and 1 GB of RAM per running instance. > > +one CPU core and 2 GB of RAM per running instance. > > I guess pointing to LIBGUESTFS_MEMSIZE here could make it more > actionable on issues. OK, I will tweak this documentation. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-df lists disk usage of guests without needin...

...about 1 GB of RAM to decrypt the block device, which is considerably larger than the default available in the libguestfs appliance. To make it possible to open these encrypted disks we need to make the appliance larger. This could be done as a one-off, and the current workaround is simply to set LIBGUESTFS_MEMSIZE=2048 or a similar amount. However since we don't know in advance whether we could be dealing with an encrypted disk, partition, etc. or what PBKDF it uses, the only way to deal with this in all circumstances is to increase the default memsize. This commit increases it quite a lot (768 -> 1...

On Wednesday, 16 May 2018 14:43:09 CEST Richard W.M. Jones wrote: > With recent Linux kernels, adding and partitioning 255 disks causes > the appliance to run out of memory. This causes a test failure in > tests/disks/test-255-disks.sh. This change gives the appliance enough > memory to complete the test. TBH raising the amount of memory only for those tests is the solution IMHO,

Use %d to parse them as int (since the variables for them as int) instead of %u, even if they both need to be at least > 0. --smp was already checked to be >= 1 while --memsize not, so check that the specified memory size is not < 128 (which is semi-arbitrary, but enough as a minimum threshold). --- rescue/rescue.c | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-)

In commit 08f82f2e3d6975b72340dd59f438862e152a15ef we increased the memory size to 800MB (on x86) so that the semodule command would work. However it has been discovered that another SELinux command takes large amounts of RAM (setfiles during the SELinux relabel step). Therefore increase the memory size again, this time to 2000MB. --- v2v/v2v.ml | 2 +- v2v/virt-v2v.pod | 2 +- 2 files

These three patches (for discussion only, NOT to be applied) implement a mutex system that lets the user limit the number of libguestfs instances that can be launched per host. There are two uses that I have identified for this: firstly so we can enable parallel-tests (the default in automake >= 1.13) without blowing up the host. Secondly oVirt has raised concerns about how to limit the

...> Virt-v2v is not especially compute or RAM intensive. If you are > running many parallel conversions, then you may consider allocating > -one CPU core and between 512 MB and 1 GB of RAM per running instance. > +one CPU core and 2 GB of RAM per running instance. I guess pointing to LIBGUESTFS_MEMSIZE here could make it more actionable on issues. Thanks, -- Pino Toscano -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: This is a digitally signed message part. URL: <http://listman.redhat.com...

I wonder why not to set required amount of memory using guestfs_set_memsize or setting LIBGUESTFS_MEMSIZE environment variable just for this test? -- +380979184774 Mykola Ivanets ср, 23 трав. 2018 о 11:28 Pino Toscano <ptoscano@redhat.com> пише: > On Wednesday, 16 May 2018 14:43:09 CEST Richard W.M. Jones wrote: > > With recent Linux kernels, adding and partitioning 255 disks...

...versatilepb -cpu arm926" (3) The versatilepb emulated system only supports memory < 512MB, and will only boot the standard kernel, so when running you need something like this: FEBOOTSTRAP_KERNEL=/boot/vmlinuz-3.3.4-4.fc17.armv7hl \ FEBOOTSTRAP_MODULES=/lib/modules/3.3.4-4.fc17.armv7hl \ LIBGUESTFS_MEMSIZE=256 \ LIBGUESTFS_DEBUG=1 \ make check (4) Currently this will fail because the virtio-pci driver doesn't work on ARM. The characteristic stack trace starts with: [ 4.841052] [<c0230a08>] (vp_reset+0x14/0x64) from [<c022fa48>] (register_virtio_device+0x4c/0x94) [ 4.844047] [...

Hi everyone, lately I've been getting familiar with library and working on slight re-layering of the library. It's about having locking layer in public API and tracing one layer below that (let's call it __t_ layer. I'm not very good at making up names, so this is temporary:) ). Then making sure that all generated public stuff call __t_ layer and all other internal stuff

Split up the huge generator/actions.ml into several smaller files. Rich.