search for: libguestfs_qemu

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:

...file changed, 2 insertions(+), 2 deletions(-) diff --git a/Makefile.am b/Makefile.am index 2eebefa..560ebda 100644 --- a/Makefile.am +++ b/Makefile.am @@ -352,11 +352,11 @@ check-with-upstream-qemu: check-with-upstream-qemu-1: $(top_builddir)/qemu-wrapper.sh $(QEMUBINARY) --version - $(MAKE) LIBGUESTFS_QEMU=$(top_builddir)/qemu-wrapper.sh check + $(MAKE) LIBGUESTFS_QEMU=$(abs_builddir)/qemu-wrapper.sh check $(top_builddir)/qemu-wrapper.sh: Makefile rm -f $@ $@-t - echo exec "$(QEMUBINARY)" -L "$(QEMUDIR)/pc-bios" "$$@" > $@-t + echo -e "#!/bin/sh\nexec"...

...gt;= 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 emulation) instead. However you can easily change this at runtime by setting the LIBGUESTFS_QEMU environment variable: http://libguestfs.org/guestfs.3.html#libguestfs_qemu http://libguestfs.org/guestfs.3.html#qemu_wrappers In RHEL 6 it's all going to be different again. The same qemu-system-x86 RPM is actually KVM. We combine qemu and KVM sources during the build to make a 'qem...

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

...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/bash - qemu=/usr/libexec/qemu-kvm...

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 because I'm using the 'ssl3=f...

...ernate kernel - NOTE: only linux-next kernel given in the URL in the patch will work, earlier kernels will definitely *not* work. You need to create an RPM of this and then build a custom appliance with this kernel. NOTE: Do not use supermin! Then you can test it with a qemu wrapper, like this: LIBGUESTFS_QEMU=~/d/vs-qemu-kvm/qemu.wrapper \ libtool --mode=execute \ ./fish/guestfish -v alloc /tmp/test.img 10M : run : debug ll / (or if you are more adventurous, try running 'make check'). Multiport virtio-console fails on my local machine if the host is under moderate load. I'm currently...

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:

...by writing a qemu wrapper: ---------------------------------------------------------------------- #!/bin/bash - exec strace -o /tmp/qemu.log -f -s 1024 /usr/bin/qemu-system-x86_64 "$@" ---------------------------------------------------------------------- chmod +x the script, then point LIBGUESTFS_QEMU at this script. See: http://libguestfs.org/guestfs.3.html#qemu-wrappers Attach the qemu.log to this list. The pastebin link above does not work for me. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Fedora Windows cross-compiler. Compile Windows program...

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

...it://git.qemu.org/qemu.git cd qemu sudo apt-get build-dep qemu ./configure --target-list=x86_64-softmmu make -j2 cat > qemu.wrapper <<EOF #!/bin/bash - qemudir=$(pwd) exec \$qemudir/x86_64-softmmu/qemu-system-x86_64 -L \$qemudir/pc-bios "\$@" EOF chmod +x qemu.wrapper export LIBGUESTFS_QEMU=$(pwd)/qemu.wrapper libguestfs-test-tool ---------------------------------------------------------------------- Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming blog: http://rwmj.wordpress.com Fedora now supports 80 OCaml packages (the O...

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

...and the fixed appliance directory to the Xen server. Note that the fixed appliance contains a large sparse file ('root'), and if you don't use the appropriate method to copy it, then you'll end up making it non-sparse and taking a large amount of space. Run it like this: export LIBGUESTFS_QEMU=/path/to/qemu export LIBGUESTFS_PATH=/path/to/appliance ./virt-rescue [normal parameters ...] If it doesn't work, then also set: export LIBGUESTFS_DEBUG=1 export LIBGUESTFS_TRACE=1 Good luck! Rich. [1] http://libguestfs.org/libguestfs-make-fixed-appliance.1.html -- Richard Jones,...

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

[Sorry - I didn't see this email until now as virt-rescue is part of the http://libguestfs.org project and so normally uses a different mailing list] On Tue, Mar 17, 2015 at 11:29:29AM +0000, Keith Roberts wrote: > Hi all. > > I’d like to create a statically-linked version of virt-rescue that I > can compile on my laptop then deploy that binary locally onto a xen > server

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

On Jan 23, 2014, at 1:54 PM, Richard W.M. Jones <rjones@redhat.com> wrote: > Please keep libguestfs mailing list in the CC. Sorry I realized that just after I sent it. > > On Thu, Jan 23, 2014 at 01:44:46PM -0800, Tim Fall wrote: >> >> On Jan 23, 2014, at 4:47 AM, Richard W.M. Jones <rjones@redhat.com> wrote: >> >>> On Thu, Jan 23, 2014 at

I'm updating the ArchLinux libguestfs package to 1.12.7, but the "make check" tests fail in qemu with: Booting from ROM... This kernel requires an x86-64 CPU, but only detected an i686 CPU. Unable to boot - please use a kernel appropriate for your CPU. How does qemu detect the CPU type? I'm running a 64-bit ArchLinux (without KVM) on an Intel Xeon E5420 processor. I'm

On Wed, Mar 31, 2010 at 09:26:24PM +0300, Active Systems O? wrote: > Hi, > > As I couldnt find any appropriate bugzilla - so I'll post directly to you. There seems to be a problem with EPEL repo libguestfs-1.0.85-1.el5.5 rpm (x86_64) - for example it is very slow with VM filesystem copy as it does not make use of KVM acceleration (running plain qemu). > Running

v1 was here: https://www.redhat.com/archives/libguestfs/2013-August/msg00005.html This now works, to some extent. The main problem now is that devices are named /dev/ubd[a-] which of course confuses everything. I'm thinking it may be easier to add a udev rule to rename them. Rich.