search for: libguestfs_attach_method

...8. Fedora 18 defaults to using the libvirt attach-method, meaning that libvirt is used to create and manage the libguestfs appliance. There are several benefits to this (see the full release notes). You can switch back to the ordinary method (directly running qemu) at any time by doing: export LIBGUESTFS_ATTACH_METHOD=appliance There is a bug in libvirt (or perhaps libnl, or somewhere else) which causes libvirtd to segfault occasionally: https://bugzilla.redhat.com/show_bug.cgi?id=875741 You will need selinux-policy >= 3.11.1-63.fc18 and libvirt >= 0.10.2.1-3.fc18 in order to use SELinux in Enforcing m...

Run with LIBGUESTFS_ATTACH_METHOD=appliance Fails with: inspect_os: mount_ro: /dev/sda on / (options: 'ro'): mount: /dev/sda is already mounted or /sysroot busy at /usr/share/perl5/vendor_perl/Sys/VirtConvert/GuestfsHandle.pm line 194. virt-inspector works as expected libguestfs-test-tool.log: http://pastebin.c...

Just a note [possibly more of a warning] that I'm intending to switch the default backend in Fedora 18+ to libvirt this week. For more information about what this means, see: https://rwmj.wordpress.com/2012/07/23/new-in-libguestfs-use-libvirt-to-launch-the-appliance/#content Barring any bugs, the change ought to be transparent. The reasons why we're making this change in Fedora are:

...LIBGUESTFS_HV would replace usage of > /usr/libexec/qemu-kvm with /root/work/qemu-wrapper, but does not > appear to OK I think the problem is that it's libguestfs 1.20, where the environment variable names are different (check guestfs(3) in your local copy). This should work: export LIBGUESTFS_ATTACH_METHOD=appliance export LIBGUESTFS_QEMU=/root/work/qemu-wrapper There's an additional problem which is you need the wrapper to distinguish between -help and -version tests and the final command. Use a wrapper like this: ---------------------------------------------------------------------- #!/bin/...

...ame problem if you use read-only tools on running guests, such as virt-df, virt-inspector, virt-cat, etc., as root. There are two workarounds possible in the short term: (1) To continue using libguestfs to inspect disks, ensure the following environment variable is set everywhere: export LIBGUESTFS_ATTACH_METHOD=appliance (eg. by putting that line into /etc/profile.d/local.sh and logging out). Note that this disables sVirt protection in libguestfs, even if SELinux is enabled. (2) OR do: yum uninstall python-libguestfs This will disable the inspection features of virt-manager....

...virt"). FWIW there are three backends (same as before): - direct (a.k.a. appliance): Run qemu directly - libvirt: Manage the appliance with libvirt - unix: Connect to a Unix socket (for libguestfs live) For backwards compatibility, the old APIs continue to be supported, along with the LIBGUESTFS_ATTACH_METHOD environment variable, and the synonym "appliance" instead of "direct". Because these are part of the C API they will be supported forever, but you can get a warning about using them by compiling with -DGUESTFS_WARN_DEPRECATED=1. See this large but mostly mechanical patch: htt...

Sometimes guestfsd fails to gather info, and the virt-<tool> -v output is usually not useful to figure out whats going on within the temporary guest. I see the /init script has support to run guestfsd with a debug tool, which is currently valgrind. Granted, valgrind support is a compile time thing. What would be a good way to optionally run guestfsd with strace or gdb? Should each tool get a

So I am getting this error on Fed18 virt-v2v trying to convert libvirtxml to Rhev 3.1 NFS Export domain: 'iface' parameter is not supported by the libvirt attach-method at /usr/share/perl5/vendor_perl/Sys/VirtConvert/GuestfsHandle.pm line 96. Which is mentioned in this bug: https://bugzilla.redhat.com/show_bug.cgi?id=895898 and this one:

...face' parameter is not supported by the libvirt attach-method at /usr/share/perl5/vendor_perl/Sys/VirtConvert/GuestfsHandle.pm line 96. This issue was previously mentioned in this thread: https://www.redhat.com/archives/libguestfs/2013-February/msg00057.html, and a workaround of 'export LIBGUESTFS_ATTACH_METHOD=appliance' was suggested. However, as mentioned in the bug, this parameter is likely no longer required. Unless there is a use-case where this setting is required, it seems like a good idea to remove it completely (which should work in either libvirt or direct mode), rather than recommend th...

