search for: libguestfs_trac

...ogress markers and show where time is being spent. (As I already added this code for my testing, I thought it might be worth discussing further here.) This patch adds the following startup options: -v | --verbose Enables verbose messages logging -vv Verbose messages, plus sets LIBGUESTFS_TRACE=1 -vvv Verbose messages, plus sets LIBGUESTFS_TRACE=1 and LIBGUESTFS_DEBUG=1 --- v2v/virt-v2v.pl | 45 +++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 45 insertions(+) diff --git a/v2v/virt-v2v.pl b/v2v/virt-v2v.pl index 3832f67..eddcd16 100755 --- a/v2v/virt-v2v.pl +++...

...you'd just get failures for every test. So there is no good way +# to debug libguestfs failures in PHP tests, but if an individual test +# fails locally then you can edit the guestfs_php_*.phpt.in and +# uncomment the putenv statement, then look at the output. unset LIBGUESTFS_DEBUG unset LIBGUESTFS_TRACE @@ -47,8 +44,4 @@ printenv | grep -E '^(LIBGUESTFS|LIBVIRT|LIBVIRTD|VIRTLOCKD|LD|MALLOC)_' >> env TESTS=$(echo tests/guestfs_*.phpt) echo TESTS: $TESTS -${MAKE:-make} test \ - TESTS="$TESTS" \ - TEST_PHP_EXECUTABLE="$PWD/php-for-tests.sh&q...

...fcf06-8743-45d1-9af8-61a0c48e8c67\\\'] > failed with rc=1 out=b\\\'3/12\\\\n{ "message": "libguestfs error: > guestfs_launch failed.\\\\\\\\nThis usually means the libguestfs > appliance failed to start or crashed.\\\\\\\\nDo:\\\\\\\\n export > LIBGUESTFS_DEBUG=1 LIBGUESTFS_TRACE=1\\\\\\\\nand run the command > again. For further information, read:\\\\\\\\n > http://libguestfs.org/guestfs-faq.1.html#debugging-libguestfs\\\\\\\\nYou > can also run \\\\\\\'libguestfs-test-tool\\\\\\\' and post the > *complete* output\\\\\\\\ninto a bug report or message...

...-------- >From 759de3f6289967a3c9978b4e947a38a4585f404c Mon Sep 17 00:00:00 2001 From: Richard Jones <rjones at trick.home.annexia.org> Date: Wed, 9 Sep 2009 17:48:30 +0100 Subject: [PATCH] Add command trace functionality. Enable this by calling guestfs_trace (handle, 1) or by setting the LIBGUESTFS_TRACE=1 environment variable. --- guestfish.pod | 4 +++ guestfs.pod | 5 +++ src/generator.ml | 74 ++++++++++++++++++++++++++++++++++++++++++++++++++++++ src/guestfs.c | 17 ++++++++++++ 4 files changed, 100 insertions(+), 0 deletions(-) diff --git a/guestfish.pod b/guestfish.po...

