search for: guestfs_set_progress_callback

This is an updated and extended version of the original patch: https://www.redhat.com/archives/libguestfs/2010-August/msg00163.html This adds OCaml and Perl bindings (both tested), support for progress bars in virt-resize, and adds progress notifications to a number of the simpler commands. Still to do is to add progress messages to more commands. There are still a few commands which would be

...chanism, which you should use in new code if possible. The old functions "guestfs_set_log_message_callback", "guestfs_set_subprocess_quit_callback", "guestfs_set_launch_done_callback", "guestfs_set_close_callback" and "guestfs_set_progress_callback" are no longer documented in this manual page. Handles generate events when certain things happen, such as log messages being generated, progress messages during long-running operations, or the handle being closed. The API calls described below let you regi...

As discussed previously: https://www.redhat.com/archives/libguestfs/2010-July/msg00003.html https://www.redhat.com/archives/libguestfs/2010-July/msg00024.html To do: (1) Implement progress notifications for many more daemon operations. (2) OCaml bindings to the callback. (3) Perl bindings to the callback. Rich. -- Richard Jones, Virtualization Group, Red Hat

From: "Richard W.M. Jones" <rjones at redhat.com> --- configure.ac | 4 ++++ 1 files changed, 4 insertions(+), 0 deletions(-) diff --git a/configure.ac b/configure.ac index fa97479..6e42423 100644 --- a/configure.ac +++ b/configure.ac @@ -141,6 +141,10 @@ if test "$gl_gcc_warnings" = yes; then # Work around warning in src/inspect.c. This seems to be a bug in gcc

The existing mechanism was clunky, slow and used ~ 10 MB of local disk. Rich.

...estfs_set_subprocess_quit_callback (e) appliance launched http://libguestfs.org/guestfs.3.html#guestfs_set_launch_done_callback (f) handle closed http://libguestfs.org/guestfs.3.html#guestfs_set_close_callback (g) progress notification http://libguestfs.org/guestfs.3.html#guestfs_set_progress_callback (a) is not exposed to language bindings because it is required in order to implement error handling and exceptions. (b) is very specialized and is not likely to be used outside specific C programs. The ones I'm interested in here are (c), (d), (e), (f), (g) -- generic events. There are three...

...od2html: -: cannot resolve L<guestfs(3)/PROTOCOL LIMITS> in paragraph 784. /usr/bin/pod2html: -: cannot resolve L<environ(3)> in paragraph 790. /usr/bin/pod2html: -: cannot resolve L<guestfs(3)/PROTOCOL LIMITS> in paragraph 791. /usr/bin/pod2html: -: cannot resolve L<guestfs(3)/guestfs_set_progress_callback> in paragraph 805. /usr/bin/pod2html: -: cannot resolve L<guestfs(3)/guestfs_set_progress_callback> in paragraph 847. /usr/bin/pod2html: -: cannot resolve L<guestfs(3)/guestfs_set_progress_callback> in paragraph 856. /usr/bin/pod2html: -: cannot resolve L<sync(2)> in paragraph...

...od2html: -: cannot resolve L<guestfs(3)/PROTOCOL LIMITS> in paragraph 784. /usr/bin/pod2html: -: cannot resolve L<environ(3)> in paragraph 790. /usr/bin/pod2html: -: cannot resolve L<guestfs(3)/PROTOCOL LIMITS> in paragraph 791. /usr/bin/pod2html: -: cannot resolve L<guestfs(3)/guestfs_set_progress_callback> in paragraph 805. /usr/bin/pod2html: -: cannot resolve L<guestfs(3)/guestfs_set_progress_callback> in paragraph 847. /usr/bin/pod2html: -: cannot resolve L<guestfs(3)/guestfs_set_progress_callback> in paragraph 856. /usr/bin/pod2html: -: cannot resolve L<sync(2)> in paragraph...

