search for: guestfs_set_backend

Thanks Rich. I have used libguestfs for several month. It worked perfectly before, the issue appears recently. I am trying guestfs_set_backend (g, "direct"). Thanks, Allen 2016-08-29 23:31 GMT+08:00 Richard W.M. Jones <rjones@redhat.com>: > On Mon, Aug 29, 2016 at 11:19:04PM +0800, Baochuan Wu wrote: > > Thanks Rich for you quick reply. I enabled logs and the program stuck > > again, here is the call stac...

...main (argc=1, argv=0x7ffd9f6a0288) at fish.c:577 Has anyone seen this? Thanks. Allen 2016-08-30 7:11 GMT+08:00 Baochuan Wu <wildpointercs@gmail.com>: > Thanks Rich. > I have used libguestfs for several month. It worked perfectly before, the > issue appears recently. I am trying guestfs_set_backend (g, "direct"). > > Thanks, > Allen > > 2016-08-29 23:31 GMT+08:00 Richard W.M. Jones <rjones@redhat.com>: > >> On Mon, Aug 29, 2016 at 11:19:04PM +0800, Baochuan Wu wrote: >> > Thanks Rich for you quick reply. I enabled logs and the program stuck &gt...

Thanks Rich for you quick reply. I enabled logs and the program stuck again, here is the call stack and log: Thread 1 (Thread 0x7fac58edc8c0 (LWP 1271)): #0 0x00007fac578fac20 in __poll_nocancel () from /lib64/libc.so.6 #1 0x00007fac56df3c5a in virNetClientIOEventLoop () from /lib64/libvirt.so.0 #2 0x00007fac56df441b in virNetClientSendInternal () from /lib64/libvirt.so.0 #3 0x00007fac56df5843

...estfs.pod b/src/guestfs.pod index f9dea92c81b5805b9011c99d0aa69e0ce687b834..87355d5c9119656e41a3b89f04f687f8fe7fb1f8 100644 --- a/src/guestfs.pod +++ b/src/guestfs.pod @@ -1550,7 +1550,7 @@ such as L<guestfish(1)> with the I<--live> option will "just work". By calling L</guestfs_set_backend> you can change how the library connects to the C<guestfsd> daemon in L</guestfs_launch> (read -L</ARCHITECTURE> for some background). +L</guestfs-internals> for some background). The normal backend is C<direct>, where a small appliance is created containing th...

...ill launch and talk to a daemon (usually ``libvirt --timeout=30'' process, if you are not running as root). Debugging into libvirtd is described here: http://libguestfs.org/guestfs-faq.1.html#debugging-libvirt A workaround is to set LIBGUESTFS_BACKEND=direct [or use the equivalent call ``guestfs_set_backend (g, "direct")''] which will cause libguestfs to run qemu directly instead of going through libvirt. http://libguestfs.org/guestfs.3.html#backend Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog:...

...ically when these two conditions are both met: - You're using the ‘direct’ backend. - Networking is enabled. The direct backend is the default upstream, but not in Fedora/RHEL/CentOS. It might also have been selected if you set the LIBGUESTFS_BACKEND=direct environment variable or called ‘guestfs_set_backend (g, "direct")’. Networking is enabled automatically by some tools (eg. virt-builder), or is enabled if your code called ‘guestfs_set_network (g, 1)’ (which is not the default). Note that the libvirt backend is _not_ affected, for two reasons: (1) It doesn't use SLIRP for networking...

Starting with libguestfs 1.22, "attach methods" will be known as "backends" (one word, no space or hyphen). There are new APIs 'guestfs_set_backend', 'guestfs_get_backend', and a new environment variable 'LIBGUESTFS_BACKEND'. Furthermore, the default backend, running qemu directly, is now called "direct" instead of "appliance". (Note that distros can change the default by compiling with ./configure --w...

This set of patches fixes virt-rescue rather cleanly. In particular the problems with handling ^C are completely fixed. Work still to be done before this can go upstream: - Shutdown doesn't work properly if you exit the shell. At the moment to exit you must do 'reboot -f'. Future improvements: - An escape sequence and escape commands that could be handled by virt-rescue,

This fixes the main issues in virt-rescue and is usable. There are some enhancements which could be made (in follow up work): - An escape sequence and escape commands that could be handled by virt-rescue, eg. to shut down the appliance, mount or unmount filesystems. - `virt-rescue -i' could be implemented cleanly by performing the right API calls before handing control to the

...signal (SIGCHLD, SIG_DFL); g = guestfs_create(); if (g == NULL) { ERROR(PLUGIN_NAME " plugin: failed to create libguestfs handle"); goto cont; //exit(EXIT_FAILURE); } guestfs_set_trace(g,1); //guestfs_set_verbose(g,1); if ( 0 != guestfs_set_backend (g, "direct") ) { ERROR(PLUGIN_NAME " plugin: guestfs_set_backend failed"); } cnt_drives = guestfs_add_domain (g, name, GUESTFS_ADD_DOMAIN_READONLY, 1, -1); if (cnt_drives == -1) { ERROR(PLUGIN_NAME " plugin: failed to get guestfs domain h...

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

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

This supersedes the two previous patch series: https://www.redhat.com/archives/libguestfs/2017-March/msg00017.html https://www.redhat.com/archives/libguestfs/2017-March/msg00046.html Rich.

Version 3: - Tidies up the code further. - Implements correct handling of SIGTSTP and SIGCONT. - Adds: ^] s - sync filesystems - Adds: ^] z - suspend virt-rescue Rich.

v1 was here: https://www.redhat.com/archives/libguestfs/2013-August/msg00005.html This now works, to some extent. The main problem now is that devices are named /dev/ubd[a-] which of course confuses everything. I'm thinking it may be easier to add a udev rule to rename them. Rich.

This is a User-Mode Linux backend for libguestfs. You can select it by doing: export LIBGUESTFS_BACKEND=uml export LIBGUESTFS_QEMU=/path/to/vmlinux Note we're reusing the 'qemu' variable in the handle for convenience. QEmu is not involved when using the UML backend. This almost works. UML itself crashes when the daemon tries to connect to the serial port. I suspect it's

...r (EXIT_FAILURE, errno, "guestfs_create"); + + /* We always run these tests using LIBGUESTFS_BACKEND=direct. It + * may be in future we need to test libvirt as well, in case + * performance issues are suspected there, but so far libvirt has + * not been a bottleneck. + */ + if (guestfs_set_backend (g, "direct") == -1) + exit (EXIT_FAILURE); + + return g; +} + +/* Common function to add the /dev/null drive. */ +static void +add_drive (guestfs_h *g) +{ + if (guestfs_add_drive (g, "/dev/null") == -1) + exit (EXIT_FAILURE); +} + +/* Called when the handle is closed....

v4: - Lots more analysis of the /init script and other parts. - Display a list of the longest to shortest activities. - Rebase on top of current head. Rich.

Hi, this series update libguestfs to a recent gnulib version, so that we can use its new getprogname module, and solve altogether one of the porting issues (the need for 'program_name' by the error module of gnulib), and have a single way to get the name of the current program. A number of changes in tools mostly, although mechanical. Thanks, Pino Toscano (3): Update gnulib to latest

Lots of changes since v2, too much to remember or summarize. Please ignore patch 11/11, it's just for my testing. Rich.