similar to: Re: Use libguestfs with SAS URI of a disk image

CentOS 6 has libguestfs-devel 1.20.11, which predates the support in guestfs_add_drive_opts() for requesting an nbd drive instead of a local file. The guestfs plugin can still be built, so no configure changes are needed; but skip the tests that fail to compile so that 'make check' can at least complete. Signed-off-by: Eric Blake <eblake@redhat.com> --- Even with this patch,

On Fri, Apr 06, 2018 at 09:02:01AM -0500, Eric Blake wrote: > On 04/06/2018 04:26 AM, Richard W.M. Jones wrote: > > On Thu, Apr 05, 2018 at 03:03:41PM -0500, Eric Blake wrote: > >> CentOS 6 has libguestfs-devel 1.20.11, which predates the support > >> in guestfs_add_drive_opts() for requesting an nbd drive instead > >> of a local file. The guestfs plugin can

On 04/06/2018 04:26 AM, Richard W.M. Jones wrote: > On Thu, Apr 05, 2018 at 03:03:41PM -0500, Eric Blake wrote: >> CentOS 6 has libguestfs-devel 1.20.11, which predates the support >> in guestfs_add_drive_opts() for requesting an nbd drive instead >> of a local file. The guestfs plugin can still be built, so no >> configure changes are needed; but skip the tests that

Test the partition filter against real life partition tables created by sfdisk. --- tests/test-partition.c | 101 --------------------------- README | 2 + tests/Makefile.am | 7 +- tests/test-partition.sh | 148 ++++++++++++++++++++++++++++++++++++++++ 4 files changed, 152 insertions(+), 106 deletions(-) diff --git a/tests/test-partition.c b/tests/test-partition.c

Test the partition filter against real life partition tables created by sfdisk. --- tests/test-partition.c | 101 ------------------------ README | 2 + tests/Makefile.am | 7 +- tests/test-partition1.sh | 165 +++++++++++++++++++++++++++++++++++++++ 4 files changed, 169 insertions(+), 106 deletions(-) diff --git a/tests/test-partition.c b/tests/test-partition.c

On Mon, Jun 29, 2015 at 05:57:38PM +0000, Gabriel Hartmann wrote: > +Snesha Foss <sneshaf@microsoft.com> who is taking over this work. > > It definitely looks like adding the query string to every path is just > wrong. > > I'm not sure I understand why we'd want to parse, deconstruct key value > pairs and then reconstruct the query string from these values and

Add a flag "ConfigOnly" to make sure that some non-daemon-functions should be called only at CONFIG state(RHBZ796520). Signed-off-by: Wanlong Gao <gaowanlong at cn.fujitsu.com> --- generator/generator_actions.ml | 44 ++++++++++++++++++++-------------------- generator/generator_c.ml | 8 ++++++- generator/generator_checks.ml | 1 + generator/generator_types.ml |

On Sat, Mar 14, 2020 at 04:48:24AM +0000, JP Zhang wrote: > HI Richard, > > Thanks for the quick reply. > > The Python program that works, that I mentioned earlier, uses subprocess to issue/run "guestfish" commands below in that order. > /libguestfs/run guestfish --listen -a <https storage-SAS-URL> -- ro > then the Python code exported $PID to the

I'm using qemu-nbd to setup the device with an offset into the image. Using libguestfs version 1.21.22 Code for adding the drive: char *server[] = { "localhost:3000", NULL }; if (guestfs_add_drive_opts (g, "" /* export name - see below */, GUESTFS_ADD_DRIVE_OPTS_FORMAT, "raw", GUESTFS_ADD_DRIVE_OPTS_PROTOCOL, "nbd",

+Snesha Foss <sneshaf@microsoft.com> who is taking over this work. It definitely looks like adding the query string to every path is just wrong. I'm not sure I understand why we'd want to parse, deconstruct key value pairs and then reconstruct the query string from these values and append them to the path selectively. This seems like added complexity for a benefit I don't