...od2html: -: cannot resolve L<guestfs(3)/PROTOCOL LIMITS> in paragraph 784. /usr/bin/pod2html: -: cannot resolve L<environ(3)> in paragraph 790. /usr/bin/pod2html: -: cannot resolve L<guestfs(3)/PROTOCOL LIMITS> in paragraph 791. /usr/bin/pod2html: -: cannot resolve L<guestfs(3)/guestfs_set_progress_callback> in paragraph 805. /usr/bin/pod2html: -: cannot resolve L<guestfs(3)/guestfs_set_progress_callback> in paragraph 847. /usr/bin/pod2html: -: cannot resolve L<guestfs(3)/guestfs_set_progress_callback> in paragraph 856. /usr/bin/pod2html: -: cannot resolve L<sync(2)> in paragraph...

...guestfs_close_cb cb, void *opaque) { + ACQUIRE_LOCK (g); replace_old_style_event_callback (g, close_callback_wrapper, GUESTFS_EVENT_CLOSE, opaque, cb); + RELEASE_LOCK (g); } static void @@ -384,7 +415,9 @@ void guestfs_set_progress_callback (guestfs_h *g, guestfs_progress_cb cb, void *opaque) { + ACQUIRE_LOCK (g); replace_old_style_event_callback (g, progress_callback_wrapper, GUESTFS_EVENT_PROGRESS, opaque, cb); + RELEASE_L...

...od2html: -: cannot resolve L<guestfs(3)/PROTOCOL LIMITS> in paragraph 799. /usr/bin/pod2html: -: cannot resolve L<environ(3)> in paragraph 805. /usr/bin/pod2html: -: cannot resolve L<guestfs(3)/PROTOCOL LIMITS> in paragraph 806. /usr/bin/pod2html: -: cannot resolve L<guestfs(3)/guestfs_set_progress_callback> in paragraph 820. /usr/bin/pod2html: -: cannot resolve L<guestfs(3)/guestfs_set_progress_callback> in paragraph 862. /usr/bin/pod2html: -: cannot resolve L<guestfs(3)/guestfs_set_progress_callback> in paragraph 871. /usr/bin/pod2html: -: cannot resolve L<sync(2)> in paragraph...

...od2html: -: cannot resolve L<guestfs(3)/PROTOCOL LIMITS> in paragraph 799. /usr/bin/pod2html: -: cannot resolve L<environ(3)> in paragraph 805. /usr/bin/pod2html: -: cannot resolve L<guestfs(3)/PROTOCOL LIMITS> in paragraph 806. /usr/bin/pod2html: -: cannot resolve L<guestfs(3)/guestfs_set_progress_callback> in paragraph 820. /usr/bin/pod2html: -: cannot resolve L<guestfs(3)/guestfs_set_progress_callback> in paragraph 862. /usr/bin/pod2html: -: cannot resolve L<guestfs(3)/guestfs_set_progress_callback> in paragraph 871. /usr/bin/pod2html: -: cannot resolve L<sync(2)> in paragraph...

...u cannot call libguestfs APIs from multiple threads: http://libguestfs.org/guestfs.3.html#multiple_handles_and_multiple_threads] Also callers may register a callback function using: typedef void (*guestfs_progress_cb) (guestfs_h *g, void *data, int64_t total, int64_t current); extern void guestfs_set_progress_callback (guestfs_h *g, guestfs_progress_cb cb, void *data); which is called on receipt of a status message. The numbers are reset to (-1, -1) when the final reply is received for a call. The numbers are only meaningful when the handle state is busy (see http://libguestfs.org/guestfs.3.html#guestfs_i...

...od2html: -: cannot resolve L<guestfs(3)/PROTOCOL LIMITS> in paragraph 784. /usr/bin/pod2html: -: cannot resolve L<environ(3)> in paragraph 790. /usr/bin/pod2html: -: cannot resolve L<guestfs(3)/PROTOCOL LIMITS> in paragraph 791. /usr/bin/pod2html: -: cannot resolve L<guestfs(3)/guestfs_set_progress_callback> in paragraph 805. /usr/bin/pod2html: -: cannot resolve L<guestfs(3)/guestfs_set_progress_callback> in paragraph 847. /usr/bin/pod2html: -: cannot resolve L<guestfs(3)/guestfs_set_progress_callback> in paragraph 856. /usr/bin/pod2html: -: cannot resolve L<sync(2)> in paragraph...

...od2html: -: cannot resolve L<guestfs(3)/PROTOCOL LIMITS> in paragraph 799. /usr/bin/pod2html: -: cannot resolve L<environ(3)> in paragraph 805. /usr/bin/pod2html: -: cannot resolve L<guestfs(3)/PROTOCOL LIMITS> in paragraph 806. /usr/bin/pod2html: -: cannot resolve L<guestfs(3)/guestfs_set_progress_callback> in paragraph 820. /usr/bin/pod2html: -: cannot resolve L<guestfs(3)/guestfs_set_progress_callback> in paragraph 862. /usr/bin/pod2html: -: cannot resolve L<guestfs(3)/guestfs_set_progress_callback> in paragraph 871. /usr/bin/pod2html: -: cannot resolve L<sync(2)> in paragraph...

...od2html: -: cannot resolve L<guestfs(3)/PROTOCOL LIMITS> in paragraph 798. /usr/bin/pod2html: -: cannot resolve L<environ(3)> in paragraph 804. /usr/bin/pod2html: -: cannot resolve L<guestfs(3)/PROTOCOL LIMITS> in paragraph 805. /usr/bin/pod2html: -: cannot resolve L<guestfs(3)/guestfs_set_progress_callback> in paragraph 819. /usr/bin/pod2html: -: cannot resolve L<guestfs(3)/guestfs_set_progress_callback> in paragraph 861. /usr/bin/pod2html: -: cannot resolve L<guestfs(3)/guestfs_set_progress_callback> in paragraph 870. /usr/bin/pod2html: -: cannot resolve L<sync(2)> in paragraph...

...od2html: -: cannot resolve L<guestfs(3)/PROTOCOL LIMITS> in paragraph 798. /usr/bin/pod2html: -: cannot resolve L<environ(3)> in paragraph 804. /usr/bin/pod2html: -: cannot resolve L<guestfs(3)/PROTOCOL LIMITS> in paragraph 805. /usr/bin/pod2html: -: cannot resolve L<guestfs(3)/guestfs_set_progress_callback> in paragraph 819. /usr/bin/pod2html: -: cannot resolve L<guestfs(3)/guestfs_set_progress_callback> in paragraph 861. /usr/bin/pod2html: -: cannot resolve L<guestfs(3)/guestfs_set_progress_callback> in paragraph 870. /usr/bin/pod2html: -: cannot resolve L<sync(2)> in paragraph...

...od2html: -: cannot resolve L<guestfs(3)/PROTOCOL LIMITS> in paragraph 798. /usr/bin/pod2html: -: cannot resolve L<environ(3)> in paragraph 804. /usr/bin/pod2html: -: cannot resolve L<guestfs(3)/PROTOCOL LIMITS> in paragraph 805. /usr/bin/pod2html: -: cannot resolve L<guestfs(3)/guestfs_set_progress_callback> in paragraph 819. /usr/bin/pod2html: -: cannot resolve L<guestfs(3)/guestfs_set_progress_callback> in paragraph 861. /usr/bin/pod2html: -: cannot resolve L<guestfs(3)/guestfs_set_progress_callback> in paragraph 870. /usr/bin/pod2html: -: cannot resolve L<sync(2)> in paragraph...

The safe_malloc (etc) functions call g->abort_fn on failure. That's not appropriate for language bindings, and we never intended that these internal functions be used from language bindings, that was just a historical accident. This patch series removes any external use of the safe_* functions. Rich.

...od2html: -: cannot resolve L<guestfs(3)/PROTOCOL LIMITS> in paragraph 784. /usr/bin/pod2html: -: cannot resolve L<environ(3)> in paragraph 790. /usr/bin/pod2html: -: cannot resolve L<guestfs(3)/PROTOCOL LIMITS> in paragraph 791. /usr/bin/pod2html: -: cannot resolve L<guestfs(3)/guestfs_set_progress_callback> in paragraph 805. /usr/bin/pod2html: -: cannot resolve L<guestfs(3)/guestfs_set_progress_callback> in paragraph 847. /usr/bin/pod2html: -: cannot resolve L<guestfs(3)/guestfs_set_progress_callback> in paragraph 856. /usr/bin/pod2html: -: cannot resolve L<sync(2)> in paragraph...