search for: libguestfs_debug

...;*.out' files. +# so 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="...

...eb-848229f81c97/515fcf06-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...

...s error message. > > 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 passe...

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/exten...

...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 +++ b/v2v/virt-v2v.pl @@ -354,6 +354,24 @@ my $list_profiles = 0; Display a list of tar...

It looks to me that the windows 2008 image I am attempting to convert is not being detected as windows but is being updated as a Linux system. When PXE booted the server with the p2v image I ended up with this error: Failed to launch guestfs appliance. Try running again with LIBGUESTFS_DEBUG=1 for more information The system image transferred and I was able to create an XML file to boot it under kvm with IDE disks. I undefined it and attempted to convert the system into another storage pool to help in the debugging and I ended up with the same error. This is what I ran: LIBGUESTFS_...

...cular 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 stdou...

...ge in the previous 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 g...

...Examining the guest ... 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

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.

...; 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 fi...

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 qcow2 -oa sparse -n ovirtmgmt testvm virt-v2v version is 0.9.0. This is the output produced by the command: libguestfs: trace: set_verbose true libguestfs: trace: set_verbose = 0 libguestfs: tr...

...as the precise error or output 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/af13b8...

Hello, I have an issue with virt-resize on the newest version of proxmox which is running on debian wheezy. when I run the virt-resize on a windows 2008 qemu image I got an error. Here is the last part of the debug message: Copying /dev/sda1 ... libguestfs: trace: copy_device_to_device "/dev/sda1" "/dev/sdb1" "size:32210026496" 100%

...} } else { @@ -866,8 +863,32 @@ do_part_get_gpt_type(const char *device, int partnum) } } - /* If we got here it means we didn't find the Partition GUID code */ - reply_with_error ("sgdisk output did not contain Partition GUID code. " - "See LIBGUESTFS_DEBUG output for more details"); + /* If we got here it means we didn't find the field */ + reply_with_error ("sgdisk output did not contain '%s'. " + "See LIBGUESTFS_DEBUG output for more details", field); return NULL; } + +static char * +ext...

...m at (on 'master' 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/r...

...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='i686'> <dep name='kernel' minversion='2.6.18-12...

...n the server - the windows partition 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 ------...

...crash upon nested vm with high memory pressure - http://git.kernel.org/cgit/virt/kvm/kvm.git/patch/arch/x86/kvm/mmu.c?id=989c6b34f6a9480e397b170cc62237e89bf4fdb9. Command within L1 to perform the conversion (fedora.ova - vmdk image of fedora - was placed in advance on the VM): LIBGUESTFS_TRACE=1 LIBGUESTFS_DEBUG=1 /usr/bin/virt-v2v -i ova -os default -oc qemu:///system -of qcow2 -n default /var/tmp/fedora-v2v.ova Version-Release number of selected component (if applicable): L0: Kernel: 3.11.8-200.fc19 + nested crash patches libvritd: 1.0.5.8 qemu: 1.6.1 libguestfs-test-tool 1.22.7fedora=19,release=1.fc19...

>From IRC channel: <StenaviN> Can someone confirm cat/test-virt-tail.sh works in 'master'? <StenaviN> I get https://pastebin.com/GBkg7Vtw <rwmjones> StenaviN: yes it works for me; the error is not very helpful, you'll need to set LIBGUESTFS_DEBUG=1 LIBGUESTFS_TRACE=1 <StenaviN> https://pastebin.com/yABgCHwV <rwmjones> I think the error is: <rwmjones> libguestfs: trace: statns "/tail" <rwmjones> guestfsd: => mount_options (0x4a) took 0.00 secs <rwmjones> guestfsd: <= statns (0x1a5) request length...