similar to: [PATCH] tests: Provide full path to Unix domain sockets.

On 06/06/2018 01:36 PM, Richard W.M. Jones wrote: > Maybe a bug in libvirt? > https://www.redhat.com/archives/libvir-list/2018-June/msg00490.html Or maybe intentional. Using absolute paths is better than assuming that libvirt will treat relative paths against the same directory as you intended; although it would be nicer if libvirt would reject XML with a relative path up front rather

The nbdkit tests take a long time to run especially on armv7. To try to get an idea of which tests take the most time, and since I happen to have a qemu aarch64 *TCG* guest available, I ran the tests on that guest. A TCG guest is about the worst case for libguestfs, used by some tests, since it uses double-nested TCG, and as you can see below there are tests taking over 6 hours. In fact I

This worked wonderfully!  What are the odds of getting this upstream in the near future?  I'd rather not build from source in production. # ./run guestfish --format=raw --ro -a rbd://[fd00::cefc:1]:6789/images/CentOS-7-x86_64-GenericCloud-1901 libguestfs: trace: set_verbose true libguestfs: trace: set_verbose = 0 libguestfs: trace: set_tmpdir "/root/libguestfs/tmp" libguestfs:

I have scoured the web and can't find anything on the topic: Is IPv6 supported for remote image targets? For example: guestfish --format=raw --ro -a rbd://[fd00::cefc:1]:6789/images/CentOS-7-x86_64-GenericCloud-1901 Does not work citing the following: libguestfs: trace: set_verbose true libguestfs: trace: set_verbose = 0 libguestfs: create: flags = 0, handle = 0x5560231bdfb0, program =

--- docs/nbdkit-captive.pod | 4 ++-- docs/nbdkit-plugin.pod | 2 +- docs/nbdkit-service.pod | 2 +- docs/nbdkit-tls.pod | 2 +- filters/cow/nbdkit-cow-filter.pod | 4 ++-- filters/delay/nbdkit-delay-filter.pod | 2 +- filters/error/nbdkit-error-filter.pod | 6 +++---

--- docs/nbdkit-captive.pod | 4 ++-- docs/nbdkit-plugin.pod | 2 +- docs/nbdkit-service.pod | 2 +- docs/nbdkit-tls.pod | 2 +- filters/cow/nbdkit-cow-filter.pod | 4 ++-- filters/delay/nbdkit-delay-filter.pod | 2 +- filters/error/nbdkit-error-filter.pod | 6 +++---

--- configure.ac | 5 + filters/Makefile.am | 4 + filters/cow/Makefile.am | 65 +++++++ filters/cow/cow.c | 392 ++++++++++++++++++++++++++++++++++++++ filters/cow/nbdkit-cow-filter.pod | 162 ++++++++++++++++ tests/Makefile.am | 6 + tests/test-cow.sh | 98 ++++++++++ 7 files changed, 732

This assumes bashisms, but bash is required to run the tests. This is mostly refactoring. However the changes (simplifications) are quite substantial: - Since the new start_nbdkit helper function cleans up nbdkit on exit, most scripts no longer need to deal with the pid or kill the pid in the cleanup function. - As a result, cleanup functions are radically simpler, and often

A bit of refactoring to the HAVE_LIBGUESTFS conditional, coupled with the addition of a LIBGUESTFS_TESTS intermediate list, allows us to run a few more tests on CentOS 6 (adding some tests of command-line behavior and filters that was previously completely skipped). For the two tests that we can't run, using check_PROGRAMS still causes those programs to try to compile (which leads to compile

I pushed a change which should reduce the time taken in the test-cache-* and test-cow.sh tests. Again note this is double TCG which is the worst case for these tests and explains the excessively long times which wouldn't be seen on a normal build system. Updated results: 01:04:18 PASS: test-readahead 01:02:32 PASS: test-cow.sh 00:37:25 PASS: test-floppy.sh 00:34:57 PASS: test-shell 00:34:53

Avoid a cat+sed for getting the prepared disk name, using a make function instead. --- test-data/phony-guests/Makefile.am | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/test-data/phony-guests/Makefile.am b/test-data/phony-guests/Makefile.am index 5a56960..9fac2d0 100644 --- a/test-data/phony-guests/Makefile.am +++ b/test-data/phony-guests/Makefile.am @@ -70,8 +70,7 @@

Hello libvirt experts, I use libvirt (0.7.5-5ubuntu27.7) with KVM / qemu (0.12.3+noroms-0ubuntu9.2). Some machines use raw images but same use Virtualbox images (.vdi). Since last Ubuntu 10.04 LTS update I can not start the vdi-images. The "driver name= type=" option was new. <devices> <emulator>/usr/bin/kvm</emulator> <disk type='file'

v2: - Make virbr0 configurable. - Fix the tests.

Test case adapted from Hu Zhang's RHBZ#1242853, thanks. --- tests/regressions/Makefile.am | 2 + tests/regressions/rhbz1011907-1165785.sh | 66 ++++++++++++++++++++++++++++++++ 2 files changed, 68 insertions(+) create mode 100755 tests/regressions/rhbz1011907-1165785.sh diff --git a/tests/regressions/Makefile.am b/tests/regressions/Makefile.am index c4f60ae..026987b 100644 ---

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 (annoyingly, guestfs documentation merely states the function was available since 0.3, without saying which later releases added new options); causing a compilation failure during 'make check'. Maybe the guestfs plugin should still be built,

On Fri, Aug 16, 2019 at 10:13 PM John Pierce <jhn.pierce at gmail.com> wrote: > > $ sudo rm -rf / Just for fun, I cloned a C7 VM and ran rm -rf. I then examined the disk image with guestfish. Everything was gone except for a few empty directoriers: /dev, /etc, /proc, /sys, and so on. Jim

Hello, As I understand it guestfs appliances normally work as servers and run high-level commands from some external channel. But it might be possible to bundle a guestfish script to run commands from and do away with the external system. That would make it useful on non-virtualised systems. Has anyone tried this already?

QEMU upstream has broken snapshot=on ... again. These two patches stop using it entirely. Instead we run 'qemu-img create' to create overlay disks as required. Note that the libvirt and UML backends were already doing this: The libvirt backend because <transient/> has never worked, and the UML backend was running uml_mkcow because the UML-equivalent syntax of snapshot=on was

For raw, this allows "off" as a synonym for "sparse" (to make it consistent with qcow2). For qcow2, this allows "sparse" as a synonym for "off". It also adds qcow2 "full" preallocation, which is actually mapped to the qemu option "falloc" (see arguments about this on the qemu-devel mailing list, which we lost). This also updates the

21:51 < foxx> hello! does anyone know if libguestfs supports any sort of COW (copy on write) functionality? for example, if i mount an image which is RO, can i make it write any changes out to a higher dir (such as how overlayfs/aufs works) The answer is yes. Create a qcow2 overlay on top of your image before starting: qemu-img