search for: libguestfs_hv

I was going to post this as a patch, but I realize the patch is just working around an actual bug in the libvirt backend [not in libvirt]. Anyway, posting it here so we don't forget about it. Rich.

On 16.09.14 15:09, Richard W.M. Jones wrote: > On Tue, Sep 16, 2014 at 05:06:57PM +0300, Shahar Havivi wrote: > > I am using upstream qemu while using this local variables: > > export PATH=/home/shahar/git/qemu:$PATH > > export LIBGUESTFS_HV=/home/shahar/git/qemu/x86_64-softmmu/qemu-system-x86_64 > > > > Is that sufficient? > > Yup, upstream qemu should work fine. Or even the qemu in Fedora Rawhide. Build the latest qemu, set the PATH and LIBGUESTFS_HV variables and still got the error, any idea? -----------------...

...in our qemu-kvm-rhev yet (see rhvirt-patches for > current status), but I have a patched version of qemu here: > > https://www.redhat.com/archives/libguestfs/2014-May/msg00090.html I am using upstream qemu while using this local variables: export PATH=/home/shahar/git/qemu:$PATH export LIBGUESTFS_HV=/home/shahar/git/qemu/x86_64-softmmu/qemu-system-x86_64 Is that sufficient? > > > If reporting bugs, run virt-v2v with debugging enabled and include the > > complete output: > > > > virt-v2v -v -x [...] > > -----------------------------------------------------...

...> > On 16.09.14 15:09, Richard W.M. Jones wrote: > > > On Tue, Sep 16, 2014 at 05:06:57PM +0300, Shahar Havivi wrote: > > > > I am using upstream qemu while using this local variables: > > > > export PATH=/home/shahar/git/qemu:$PATH > > > > export LIBGUESTFS_HV=/home/shahar/git/qemu/x86_64-softmmu/qemu-system-x86_64 > > > > > > > > Is that sufficient? > > > > > > Yup, upstream qemu should work fine. Or even the qemu in Fedora Rawhide. > > Build the latest qemu, set the PATH and LIBGUESTFS_HV variables and...

...te: > Ok - > By the way, I looked into updating out KVM versions. Since we already > have so many KVM servers of this version in production, I can't easily > forklift update everything without much testing. > > exec /usr/libexec/qemu-kvm -s -S "$@" > > export LIBGUESTFS_HV=/root/work/qemu-wrapper > export LIBGUESTFS_BACKEND=direct > > How do I simulate the setup of devices the test tool perform? > Just copy/pasting the qemu-kvm argument list doesn't work. > > I was hoping that LIBGUESTFS_HV would replace usage of > /usr/libexec/qemu-kvm wit...

