similar to: [PATCH v2] tests: Fix qemu-wrapper.sh generation

--- There's some other issues with check-with-upstream-qemu, like qemu-wrapper isn't regenerated if we specify a new QEMUDIR. Makefile.am | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Makefile.am b/Makefile.am index 2eebefa..4f88311 100644 --- a/Makefile.am +++ b/Makefile.am @@ -356,7 +356,7 @@ check-with-upstream-qemu-1: $(top_builddir)/qemu-wrapper.sh

qemu-wrapper isn't regenerated if QEMUDIR is changed, so just delete it and force regeneration. Additionally we can drop the silent binary check, since check-with-upstream-qemu-1 already does a similar test with --version that will actually report an error to the user. --- Makefile.am | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/Makefile.am b/Makefile.am index

Hello, I have installed libguestfs on RHEL 5.5 64 bit. 3 packages i have installed. libguestfs-tools-c-1.9.10-1.1 libguestfs-tools-1.9.10-1.1 libguestfs-1.9.10-1.1 When i am trying to run virt-resize it gives me error: virt-resize -expand /dev/sda1 vm01.scilab vm01.scilab-15GB -d libguestfs: trace: add_drive_opts "vm01.scilab" "readonly:true" libguestfs: trace:

On Fri, Jan 24, 2014 at 04:49:24PM -0800, Tim Fall wrote: > Not that I know of, resource usage seems totally normal. Also, as I > mentioned, virt-install and virt-manager can both access and run vm's on > qmeu without any trouble. Ulimit is also unset. You can try a different qemu from upstream, which should diagnose whether this is a kernel problem or a qemu problem:

Not that I know of, resource usage seems totally normal. Also, as I mentioned, virt-install and virt-manager can both access and run vm's on qmeu without any trouble. Ulimit is also unset. On Fri, Jan 24, 2014 at 2:42 PM, Richard W.M. Jones <rjones@redhat.com>wrote: > On Fri, Jan 24, 2014 at 12:45:43PM -0800, Tim Fall wrote: > > Here’s the trace you requested. I can dump the

Ubuntu are now supplying a libguestfs package (or to be more accurate, they are just copying the Debian package) but it doesn't work out of the box. There is a bug in apt which we worked around in febootstrap 3.14, but the supplied version of febootstap is only 3.12. Hence you will get errors like this during installation: febootstrap: aptitude: error: no file was downloaded corresponding

On Sun, Aug 08, 2010 at 12:05:58PM +0800, Kirby Zhou wrote: > guestfish takes legacy qemu instead of kvm? > ]# rpm -q libguestfs --requires | fgrep qemu > qemu-system-x86 >= 0.10.5 To make it clear, this is EPEL-5. There was some still unresolved problem with adding a dependency on KVM: https://fedorahosted.org/rel-eng/ticket/2982 As a result, we have to depend on qemu (software

On Thu, Jul 31, 2014 at 03:32:18PM -0700, Zetan Drableg wrote: > 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

*** BLURB HERE *** Pino Toscano (3): test-tool: implement --short-options & --long-options test-tool: add a documentation test bash: add a completion script for libguestfs-test-tool .gitignore | 1 + bash/Makefile.am | 3 ++- bash/virt-v2v-copy-to-local | 6 +++++ test-tool/Makefile.am

Hi, I am using the libguestfs-1.11.0-1 binaries posted here: http://libguestfs.org/download/binaries/debian-packages/ on a Sid system. When I use libguestfs, I can see that an instance of QEMU is starting up using the binary @ /usr/bin/qemu-system-x86_64 I have KVM installed on the system at /usr/bin/kvm -- how do I ensure that KVM gets used by libguestfs instead of qemu? I guess I can

This is a User-Mode Linux backend for libguestfs. You can select it by doing: export LIBGUESTFS_BACKEND=uml export LIBGUESTFS_QEMU=/path/to/vmlinux Note we're reusing the 'qemu' variable in the handle for convenience. QEmu is not involved when using the UML backend. This almost works. UML itself crashes when the daemon tries to connect to the serial port. I suspect it's

While not useful per-se, it will help checking the available options. --- test-tool/Makefile.am | 5 ++++- test-tool/test-tool.c | 9 ++++++++- 2 files changed, 12 insertions(+), 2 deletions(-) diff --git a/test-tool/Makefile.am b/test-tool/Makefile.am index bf4f5a843..2cbd4d1b1 100644 --- a/test-tool/Makefile.am +++ b/test-tool/Makefile.am @@ -22,11 +22,14 @@ EXTRA_DIST =

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

This patch is for discussion only. The multiport virtio-console is not accepted upstream, and in any case is currently being rewritten for the nth time. Getting a test environment to test this out is also non-trivial. It look me about a day. You need to compile the alternate qemu (see URL in the patch + attached qemu patch on top of this). You also need to compile the alternate kernel - NOTE:

On Thu, Jan 23, 2014 at 02:06:03PM -0800, Tim Fall wrote: > On Jan 23, 2014, at 1:54 PM, Richard W.M. Jones <rjones@redhat.com> wrote: > > It seems to be the same as mine so I don't know why it's failing. > > Perhaps strace qemu to see how it quits? > > Here’s the strace from libguestfs-test-tool. > > http://hastebin.com/gowayehowu.tex That's not

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

After configuring my home network, aMSN segfaults. I posted this issue originally in the aMSN forums under this thread: http://www.amsn-project.net/forums/viewtopic.php?t=7593 I was told that my issue is related to SAMBA, referring this thread: http://www.amsn-project.net/forums/viewtopic.php?t=6343 After uninstalling SAMBA, aMSN stops segfaulting and works as expected. After installing it

Hi, whenever I perform 'launch' operation to launch a disk, guestfs looks for KVM support and prints this message "Could not initialize KVM, will disable KVM support" . Is there a way to turn it off.. I dont want guestfs to look for KVM . Thanks in advance -- Cheers, Yeswanth -------------- next part -------------- An HTML attachment was scrubbed... URL:

[This email is either empty or too large to be displayed at this time]

I've added a few patches upstream to make static linking work, and it is [surprisingly] possible to get it to work. You'll have to check out libguestfs from git. Read the README file very carefully, and get familiar with building from source. This is easier on a recent Fedora machine or VM. Once you are comfortable building libguestfs from source, configure it like this: ./configure