similar to: Libguestfs with Perl 6 :-)

On Wed, May 06, 2015 at 08:42:09AM +0800, fu lirong wrote: > （1） make quickcheck > > works well ,after the command the terminal shows: > > ===== TEST FINISHED OK ===== That's good. > (2) what your program does ( I executed ./autogen.sh 、 ./configure 、 > make 、 make check as I mentioned before , when I execute make check ,there > is something wrong and I

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 -

Hi there, perl6 offers with the NativeCall package a great tool to implement other languages into perl scripts. This has already been done with python, C(++) and perl5. For my use cases - lots of data munging and statistical analyses (climatology/meteorology) - it would be perfect to parse data and call/run models from perl6 and then to do plotting and analyses in R. I saw R does have some

Like with the previous commit, this replaces instances of: if (something_bad) { fprintf (stderr, "%s: error message\n", guestfs_int_program_name); exit (EXIT_FAILURE); } with: if (something_bad) error (EXIT_FAILURE, 0, "error message"); (except in a few cases were errno was incorrectly being ignored, in which case I have fixed that). It's slightly

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

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

guestfs_list_filesystems uses mount/umount to discover btrfs sub-volumes and since 1.37 it generates random mountpoint so it will longer affect already mounted filesystems if either. --- generator/actions_core.ml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/generator/actions_core.ml b/generator/actions_core.ml index ed8cb16..9a695c0 100644 --- a/generator/actions_core.ml

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 |

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

The existing test of language bindings was not covering any use of NBD_CMD_WRITE_ZEROES, making it harder to test changes to the plugin's zero callback. Recent Linux kernels are now smart enough to turn fallocate(2) with FALLOC_FL_ZERO_RANGE into a SCSI WRITE SAME request, which qemu in turn converts into an NBD_CMD_WRITE_ZEROES. Since libguestfs does not directly have an API for this, we

Richard- > On Mon, Feb 09, 2015 at 08:27:22AM -0600, Jeff Brower wrote: >> Yes we know that it doesn't know. We'd be ok to re-launch the image >> to pick up changes except for the time it takes (if we could get >> into 1 to 10 msec range it would be ok). > > There's no feasible way to start a Linux kernel in under about 1-2 > seconds. It just takes

Move the list_filesystems API into the daemon, reimplementing it in OCaml. Since this API makes many other API calls, it runs a lot faster in the daemon. --- daemon/Makefile.am | 2 + daemon/ldm.ml | 3 + daemon/ldm.mli | 2 + daemon/listfs.ml | 156 +++++++++++++++++++++++++++++ daemon/listfs.mli | 19 ++++ daemon/lvm.ml | 3 +

Update: Using mount (read-only) and unmount commands in a script that loops continuously, we are able to see near instantaneous file modifications (less than 0.5 sec) performed on a Win7 live guest. We have to use the sync.exe utility (technet.microsoft.com/en-us/sysinternals/bb897438.aspx), otherwise changes are not visible for 10-20 sec. We tested sync.exe with our libguestfs test program

On Wed, Jul 17, 2013 at 04:43:34PM +0300, Or Goshen wrote: > Hi, > > When I register a callback for events with this function call: > eh = guestfs_set_event_callback(g, message_callback, GUESTFS_EVENT_ALL, 0, > dev); > > Shouldnt it capture and redirect messages like this to message_callback(): > "libguestfs: error: lstat: /.Trash: No such file or directory"

Well, I get these error messages during the execution of guestfs_mount_local_run(). What can I do then ? On Wed, Jul 17, 2013 at 5:08 PM, Richard W.M. Jones <rjones@redhat.com>wrote: > On Wed, Jul 17, 2013 at 04:43:34PM +0300, Or Goshen wrote: > > Hi, > > > > When I register a callback for events with this function call: > > eh = guestfs_set_event_callback(g,

On 06/09/2016 03:18 PM, Pino Toscano wrote: > In data mercoledì 1 giugno 2016 02:04:33, Maros Zatko ha scritto: >> --autosysroot option uses suggestions to user on how to mount filesystems >> and change root suggested by --suggest option in virt-rescue. > IMHO it should be called -i, like in the other tools, as what > --autosysroot does is basically the same. We can call it

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'.

https://bugzilla.redhat.com/show_bug.cgi?id=836710 https://bugzilla.redhat.com/show_bug.cgi?id=836913 There are at least two related bugs going on: (1) Linux sync(2) system call doesn't send a write barrier to the disk, so in effect it doesn't force the hard disk to flush its cache. libguestfs used sync(2) to force changes to disk. We didn't expect that qemu was caching anything

In data mercoledì 1 giugno 2016 02:04:33, Maros Zatko ha scritto: > --autosysroot option uses suggestions to user on how to mount filesystems > and change root suggested by --suggest option in virt-rescue. IMHO it should be called -i, like in the other tools, as what --autosysroot does is basically the same. > Commands are passed on kernel command line in format >

Richard- > On Mon, Feb 09, 2015 at 08:01:31AM -0600, Jeff Brower wrote: >> Richard- >> >> > On Sun, Feb 08, 2015 at 12:11:37PM -0600, Jeff Brower wrote: >> >> With continuous loop testing, what we found is that we have to shut >> >> down and re-launch the image handle to see changes on the Win7 live >> >> guest. Unfortunately image