[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

- run bindtests.opt only if available - use ocamlc -custom - Don't try to install native code if it hasn't been built (Thanks to Olaf Hering) --- mllib/Makefile.am | 2 +- ocaml/Makefile.am | 7 ++++++- ocaml/examples/Makefile.am | 11 ++++------- ocaml/run-bindtests | 2 ++ 4 files changed, 13 insertions(+), 9 deletions(-) diff --git a/mllib/Makefile.am

...ith-qemu=search (or --with-qemu omitted) Search for various qemu binaries on the path. * --with-qemu=/path/to/qemu Use the supplied qemu binary without question. No checks on the binary are done. * --with-qemu=no or --without-qemu Disable the default hypervisor. You have to set $LIBGUESTFS_HV before running programs. --- docs/guestfs-building.pod | 7 +-- m4/guestfs_qemu.m4 | 137 ++++++++++++++++++---------------------------- 2 files changed, 56 insertions(+), 88 deletions(-) diff --git a/docs/guestfs-building.pod b/docs/guestfs-building.pod index 187da37be..9b3f37901 10...

...stfs, but I suspect what'll happen is it'll cause fall-back behaviour which might be harder to detect. * Be *really* good to have this for command line parameters! Notes on the attached patch: * https://libguestfs.org/guestfs-building.1.html * Simple test: LIBGUESTFS_BACKEND=direct \ LIBGUESTFS_HV=~/d/qemu/build/x86_64-softmmu/qemu-system-x86_64 \ ./run libguestfs-test-tool * Run the full test suite: LIBGUESTFS_HV=~/d/qemu/build/x86_64-softmmu/qemu-system-x86_64 \ make -k check-direct Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programm...

...300, Shahar Havivi wrote: > On 16.09.14 15:09, Richard W.M. Jones wrote: > > On Tue, Sep 16, 2014 at 05:06:57PM +0300, Shahar Havivi wrote: > > > I am using upstream qemu while using this local variables: > > > export PATH=/home/shahar/git/qemu:$PATH > > > export LIBGUESTFS_HV=/home/shahar/git/qemu/x86_64-softmmu/qemu-system-x86_64 > > > > > > Is that sufficient? > > > > Yup, upstream qemu should work fine. Or even the qemu in Fedora Rawhide. > Build the latest qemu, set the PATH and LIBGUESTFS_HV variables and still got > the error...

...14 15:09, Richard W.M. Jones wrote: > > > > On Tue, Sep 16, 2014 at 05:06:57PM +0300, Shahar Havivi wrote: > > > > > I am using upstream qemu while using this local variables: > > > > > export PATH=/home/shahar/git/qemu:$PATH > > > > > export LIBGUESTFS_HV=/home/shahar/git/qemu/x86_64-softmmu/qemu-system-x86_64 > > > > > > > > > > Is that sufficient? > > > > > > > > Yup, upstream qemu should work fine. Or even the qemu in Fedora Rawhide. > > > Build the latest qemu, set the PATH and LI...

New option -compat lets you configure what to do when deprecated interfaces get used. This is intended for testing users of the management interfaces. It is experimental. -compat deprecated-input=<in-policy> configures what to do when deprecated input is received. Available policies: * accept: Accept deprecated commands and arguments (default) * reject: Reject them * crash: Crash

...c/supermin/src/supermin ./configure $ ./bootstrap && ./autogen.sh && make Compile libguestfs: $ ./autogen.sh $ make -j22 (4) Use the QEMU built in step (1), build and run the 'boot-analysis' program from libguestfs test suite: $ export LIBGUESTFS_HV=$HOME/build/qemu-build/x86_64-softmmu/qemu-system-x86_64 $ make -C tests/qemu boot-analysis $ ./run tests/qemu/boot-analysis -v One and a half minute passes, nothing is printed on the screen. . . Okay, let's try 'libguestfs-test-tool' (untruncated output attached), it fai...

...new enough" qemu. As a special case you can also do ‘./configure --without-qemu’ (or ‘./configure --with-qemu=no’ which is the same thing) which disables qemu, although that means for libguestfs to work at all you would need to supply a qemu binary at runtime through an environment variable (‘LIBGUESTFS_HV=/path/to/qemu program’). The logic for all this is here: https://github.com/libguestfs/libguestfs/blob/master/m4/guestfs_qemu.m4#L26 > I would like libguestfs to take even the "qemu-img" binary from the > installed qemu package. > How to enable that? qemu is a hypervisor, q...

...nds run through the guestfs_int_cmd_* mechanism can be displayed by enabling debugging: http://libguestfs.org/guestfs-faq.1.html#debugging-libguestfs so I suggest you enable this to see exactly what's going on. > • I used "--with qemu=qemu-kvm qemu-img" as well as “export > LIBGUESTFS_HV=/path/to/qemu-img” which will obviously > override qemu-kvm to qemu-img > > Hope you got what I am saying now? > > I do not want to substitute qemu-img instead of qemu-kvm. Both has > to be taken from the specified path i.e., $PATH. > > > P.S: Its surprising to see that...

...loader opening the 170+ libraries that qemu is linked to (×2 because we need to run qemu twice). Fixing that is seriously hard work. Therefore memoize the results of guestfs_int_test_qemu. This is keyed on the size and mtime of the qemu binary, so if the user changes the qemu binary (eg. setting LIBGUESTFS_HV) we discard the memoized result and rerun the qemu commands. There is also a generation number so we can bump the generation in future versions of libguestfs to invalidate all previously cached data. The memo is stored in the supermin cache directory (eg. /var/tmp/.guestfs-*) in the files: qem...

Hi Rich I'm noe getting the below logs after running libguestfs-test-tool.. SUPERMIN_MODULES=/lib/modules/3.8.13-rt9-QorIQ-SDK-V1.4 SUPERMIN_KERNEL=/boot/vmlinuz-3.8.13-rt9-QorIQ-SDK-V1.4 PATH=/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/sbin:/usr/local/bin SELinux: sh: getenforce: command not found guestfs_get_append: (null) guestfs_get_autosync: 1 guestfs_get_backend: direct

Hi, I am trying to convert from esx server to local directory a VM names CSB, Its build from source 77b371b18b6a7ad37105a595931514f542a04396 When running: LIBGUESTFS_BACKEND=direct ./run ./v2v/virt-v2v -ic "esx://root@10.35.5.45/?no_verify=1" -o local -of raw -os /tmp/v2v CSB I get the following: --------------------------------------------------------------------------- [ 0.0]

...\ diff --git a/tests/disks/test-qemu-drive-libvirt.sh b/tests/disks/test-qemu-drive-libvirt.sh index 215a99e..b2656ba 100755 --- a/tests/disks/test-qemu-drive-libvirt.sh +++ b/tests/disks/test-qemu-drive-libvirt.sh @@ -47,6 +47,12 @@ export LIBGUESTFS_BACKEND=direct export LIBGUESTFS_HV="${abs_srcdir}/debug-qemu.sh" export DEBUG_QEMU_FILE="${abs_builddir}/test-qemu-drive-libvirt.out" +# Setup the fake pool. +pool_dir=tmp +rm -rf "$pool_dir" +mkdir "$pool_dir" +touch "$pool_dir/in-pool" + function check_output () { if [ !...

From: "Richard W.M. Jones" <rjones at redhat.com> This means there will be no default hypervisor, and effectively the user will always have to specify one (eg. by setting LIBGUESTFS_HV or calling guestfs_set_hv). This is useful on platforms where qemu doesn't work, or where qemu is not needed (eg. if you want to use UML, or you just want to compile libguestfs without using/testing it). --- configure.ac | 125 ++++++++++++++++++++++------------------- src/h...