...39;direct' backend, and ensure maximum libguestfs debugging is -# written to the *.log files in case there is a problem. +# Use the 'direct' backend, and ensure maximum libguestfs and libnbd +# debugging is written to the *.log files in case there is a problem. TESTS_ENVIRONMENT += \ LIBGUESTFS_ATTACH_METHOD=appliance \ LIBGUESTFS_DEBUG=1 \ LIBGUESTFS_TRACE=1 \ + LIBNBD_DEBUG=1 \ $(NULL) # Common test library. diff --git a/tests/test-error0.sh b/tests/test-error0.sh index fe97354..de9dca2 100755 --- a/tests/test-error0.sh +++ b/tests/test-error0.sh @@ -34,7 +34,7 @@ source ./functions.sh set...

Hello, I have been looking at the "virt-df" libguestfs tool to get guest-level disk used/free statistics - specifically with Qemu-KVM/Openstack. This works great for a few Openstack instances, but when I begin to scale (even to ~30 instances/guests) the performance really takes a hit. The time it takes for the command to complete seems to scale linearly with the amount of guests/domains

I am unable to convert a vm using virt-v2v. From the trace and debug logs I am unable to understand the cause of the problem. I assume it is a permission or configuration issue but I don't know where to start looking. The following command was issued: LIBGUESTFS_TRACE=1 LIBGUESTFS_DEBUG=1 virt-v2v -ic qemu+ssh://xxx at 192.168.xxx.xxx/system -o rhev -os 192.168.xxx.xxx:/mnt/exports -of

[Let's keep this on the mailing list] On Thu, Jul 31, 2014 at 02:48:25PM -0700, Zetan Drableg wrote: > Hi Richard, > I created qemu-wrapper: > #!/bin/bash -x > > exec gdbserver :1234 /usr/libexec/qemu-kvm "$@" gdbserver will end up debugging the qemu process, not the guest inside. This is not useful. You need to do something like: exec /usr/libexec/qemu-kvm -s

Hi everyone, lately I've been getting familiar with library and working on slight re-layering of the library. It's about having locking layer in public API and tracing one layer below that (let's call it __t_ layer. I'm not very good at making up names, so this is temporary:) ). Then making sure that all generated public stuff call __t_ layer and all other internal stuff

...--- You can also read the release notes online at: http://libguestfs.org/guestfs-release-notes.1.html RELEASE NOTES FOR LIBGUESTFS 1.20 New features libvirt and sVirt (SELinux confinement) You can optionally use libvirt to launch and manage the backend appliance by: * setting LIBGUESTFS_ATTACH_METHOD=libvirt[:URI] * using ./configure --with-default-attach-method=libvirt[:URI] * or calling the API method guestfs_set_attach_method SVirt (SELinux confinement) is used to secure the libguestfs appliance, if the libvirt backend is selected. virtio-scsi, larger number of driv...

Very much a work in progress as there are still many tests using qemu-io which are candidates for conversion. You'll notice at the end of test-full.sh that the new test has some duplicated code which looks as if it ought to be refactored into a Python function. When I tried to do that, I got loads of strange Python problems which may indicate bugs in nbdsh itself or problems with my

v3 was here: https://www.redhat.com/archives/libguestfs/2019-November/msg00209.html In v4: - Rebase on top of current master. Includes various fixes and updates required because of Nir's patches that went into master. - Fix api_version() -> API_VERSION in patch 2 noted previously on the mailing list. Rich.

v2 was here: https://www.redhat.com/archives/libguestfs/2019-November/msg00163.html I pushed patch 1 (with spelling fix), patch 4 and patch 5 since those were previously ACKed on the list. Differences in v3: - Add error checking to PyModule_AddIntConstant. - Use API_VERSION constant instead of function. - Add max API version supported to --dump-plugin output. - Print API_VERSION selected by

Also available here: https://github.com/rwmjones/nbdkit/tree/2020-windows-mingw-nolib After a lot of work I have made the port to Windows work without using a separate library. Instead, on Windows only, we build an "import library" (library of stubs) which resolves references to nbdkit_* functions in the main program and fixes up the plugin, basically the first technique outlined in