search for: e2ee1b5

On Wed, Jun 10, 2015 at 06:47:44PM +0200, Pino Toscano wrote: > index e2ee1b5..eebab53 100644 > --- a/src/guestfs.pod > +++ b/src/guestfs.pod > @@ -3540,6 +3540,30 @@ Finally, the child process sends asynchronous messages back to the > main program, such as kernel log messages. You can register a > callback to receive these messages. > > +=head1 FIX...

...ompiled appliance, as also described in +L<guestfs(3)/FIXED APPLIANCE>. + +For pre-compiled appliances, see also: +L<http://libguestfs.org/download/binaries/appliance/>. Patches to port supermin to more Linux distros are welcome. diff --git a/src/guestfs.pod b/src/guestfs.pod index e2ee1b5..eebab53 100644 --- a/src/guestfs.pod +++ b/src/guestfs.pod @@ -3540,6 +3540,30 @@ Finally, the child process sends asynchronous messages back to the main program, such as kernel log messages. You can register a callback to receive these messages. +=head1 FIXED APPLIANCE + +When libguestfs (or...

On Monday 15 June 2015 15:47:31 Richard W.M. Jones wrote: > On Wed, Jun 10, 2015 at 06:47:44PM +0200, Pino Toscano wrote: > > index e2ee1b5..eebab53 100644 > > --- a/src/guestfs.pod > > +++ b/src/guestfs.pod > > @@ -3540,6 +3540,30 @@ Finally, the child process sends asynchronous messages back to the > > main program, such as kernel log messages. You can register a > > callback to receive these messages...

...<guestfs(3)/FIXED APPLIANCE>. + +You can find pre-compiled appliances already prepared by the +libguestfs team at +L<http://libguestfs.org/download/binaries/appliance/>. Patches to port supermin to more Linux distros are welcome. diff --git a/src/guestfs.pod b/src/guestfs.pod index e2ee1b5..eebab53 100644 --- a/src/guestfs.pod +++ b/src/guestfs.pod @@ -3540,6 +3540,30 @@ Finally, the child process sends asynchronous messages back to the main program, such as kernel log messages. You can register a callback to receive these messages. +=head1 FIXED APPLIANCE + +When libguestfs (or...

This patch isn't ready to go upstream. In fact, I think we might do a quick 1.30 release soon, and save this patch, and also the extensive changes proposed for the test suite[1], to after 1.30. Currently it is not safe to use the same handle from multiple threads, unless you implement your own mutexes. See: http://libguestfs.org/guestfs.3.html#multiple-handles-and-multiple-threads These

...mp> is on tmpfs, or if you use C<TMPDIR=/dev/shm>), tmpfs defaults to a maximum size of I<half> of physical RAM. If virt-sparsify exceeds this, it will hang. The solution is either to use a real disk, or to increase the maximum diff --git a/src/guestfs.pod b/src/guestfs.pod index e2ee1b5..0068183 100644 --- a/src/guestfs.pod +++ b/src/guestfs.pod @@ -140,8 +140,8 @@ cause disk corruption, but adding it read-only is safe. You should usually add at least one disk image, and you may add multiple disk images. If adding multiple disk images, they usually have to be "related&quo...