Rename the existing tests according to the naming/numbering described in guestfs-hacking(1), and improve the current ones: - guestfs_php_001.phpt: rename to guestfs_020_create.phpt - guestfs_php_003.phpt: rename to guestfs_070_optargs.phpt - guestfs_php_bindtests.phpt: rename to guestfs_090_bindtests.phpt - guestfs_091_version.phpt: new, checks taken from the former guestfs_php_002.phpt -

libguestfs recently added support for virtio-scsi and libvirt, and when these are both available this lets us relatively easily add hotplugging of drives. This email is about how we would present that through the libguestfs API. (a) The current API Currently you have to add drive(s) via guestfs_add_drive* and then call guestfs_launch, ie. your program must look something like this: guestfs_h

Yeswanth, I'm looking at: https://bitbucket.org/swamiyeswanth/pyti/src/2b3a7401eccf/diskhandler.py from this thread: http://librelist.com/browser//pyti/2011/6/13/disk-handler/ (1) I don't think the code you posted will work unless you move line 23 ('launch') up to just after you've added the drive (after line 12). (2) You probably don't want to use 'add_drive'.

It's possible through the API to do a sequence of calls like this: g = guestfs_create (); guestfs_add_drive (g, "foo"); guestfs_launch (g); guestfs_shutdown (g); guestfs_launch (g); # relaunch the handle The question is, what should be the state of the handle at the second launch? Would the verbose flag still be set if it had been set earlier? (I think fairly

There's a new syntax check rule from gnulib. It requires that you write e.g., exit (EXIT_SUCCESS), not exit (0). And the same for 1/EXIT_FAILURE and any other constants. There were a lot of violations, including a few false positives, so I started with the exemptions (see the .x-sc file below). Then I converted the vast majority automatically, with this: maint: use EXIT_SUCCESS and

I saw the latest parrot release notice on LWN this week and randomly wondered the Perl6 native call interface was like compared to the horrific mess that is Perl5 XS. The answer is that it is a thing of beauty ! Here is the libguestfs hello world example in Perl6 $ dd if=/dev/zero of=guest.img bs=1M count=100 $ mke2fs guest.img $ cat guestfs.p6 use NativeCall; say "Defining stubs";

On Thu, Jun 25, 2015 at 06:44:50PM +0000, Gabriel Hartmann wrote: > I have written a patch (please see attached) which fixes both of these bugs: > > https://bugzilla.redhat.com/show_bug.cgi?id=1092583 > https://bugzilla.redhat.com/show_bug.cgi?id=1232477 > > By default, when saving a URI using xmlSaveUri it escapes everything in the > URI. QEMU doesn't want anything

From: "Richard W.M. Jones" <rjones@redhat.com> NULL means that libvirt gets to guess what connection URI we meant. Currently it guesses qemu:///session for non-root and qemu:///system for root. Except if LIBVIRT_DEFAULT_URI is set in which case this is used even if it's not appropriate. Except if Xen is installed in which case it guesses xen:/// which is not helpful at all.

On Tue, Jun 16, 2015 at 07:45:35PM +0000, Gabriel Hartmann wrote: > I'm trying to read the contents of a remote vhd and running into some > problems. I suspect the issue has to do with the inclusion of a SAS key in > the url. Does anyone have any experience with this, or recommendations on > where to begin looking to make a fix? > > Here's the verbose (debug) log and

This can be used for creating temporary disks to thin clients, as a kind of "remote tmpfs". See also: https://www.redhat.com/archives/libguestfs/2020-March/msg00134.html --- plugins/data/nbdkit-data-plugin.pod | 1 + plugins/file/nbdkit-file-plugin.pod | 1 + plugins/linuxdisk/nbdkit-linuxdisk-plugin.pod | 7 +- plugins/memory/nbdkit-memory-plugin.pod |