similar to: trouble compiling libguestfs 1.17.21

[Please remember to post all questions on the mailing list] On Thu, Mar 08, 2012 at 09:41:19PM +0700, Tho Huynh wrote: > Can I mount the guest's file system into a folder/path (mountpoint) > in the host machine using guestfish? No, but you don't need to. > And accessing that folder equal to accessing the guest's file > system. What I'm trying to do is to copy a file

Hello all, I am having an issue with guestmount in respect to live instances and I was hoping someone might have an idea where I've gone wrong. The following output is from my shell session, if there's any more information needed please let me know and I'll happily provide it. [root at longitude ~]# virt-filesystems -d F16-rawhide/dev/sda2 /dev/sda3 [root at longitude ~]#

On Wed, Mar 07, 2012 at 05:57:45AM -0800, THO HUYNH wrote: > I tried to copy file from host to the running guest after I had > mounted the guest but it`s seemed slow. The speed is about 6-8 > MB/s. I thought it would be the same with real hard drive (about > 20MB/s). Is this using 'guestmount --live'? Unfortunately FUSE is inefficient, particularly the way we implement it in

Add a new api restorecon to restore file(s) default SELinux security contexts. Signed-off-by: Wanlong Gao <gaowanlong at cn.fujitsu.com> --- daemon/selinux.c | 69 + generator/actions.ml | 25 + gobject/Makefile.inc | 6 +- po/POTFILES | 2 + src/MAX_PROC_NR | 2 +- 21 files changed, 13282 insertions(+), 28030 deletions(-) diff --git

hi Mr Rich As you recommended, I switched to Fedora 16. I also built a guest machine with Fedora 16 Mini version. Inside the guest I? installed libguestfs-live-service package but I failed? to start the guestfsd daemon : ??? [root at Fedora16 ~]# guestfsd -vr ??? verbose daemon enabled ??? linux commmand line: BOOT_IMAGE=/vmlinuz-3.2.7-1.fc16.i686.PAE root=/dev/mapper/vg_fedora16-lv_root ??? ro

Users select a virtual machine on their current libvirt host. They then select a target machine, which must have been previously configured as a connection. They confirm the migration and then it runs. Signed-off-by: Darryl L. Pierce <dpierce at redhat.com> --- nodeadmin/addhost.py | 10 ++++- nodeadmin/libvirtworker.py | 6 +++ nodeadmin/migratedomain.py | 81

From: "Richard W.M. Jones" <rjones at redhat.com> --- configure.ac | 4 ++++ 1 files changed, 4 insertions(+), 0 deletions(-) diff --git a/configure.ac b/configure.ac index fa97479..6e42423 100644 --- a/configure.ac +++ b/configure.ac @@ -141,6 +141,10 @@ if test "$gl_gcc_warnings" = yes; then # Work around warning in src/inspect.c. This seems to be a bug in gcc

We have extended collectd virt plugin to extract info about disk usage from a libvirt domain using libguestfs. We have had several issues with it which were raised here in 2018 by Peter Dimitrov. Currently the collectd plugin works fine and retrieves the required statistics. Current collectd configuration says that interval of reading statistics (interval of calling all plugins read functions) is

Signed-off-by: Wanlong Gao <gaowanlong at cn.fujitsu.com> --- po/POTFILES | 39 +++++++++++++++++++++++++++++++++++++++ 1 file changed, 39 insertions(+) diff --git a/po/POTFILES b/po/POTFILES index 2b4b586..789279a 100644 --- a/po/POTFILES +++ b/po/POTFILES @@ -131,6 +131,45 @@ fish/time.c fish/virt.c format/format.c fuse/guestmount.c +gobject/guestfs-gobject-optargs-add_domain.c

This series of patches aim to make adding disks from libvirt domains easy through the core API. These two new APIs allow you to add the disks from a libvirt domain. The higher level add-domain API takes the name of the libvirt domain as a string and connects to libvirt itself. The lower level add-libvirt-dom API relies on the program to connect to libvirt and pass the virDomainPtr into the API

These patches are a distillation of the good patches from the previous large / for-discussion-only error handling patch. See: https://www.redhat.com/archives/libguestfs/2009-November/msg00298.html Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones virt-df lists disk usage of guests without needing to install any software inside the virtual machine.

This patch series adds support for outputing an ext2-based appliance from febootstrap-supermin-helper. The usage is very simple, you just add '-f ext2' flag and the name of the appliance file that you want to write to. The implementation uses libext2fs, which is a very low level way to create ext2 filesystems from scratch. We'd like to use libguestfs, but that's an obvious

The gobject bindings generate a large number of header files, which pollute /usr/include when installed. This patch moves them all into a guestfs-gobject/ subdirectory. guestfs-gobject.h remains in the same place. This change also moves generated source files into src/, because it makes the gobject directory a bit tidier. --- generator/Makefile.am | 3 +

This series of patches prepares the way for a later series which will add write support for Windows Registry 'hive' files to our 'hivex' mini library. About hivex: http://libguestfs.org/hivex.3.html About the Windows Registry: Forget it - there are no reliable references. However the Wikipedia page explains some of the top level concepts:

The internal_yara_scan runs the Yara engine with the previously loaded rules against the given file. For each rule matching against the scanned file, a struct containing the file name and the rule identifier is returned. The gathered list of yara_detection structs is serialised into XDR format and written to a file. Signed-off-by: Matteo Cafasso <noxdafox@gmail.com> --- daemon/yara.c

The internal_yara_scan runs the Yara engine with the previously loaded rules against the given file. For each rule matching against the scanned file, a struct containing the file name and the rule identifier is returned. The gathered list of yara_detection structs is serialised into XDR format and written to a file. Signed-off-by: Matteo Cafasso <noxdafox@gmail.com> --- daemon/yara.c

The internal_yara_scan runs the Yara engine with the previously loaded rules against the given file. For each rule matching against the scanned file, a struct containing the file name and the rule identifier is returned. The gathered list of yara_detection structs is serialised into XDR format and written to a file. Signed-off-by: Matteo Cafasso <noxdafox@gmail.com> --- daemon/yara.c

The internal_yara_scan runs the Yara engine with the previously loaded rules against the given file. For each rule matching against the scanned file, a struct containing the file name and the rule identifier is returned. The gathered list of yara_detection structs is serialised into XDR format and written to a file. Signed-off-by: Matteo Cafasso <noxdafox@gmail.com> --- daemon/yara.c

Thank you, Rich, This was the issue indeed. export LIBGUESTFS_BACKEND=direct fixed it. The next step I tried was to integrate libguestfs in collectd virt plugin to collect this data automatically. In this case I'm having an unknown error in add_libvirt_dom() (same with add_domain) when it's invoking qemu-img to create overlay image. There is no difference between manual and service

NOTE: This is HIGHLY EXPERIMENTAL and can eat babies ... Modify the guest libvirt XML to add the virtio-serial channel: <channel type='unix'> <source mode='bind' path='/tmp/socket'/> <target type='virtio' name='org.libguestfs.channel.0'/> </channel> In the guest, compile guestfsd and run it like this: sudo