...> > Right, so in this particular instance the error message would tell us > that you should run libguestfs-test-tool because your qemu/kernel/etc > is broken in some way :-/ > > There's not a particularly good answer here if you don't want to ever > use LIBGUESTFS_DEBUG/LIBGUESTFS_TRACE, but perhaps you could run > libguestfs-test-tool if you see any error which matches the substring > /guestfs_launch/ ? Another (orthogonal?) option: Make LIBGUESTFS_DEBUG/LIBGUESTFS_TRACE log elsewhere, not to stdout/err (e.g. some other file descriptor, or to a file passed via env or wha...

From: Pino Toscano <ptoscano at redhat.com> Move unsetting of LIBGUESTFS_DEBUG & LIBGUESTFS_TRACE into the php-for-tests.sh wrapper. Fixes commit 0d69eab98f0bd5dd2d218ce5adcafdeb13f9d90d. --- php/extension/php-for-tests.sh.in | 12 ++++++++++++ php/run-php-tests.sh | 12 ------------ 2 files changed, 12 insertions(+), 12 deletions(-) diff --git a/php/extension/php-for-tests.sh....

...is sparse in virt-v2v; it > will be better in guestconv. It's lame in virt-v2v because we didn't > consider it important early, and didn't retrofit it later. However, you > have to consider what the logging is for. If it's just for debugging, > nothing is likely to beat LIBGUESTFS_TRACE. LIBGUESTFS_TRACE is more than enough to monitor the conversion itself. I was specifically thinking a little higher level anyway. > I would keep logging to: > 1. Debugging information which won't be captured by LIBGUESTFS_TRACE, > because it doesn't involve a libguestfs api ca...

On Tuesday, September 03, 2013 07:52:08 PM Richard W.M. Jones wrote: > Even better, there is a repo: https://github.com/mdbooth/guestconv Excellent. Thanks for the pointer. > Matt - can you push your latest commits, or is there a more canonical > repo that Mike can look at? The last changes in the repo seem to be from back in June. Is guestconv expected to completely replace virt-v2v

...e error message would tell us > > > that you should run libguestfs-test-tool because your qemu/kernel/etc > > > is broken in some way :-/ > > > > > > There's not a particularly good answer here if you don't want to ever > > > use LIBGUESTFS_DEBUG/LIBGUESTFS_TRACE, but perhaps you could run > > > libguestfs-test-tool if you see any error which matches the substring > > > /guestfs_launch/ ? > > > > Another (orthogonal?) option: > > > > Make LIBGUESTFS_DEBUG/LIBGUESTFS_TRACE log elsewhere, not to stdout/err > >...

https://bugzilla.redhat.com/show_bug.cgi?id=1175196 Currently if you write something like LIBGUESTFS_DEBUG=0 or LIBGUESTFS_DEBUG=true then it doesn't do what you probably expect. This patch series fixes that. Rich.

...s message, basically the only info about the error is: libguestfs error: guestfs_launch failed I don't see what we can do with this error message. If this is an error running qemu, the error message from qemu can help to understand why qemu failed to start. > Without LIBGUESTFS_DEBUG/LIBGUESTFS_TRACE stdout + stderr should be > quite minimal for all tools. > > Rich. > > -- > Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones > Read my programming and virtualization blog: http://rwmj.wordpress.com > virt-df lists disk usage of guests without ne...

...2v; it > > will be better in guestconv. It's lame in virt-v2v because we didn't > > consider it important early, and didn't retrofit it later. However, you > > have to consider what the logging is for. If it's just for debugging, > > nothing is likely to beat LIBGUESTFS_TRACE. > > LIBGUESTFS_TRACE is more than enough to monitor the conversion itself. I was > specifically thinking a little higher level anyway. > > > I would keep logging to: > > 1. Debugging information which won't be captured by LIBGUESTFS_TRACE, > > because it does...

...image with the same result: > > > > virtio configured, but no virtio kernel found > > at /usr/share/perl5/vendor_perl/Sys/VirtConvert/Converter/RedHat.pm > > Hi, Owen, > > Could you please pastebin the output of the conversion run with the > environment variable LIBGUESTFS_TRACE=1. > > Thanks, > > Matt > Done but with LIBGUESTFS_DEBUG=1 (I already had it) : http://pastebin.com/ZUQ9BMzP Anyway, I have a working VM now. I added: <capability os='linux' name='kernel' distro='centos' major='6' minor='4' arch=&...

...Fatal error: exception Guestfs.Error("guestfs_launch failed. See http://libguestfs.org/guestfs-faq.1.html#debugging-libguestfs and/or run 'libguestfs-test-tool'.") So I ran virt-sysprep and libguestfs-test-tool after setting these: export LIBGUESTFS_DEBUG=1 export LIBGUESTFS_TRACE=1 ... and have attached the output files. Do you have any ideas on how to fix this? Bests, Stuart -- Stuart Young Director of Bioinformatics Annai Systems 2100 Palomar Airport Road, Suite 210, Carlsbad, CA 92008 Mobile: 305-781-2286 Email: stuarty@annaisystems.com

...is particular instance the error message would tell us > > that you should run libguestfs-test-tool because your qemu/kernel/etc > > is broken in some way :-/ > > > > There's not a particularly good answer here if you don't want to ever > > use LIBGUESTFS_DEBUG/LIBGUESTFS_TRACE, but perhaps you could run > > libguestfs-test-tool if you see any error which matches the substring > > /guestfs_launch/ ? > > Another (orthogonal?) option: > > Make LIBGUESTFS_DEBUG/LIBGUESTFS_TRACE log elsewhere, not to stdout/err > (e.g. some other file descriptor, o...

...put of these commands? While remounting the qcow2 I'm not able to see the modifications I have made to the qcow2 during initial mounting. May I know why. 1. Enable debugging, run the commands again, and capture the complete output. Do not edit the output. export LIBGUESTFS_DEBUG=1 export LIBGUESTFS_TRACE=1 I have attached the debuglog.txt Please let me know if you need more information... Awaiting for a response. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://listman.redhat.com/archives/libguestfs/attachments/20230314/af13b889/attachment-0001.htm>...

...ogging. Yes, logging is sparse in virt-v2v; it will be better in guestconv. It's lame in virt-v2v because we didn't consider it important early, and didn't retrofit it later. However, you have to consider what the logging is for. If it's just for debugging, nothing is likely to beat LIBGUESTFS_TRACE. I would keep logging to: 1. Debugging information which won't be captured by LIBGUESTFS_TRACE, because it doesn't involve a libguestfs api call. 2. Information about the conversion which is of use to the end user. If you have any ideas on what the second set is, that would be very inter...

...r' branch): $ git log | head -2 commit 4d2c63a9bc3accd7b852b1c8b2089c6296fee156 Author: Richard W.M. Jones <rjones@redhat.com> I invoked: $ git pull ; ./autogen.sh && make clean && make -j 7 \ && time make -k extra-tests LIBGUESTFS_DEBUG=1 LIBGUESTFS_TRACE=1 \ | tee /var/tmp/make-extra-check-libguestfs-24-may.log . . . . extracting /usr/lib64/gconv/gconv-modules from glibc-2.17-11.fc19.x86_64.rpm ... Fatal error: exception Unix.Unix_error(8, "mkdir", "/tmp/supermin66a2e1c4c95a0e7fb53c3122f449b299.tmp/root//var/run") make[2]:...

...artition is not encrypted. root at kvm1:~# ntfsresize -v ntfsresize v2011.4.12AR.4 (libntfs-3g) The attempt ends with an error Fatal error: exception Guestfs.Error("ntfsresize_opts: /dev/vda2) I have attached a txt file of the results where I have used export LIBGUESTFS_DEBUG=1 ; export LIBGUESTFS_TRACE=1 I have also tried using virt-resize --expand /dev/sda2 /dev/vgpool/w2008webtemplate /dev/vgpool/wintest2 as well as virt-resize --expand /dev/vda2 /dev/vgpool/w2008webtemplate /dev/vgpool/wintest2 Any ideas how to get it working ? -------------- next part -------------- An HTML attachment...

Hello, I've trying to move a 32bit CentOS 6.4 on VirtualBox to oVirt on Fedora 19 64bit via virt-v2v. The command I'm currently using is: virt-v2v -i libvirtxml -of qcow2 -oa sparse -o rhev -osd xxx.xxx.xxx.xxx:/usr/local/ovirt/exports --network ovirtmgmt /usr1/home/williams/Downloads/OpenAthens/VMs/OpenAthensLARuntime2.2.xml The exciting bit of the XML is: <devices>