™.. libguestfs-test-tool - Online Linux Manual PageSection : 1
Updated : 2013-08-27
Source : libguestfs-1.20.11
Note : Virtualization Support
NAMElibguestfs−test−tool − Diagnostics for libguestfs
SYNOPSIS​ libguestfs−test−tool [−−options]
DESCRIPTIONlibguestfs-test-tool is a test program shipped with libguestfs to allow you to check basic libguestfs functionality is working. This is needed because libguestfs occasionally breaks for reasons beyond our control: usually because of changes in the underlying qemu or kernel packages, or the host environment. If you suspect a problem in libguestfs, then just run: ​ libguestfs−test−tool It will print lots of diagnostic messages. If it runs to completion successfully, you will see this near the end: ​ ===== TEST FINISHED OK ===== and the test tool will exit with code 0. If it fails (and/or exits with non-zero error code), please paste the ​complete, unedited output of the test tool into a bug report. More information about reporting bugs can be found on the http://libguestfs.org/ website.
OPTIONS−−help Display short usage information and exit. −−qemu qemu_binary If you have downloaded another qemu binary, point this option at the full path of the binary to try it. −−qemudir qemu_source_dir If you have compiled qemu from source, point this option at the source directory to try it. −t N −−timeout N Set the launch timeout to \*(C`N\*(C'\fR seconds. The default is 600 seconds (10 minutes) which does not usually need to be adjusted. −V −−version Display the libguestfs version number and exit.
TRYING OUT A DIFFERENT VERSION OF QEMUIf you have compiled another version of qemu from source and would like to try that, then you can use the −−qemudir option to point to the qemu source directory. If you have downloaded a qemu binary from somewhere, use the −−qemu option to point to the binary. Note when using these options, you can ignore the business of qemu wrapper scripts (‟QEMU WRAPPERS” in guestfs (3)), since libguestfs-test-tool writes a wrapper script for you if one is needed.
TRYING OUT A DIFFERENT KERNELIf you are using supermin / febootstrap ≥ 3.8 then you can select which kernel libguestfs tries. You do this by setting the environment variables \*(C`SUPERMIN_KERNEL\*(C'\fR and/or \f(CW\*(C`SUPERMIN_MODULES\*(C'\fR (\*(C`FEBOOTSTRAP_KERNEL\*(C'\fR and \f(CW\*(C`FEBOOTSTRAP_MODULES\*(C'\fR if still using the old febootstrap 3.21 program). Refer to ‟ENVIRONMENT VARIABLES” in supermin−helper (8) for further information.
TRYING OUT A DIFFERENT VERSION OF LIBVIRTTo find out which attach-method is the default in your libguestfs package, do: ​ unset LIBGUESTFS_ATTACH_METHOD ​ guestfish get−attach−method If you are using the libvirt attach-method, then you can try out a different (eg. upstream) version of libvirt by running these commands (not as root): ​ killall libvirtd lt−libvirtd ​ ~/path/to/libvirt/run libguestfs−test−tool The first command kills any session \*(C`libvirtd\*(C'\fR process(es) that may be running on the machine. The second command uses libvirt's \*(C`run\*(C'\fR script (in the top-level libvirt build directory) to set some environment variables so that the alternate version of libvirt is used to run the program.
TRYING OUT WITH / WITHOUT LIBVIRTTo find out which attach-method is the default in your libguestfs package, do: ​ unset LIBGUESTFS_ATTACH_METHOD ​ guestfish get−attach−method If you are using the libvirt attach-method, you can try without (ie. libguestfs directly launching qemu) by doing: ​ export LIBGUESTFS_ATTACH_METHOD=appliance Or if you are using the default (appliance) attach-method, then you can try libvirt: ​ export LIBGUESTFS_ATTACH_METHOD=libvirt or with libvirt and a specific libvirt URI: ​ export LIBGUESTFS_ATTACH_METHOD=libvirt:qemu:///session
TRYING OUT DIFFERENT SELINUX SETTINGSTo find out which attach-method is the default in your libguestfs package, do: ​ LIBGUESTFS_ATTACH_METHOD= guestfish get−attach−method To find out if SELinux is being used, do: ​ getenforce If you are using libvirt, SELinux and sVirt, then you can try to see if changing SELinux to ‟permissive” mode makes any difference. Use this command as root: ​ setenforce Permissive If this makes a difference, look in the audit logs for recent failures (‟AVCs”): ​ ausearch −m avc −ts recent You can convert AVCs into suggested SELinux policy rules using tools like audit2allow (1). For more information, see the ‟Security Enhanced Linux User Guide”. To reenable SELinux and sVirt, do: ​ setenforce Enforcing
SELF-DIAGNOSISRefer to ‟APPLIANCE BOOT PROCESS” in guestfs (3) to understand the messages produced by libguestfs-test-tool and/or possible errors.
EXIT STATUSlibguestfs-test-tool returns 0 if the tests completed without error, or 1 if there was an error.
ENVIRONMENT VARIABLESFor the full list of environment variables which may affect libguestfs, please see the guestfs (3) manual page.
SEE ALSO​guestfs (3), http://libguestfs.org/, http://qemu.org/.
AUTHORSRichard W.M. Jones (\*(C`rjones at redhat dot com\*(C'\fR)
COPYRIGHTCopyright (C) 2009−2013 Red Hat Inc.
LICENSEThis program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but ​WITHOUT ANY WARRANTY; without even the implied warranty of ​MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110−1301 USA.
BUGSTo get a list of bugs against libguestfs, use this link: https://bugzilla.redhat.com/buglist.cgi?component=libguestfs&product=Virtualization+Tools To report a new bug against libguestfs, use this link: https://bugzilla.redhat.com/enter_bug.cgi?component=libguestfs&product=Virtualization+Tools When reporting a bug, please supply: • The version of libguestfs. • Where you got libguestfs (eg. which Linux distro, compiled from source, etc) • Describe the bug accurately and give a way to reproduce it. • Run libguestfs−test−tool (1) and paste the complete, unedited output into the bug report. 0
Johanes Gumabo
Data Size   :   24,264 byte
man-libguestfs-test-tool.1Build   :   2024-12-05, 20:55   :  
Visitor Screen   :   x
Visitor Counter ( page / site )   :   2 / 202,110
Visitor ID   :     :  
Visitor IP   :   3.133.127.131   :  
Visitor Provider   :   AMAZON-02   :  
Provider Position ( lat x lon )   :   39.962500 x -83.006100   :   x
Provider Accuracy Radius ( km )   :   1000   :  
Provider City   :   Columbus   :  
Provider Province   :   Ohio ,   :   ,
Provider Country   :   United States   :  
Provider Continent   :   North America   :  
Visitor Recorder   :   Version   :  
Visitor Recorder   :   Library   :  
Online Linux Manual Page   :   Version   :   Online Linux Manual Page - Fedora.40 - march=x86-64 - mtune=generic - 24.12.05
Online Linux Manual Page   :   Library   :   lib_c - 24.10.03 - march=x86-64 - mtune=generic - Fedora.40
Online Linux Manual Page   :   Library   :   lib_m - 24.10.03 - march=x86-64 - mtune=generic - Fedora.40
Data Base   :   Version   :   Online Linux Manual Page Database - 24.04.13 - march=x86-64 - mtune=generic - fedora-38
Data Base   :   Library   :   lib_c - 23.02.07 - march=x86-64 - mtune=generic - fedora.36
Very long time ago, I have the best tutor, Wenzel Svojanovsky . If someone knows the email address of Wenzel Svojanovsky , please send an email to johanes_gumabo@yahoo.co.id .
If error, please print screen and send to johanes_gumabo@yahoo.co.id
Under development. Support me via PayPal.
ERROR : Need New Coding :         (parse_manual_page_|249|libguestfs-test-tool.1|36/37|el══─{─══.|.el══─{─══. ds -- \|\(em\| )         (htmlprn|149|libguestfs-test-tool.1|36/37|.el══─{─══. ds --  —  |.el══─{─══. ds -- \|\(em\| )         (parse_manual_page_|249|libguestfs-test-tool.1|41|br══─}─══|'br══─}─══ )         (htmlprn|149|libguestfs-test-tool.1|41|'br══─}─══ |'br══─}─══ )         (rof_nr_x|149|libguestfs-test-tool.1|51/52|\nF|.ie \nF ══─{─══. de IX )         (rof_unit_scale_px|41|libguestfs-test-tool.1|51/52|F|.ie \nF ══─{─══. de IX )         (rof_if|19|libguestfs-test-tool.1|51/52|\nF|.ie \nF ══─{─══. de IX )         (htmlprn|149|libguestfs-test-tool.1|51/52|.ie \nF ══─{─══. de IX|.ie \nF ══─{─══. de IX )         (rof_escape_sequence|91|libguestfs-test-tool.1|53|\$1\t\\n%\t"\\$2" |. tm Index:\\$1\t\\n%\t"\\$2" )         (parse_manual_page_|249|libguestfs-test-tool.1|57|══─}─══|.══─}─══ )         (htmlprn|149|libguestfs-test-tool.1|57|.══─}─══ |.══─}─══ )         (rof_escape_sequence|91|libguestfs-test-tool.1|124|\*(C`N\*(C'\fR seconds. The default is 600 seconds |Set the launch timeout to \f(CW\*(C`N\*(C'\fR seconds. The default is 600 seconds )         (rof_escape_sequence|91|libguestfs-test-tool.1|149|\*(C`SUPERMIN_KERNEL\*(C'\fR and/or \f(CW\*(C`SUPERMIN_MODULES\*(C'\fR |variables \f(CW\*(C`SUPERMIN_KERNEL\*(C'\fR and/or \f(CW\*(C`SUPERMIN_MODULES\*(C'\fR )         (rof_escape_sequence|91|libguestfs-test-tool.1|150|\*(C`FEBOOTSTRAP_KERNEL\*(C'\fR and \f(CW\*(C`FEBOOTSTRAP_MODULES\*(C'\fR if still using the |(\f(CW\*(C`FEBOOTSTRAP_KERNEL\*(C'\fR and \f(CW\*(C`FEBOOTSTRAP_MODULES\*(C'\fR if still using the )         (rof_escape_sequence|91|libguestfs-test-tool.1|174|\*(C`libvirtd\*(C'\fR process(es) that may |The first command kills any session \f(CW\*(C`libvirtd\*(C'\fR process(es) that may )         (rof_escape_sequence|91|libguestfs-test-tool.1|175|\*(C`run\*(C'\fR |be running on the machine. The second command uses libvirt's \f(CW\*(C`run\*(C'\fR )         (rof_escape_sequence|91|libguestfs-test-tool.1|267|\*(C`rjones at redhat dot com\*(C'\fR) |Richard W.M. Jones (\f(CW\*(C`rjones at redhat dot com\*(C'\fR) )