similar to: Options for hotplugging

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

On 27/02/16 11:23, Richard W.M. Jones wrote: > [...] >>>> md_create: feature 'mdadm' is not available in this >>>> build of libguestfs. Read 'AVAILABILITY' in the guestfs(3) man page for >>>> how to check for the availability of features. at /home/noxdafox/development/libguestfs/test-data/phony-guests/make-fedora-img.pl >>>> line

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 -

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";

This rounds off hotplugging support by allowing you to add and remove drives at any stage (before and after launch). Rich.

This is, I guess, version 3 of this patch series which adds disk labels and hotplugging (only hot-add implemented so far). The good news is .. it works! Rich.

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

On Sat, Feb 27, 2016 at 09:55:32PM +0200, noxdafox wrote: > On 27/02/16 11:23, Richard W.M. Jones wrote: > >[...] > >>>>md_create: feature 'mdadm' is not available in this > >>>>build of libguestfs. Read 'AVAILABILITY' in the guestfs(3) man page for > >>>>how to check for the availability of features. at

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,

So far the failure of some test would have not reported a non-zero return value by run-tests.php. Since now all the PHP tests pass, we can ask for failures to be fatal, by exporting REPORT_EXIT_STATUS=1 for run-tests.php. --- php/run-php-tests.sh | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/php/run-php-tests.sh b/php/run-php-tests.sh index 6f9ae10..e498987 100755 ---

I think calling "sh" before "mount" should not confuse guestfish like that: # guestfish (1.20.4 on sles11sp3) Welcome to guestfish, the libguestfs filesystem interactive shell for editing virtual machine filesystems. Type: 'help' for help on commands 'man' to read the manual 'quit' to quit the shell ><fs> add-drive

Replace the monolithic 'test-max-disks.pl' script with a test program written in C. The program is completely equivalent to the old script, except for the enhancement that it is able to detect if disks are added to the appliance in the wrong order. The tests themselves are split out into some shell scripts: - test-27-disks: Fully tests 27 disks. This is the minimum supported

Hi all, I've disabled cgroups v1 on my system with the kernel boot option "systemd.unified_cgroup_hierarchy=1". Since doing so, USB hotplugging fails to work, seemingly due to a permissions problem with BPF. Please note that the technique I'm going to describe worked just fine for hotplugging USB devices to running domains until this change. Attaching / detaching USB devices

On Mon, Jan 20, 2020 at 09:00:15PM +0100, Pol Van Aubel wrote: > Hi, > > Quoting Pavel Hrdina (2020-01-20 14:29:36) > > On Sat, Jan 18, 2020 at 11:17:11PM +0100, Pol Van Aubel wrote: > > > Hi all, > > > > > > I've disabled cgroups v1 on my system with the kernel boot option > > > "systemd.unified_cgroup_hierarchy=1". Since doing

Hello Richard, One more question, you mentioned that "hot plugging" is supported from *CentOS 7 *and gave me a link. That link says "In libguestfs ≥ 1.20, you may add drives and remove after calling "guestfs_launch" <http://libguestfs.org/guestfs.3.html#guestfs_launch>. There are some restrictions, see below. This is called*hotplugging*." When I executed

[For a bug noted earlier by both Matt Booth and Jim Meyering] If you use the guestfs_add_drive function, then currently it generates a qemu command line element like: -drive ...,cache=off,... This causes qemu to try to open the device with O_DIRECT. Unfortunately some filesystems don't support this flag, notably tmpfs, which means you can't use libguestfs in conjunction with tmpfs.

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

If we're given an ISO image as the source of virtio windows drivers, and the backend supports hot-adding drives, reuse the same guestfs handle that is open for accessing the guest being inspected, rather than creating a new one (which would run another virtual machine instance and is fairly resource-intensive). Signed-off-by: Roman Kagan <rkagan@virtuozzo.com> --- changes since v1: -

Unfortunately I do need to use the address explicitly as opposed to hostnames because the source of the data fed here is Ceph's monmap which returns the addresses explicitly. I've tried all the common ways to escape the : in the v6 address to no avail.  I definitely agree that the problem looks to be it parsing the colons as if the port comes next and then everything after that is

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