search for: guestfs_rsync_out

All- Per this page https://rwmj.wordpress.com/2013/04/22/using-rsync-with-libguestfs/ We are trying to get the libguestfs API guestfs_rsync_out to work. We’ve tried combinations similar to: guestfs_rsync_out(g, “/HostShared”, “rsync://root@10.0.1.90:2999/backup/ -av”, -1) surrounding it with APIs as in the recipe examples, for example replacing libguestfs_cat(), with no luck. In the above example the "backup" rsync module na...

Richard- >>> Per this page >>> >>> https://rwmj.wordpress.com/2013/04/22/using-rsync-with-libguestfs/ >>> >>> We are trying to get the libguestfs API guestfs_rsync_out to work. We’ve tried combinations similar to: >>> >>> guestfs_rsync_out(g, “/HostShared”, “rsync://root@10.0.1.90:2999/backup/ -av”, -1) >>> >>> surrounding it with APIs as in the recipe examples, for example replacing libguestfs_cat(), with no luck. In the &g...

On Sat, Feb 07, 2015 at 05:19:42PM -0600, Jeff Brower wrote: > All- > > Per this page > > https://rwmj.wordpress.com/2013/04/22/using-rsync-with-libguestfs/ > > We are trying to get the libguestfs API guestfs_rsync_out to work. We’ve tried combinations similar to: > > guestfs_rsync_out(g, “/HostShared”, “rsync://root@10.0.1.90:2999/backup/ -av”, -1) > > surrounding it with APIs as in the recipe examples, for example replacing libguestfs_cat(), with no luck. In the above > example the "bac...

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 re-launch takes time, 3-5 sec (the image > size is 50 GByte). I'm assuming this is because libguestfs makes an > internal copy of filesystem, and

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 that long for the kernel to initialize

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

...h requirement (which takes 3-5 sec due to loading the appliance Linux kernel), would be greatly appreciated. There are many reasons why using libguestfs is a better solution for us in the long run. Thanks. -Jeff ---------------- Original Message --------------- Subject: Re: [Libguestfs] getting guestfs_rsync_out to work From: "Jeff Brower" <jbrower@signalogic.com> Date: Mon, February 9, 2015 3:39 pm To: "Richard W.M. Jones" <rjones@redhat.com> Cc: libguestfs@redhat.com ------------------------------------------------- Richard- > On Mon, Feb 09, 2015 at 0...

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 re-launch takes time, 3-5 sec (the image

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

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 re-launch takes time, 3-5 sec (the image >> size is 50 GByte). I'm assuming this is because libguestfs makes an >>

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