.\" -*- mode: troff; coding: utf-8 -*-
.\" Automatically generated by Podwrapper::Man 1.54.0 (Pod::Simple 3.45)
.\"
.\" Standard preamble:
.\" ========================================================================
.de Sp \" Vertical space (when we can't use .PP)
.if t .sp .5v
.if n .sp
..
.de Vb \" Begin verbatim text
.ft CW
.nf
.ne \\$1
..
.de Ve \" End verbatim text
.ft R
.fi
..
.\" \*(C` and \*(C' are quotes in nroff, nothing in troff, for use with C<>.
.ie n \{\
.    ds C` ""
.    ds C' ""
'br\}
.el\{\
.    ds C`
.    ds C'
'br\}
.\"
.\" Escape single quotes in literal strings from groff's Unicode transform.
.ie \n(.g .ds Aq \(aq
.el       .ds Aq '
.\"
.\" If the F register is >0, we'll generate index entries on stderr for
.\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
.\" entries marked with X<> in POD.  Of course, you'll have to process the
.\" output yourself in some meaningful fashion.
.\"
.\" Avoid warning from groff about undefined register 'F'.
.de IX
..
.nr rF 0
.if \n(.g .if rF .nr rF 1
.if (\n(rF:(\n(.g==0)) \{\
.    if \nF \{\
.        de IX
.        tm Index:\\$1\t\\n%\t"\\$2"
..
.        if !\nF==2 \{\
.            nr % 0
.            nr F 2
.        \}
.    \}
.\}
.rr rF
.\" ========================================================================
.\"
.IX Title "virt-rescue 1"
.TH virt-rescue 1 2024-10-08 libguestfs-1.54.0 "Virtualization Support"
.\" For nroff, turn off justification.  Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
.nh
.SH NAME
virt\-rescue \- Run a rescue shell on a virtual machine
.SH SYNOPSIS
.IX Header "SYNOPSIS"
.Vb 1
\& virt\-rescue [\-\-options] \-d domname
\&
\& virt\-rescue [\-\-options] \-a disk.img [\-a disk.img ...] [\-i]
.Ve
.PP
Old style:
.PP
.Vb 1
\& virt\-rescue [\-\-options] domname
\&
\& virt\-rescue [\-\-options] disk.img [disk.img ...]
.Ve
.SH WARNING
.IX Header "WARNING"
Using \f(CW\*(C`virt\-rescue\*(C'\fR in write mode
on live virtual machines, or concurrently with other
disk editing tools, can be dangerous, potentially causing disk
corruption.  The virtual machine must be shut down before you use this
command, and disk images must not be edited concurrently.
.PP
Use the \fI\-\-ro\fR (read-only) option to use \f(CW\*(C`virt\-rescue\*(C'\fR safely if the disk
image or virtual machine might be live.  You may see strange or
inconsistent results if running concurrently with other changes, but
with this option you won't risk disk corruption.
.SH DESCRIPTION
.IX Header "DESCRIPTION"
virt-rescue is like a Rescue CD, but for virtual machines, and without
the need for a CD.  virt-rescue gives you a rescue shell and some
simple recovery tools which you can use to examine or rescue a virtual
machine or disk image.
.PP
You can run virt-rescue on any virtual machine known to libvirt, or
directly on disk image(s):
.PP
.Vb 1
\& virt\-rescue \-d GuestName \-i
\&
\& virt\-rescue \-\-ro \-a /path/to/disk.img \-i
\&
\& virt\-rescue \-a /dev/sdc
.Ve
.PP
For live VMs you \fImust\fR use the \fI\-\-ro\fR option.
.PP
When you run virt-rescue on a virtual machine or disk image, you are
placed in an interactive bash shell where you can use many ordinary
Linux commands.  What you see in \fI/\fR (\fI/bin\fR, \fI/lib\fR etc) is the
rescue appliance.  You must mount the virtual machine’s filesystems.
There is an empty directory called \fI/sysroot\fR where you can mount
filesystems.
.PP
To automatically mount the virtual machine’s filesystems under
\&\fI/sysroot\fR use the \fI\-i\fR option.  This uses libguestfs inspection to
find the filesystems and mount them in the right place.  You can also
mount filesystems individually using the \fI\-m\fR option.
.PP
Another way is to list the logical volumes (with \fBlvs\fR\|(8)) and
partitions (with \fBparted\fR\|(8)) and mount them by hand:
.PP
.Vb 7
\& ><rescue> lvs
\& LV      VG        Attr   LSize   Origin Snap%  Move Log Copy%  Convert
\& lv_root vg_f15x32 \-wi\-a\-   8.83G
\& lv_swap vg_f15x32 \-wi\-a\- 992.00M
\& ><rescue> mount /dev/vg_f15x32/lv_root /sysroot
\& ><rescue> mount /dev/vda1 /sysroot/boot
\& ><rescue> ls /sysroot
.Ve
.PP
Another command to list available filesystems is
\&\fBvirt\-filesystems\fR\|(1).
.PP
To run commands in a Linux guest (for example, grub), you should
chroot into the /sysroot directory first:
.PP
.Vb 1
\& ><rescue> chroot /sysroot
.Ve
.SS NOTES
.IX Subsection "NOTES"
Virt-rescue can be used on \fIany\fR disk image file or device, not just
a virtual machine.  For example you can use it on a blank file if you
want to partition that file (although we would recommend using
\&\fBguestfish\fR\|(1) instead as it is more suitable for this purpose).  You
can even use virt-rescue on things like USB drives, SD cards and hard
disks.
.PP
You can get virt-rescue to give you scratch disk(s) to play with.
This is useful for testing out Linux utilities (see \fI\-\-scratch\fR).
.PP
Virt-rescue does not require root.  You only need to run it as root if
you need root to open the disk image.
.PP
This tool is just designed for quick interactive hacking on a virtual
machine.  For more structured access to a virtual machine disk image,
you should use \fBguestfs\fR\|(3).  To get a structured shell that you can
use to make scripted changes to guests, use \fBguestfish\fR\|(1).
.SH OPTIONS
.IX Header "OPTIONS"
.IP \fB\-\-help\fR 4
.IX Item "--help"
Display brief help.
.IP "\fB\-a\fR FILE" 4
.IX Item "-a FILE"
.PD 0
.IP "\fB\-\-add\fR FILE" 4
.IX Item "--add FILE"
.PD
Add \f(CW\*(C`FILE\*(C'\fR which should be a disk image from a virtual machine.  If
the virtual machine has multiple block devices, you must supply all of
them with separate \fI\-a\fR options.
.Sp
The format of the disk image is auto-detected.  To override this and
force a particular format use the \fI\-\-format=..\fR option.
.IP "\fB\-a\fR URI" 4
.IX Item "-a URI"
.PD 0
.IP "\fB\-\-add\fR URI" 4
.IX Item "--add URI"
.PD
Add a remote disk.  See "ADDING REMOTE STORAGE" in \fBguestfish\fR\|(1).
.IP "\fB\-\-append\fR KERNELOPTS" 4
.IX Item "--append KERNELOPTS"
Pass additional options to the rescue kernel.
.IP \fB\-\-blocksize=512\fR 4
.IX Item "--blocksize=512"
.PD 0
.IP \fB\-\-blocksize=4096\fR 4
.IX Item "--blocksize=4096"
.IP \fB\-\-blocksize\fR 4
.IX Item "--blocksize"
.PD
This parameter sets the sector size of the disk image.  It affects all
explicitly added subsequent disks after this parameter.  Using
\&\fI\-\-blocksize\fR with no argument switches the disk sector size to the
default value which is usually 512 bytes.  See also
"guestfs_add_drive_opts" in \fBguestfs\fR\|(3).
.IP "\fB\-c\fR URI" 4
.IX Item "-c URI"
.PD 0
.IP "\fB\-\-connect\fR URI" 4
.IX Item "--connect URI"
.PD
If using libvirt, connect to the given \fIURI\fR.  If omitted, then we
connect to the default libvirt hypervisor.
.Sp
If you specify guest block devices directly (\fI\-a\fR), then libvirt is
not used at all.
.IP "\fB\-d\fR guest" 4
.IX Item "-d guest"
.PD 0
.IP "\fB\-\-domain\fR guest" 4
.IX Item "--domain guest"
.PD
Add all the disks from the named libvirt guest.  Domain UUIDs can be
used instead of names.
.IP "\fB\-e none\fR" 4
.IX Item "-e none"
Disable the escape key.
.IP "\fB\-e\fR KEY" 4
.IX Item "-e KEY"
Set the escape key to the given key sequence.  The default is \f(CW\*(C`^]\*(C'\fR.
To specify the escape key you can use:
.RS 4
.ie n .IP """^x""" 4
.el .IP \f(CW^x\fR 4
.IX Item "^x"
Control key + \f(CW\*(C`x\*(C'\fR key.
.ie n .IP """none""" 4
.el .IP \f(CWnone\fR 4
.IX Item "none"
\&\fI\-e none\fR means there is no escape key, escapes are disabled.
.RE
.RS 4
.Sp
See "ESCAPE KEY" below for further information.
.RE
.IP \fB\-\-format=raw|qcow2|..\fR 4
.IX Item "--format=raw|qcow2|.."
.PD 0
.IP \fB\-\-format\fR 4
.IX Item "--format"
.PD
The default for the \fI\-a\fR option is to auto-detect the format of the
disk image.  Using this forces the disk format for \fI\-a\fR options which
follow on the command line.  Using \fI\-\-format\fR with no argument
switches back to auto-detection for subsequent \fI\-a\fR options.
.Sp
For example:
.Sp
.Vb 1
\& virt\-rescue \-\-format=raw \-a disk.img
.Ve
.Sp
forces raw format (no auto-detection) for \fIdisk.img\fR.
.Sp
.Vb 1
\& virt\-rescue \-\-format=raw \-a disk.img \-\-format \-a another.img
.Ve
.Sp
forces raw format (no auto-detection) for \fIdisk.img\fR and reverts to
auto-detection for \fIanother.img\fR.
.Sp
If you have untrusted raw-format guest disk images, you should use
this option to specify the disk format.  This avoids a possible
security problem with malicious guests (CVE\-2010\-3851).
.IP \fB\-i\fR 4
.IX Item "-i"
.PD 0
.IP \fB\-\-inspector\fR 4
.IX Item "--inspector"
.PD
Using \fBvirt\-inspector\fR\|(1) code, inspect the disks looking for
an operating system and mount filesystems as they would be
mounted on the real virtual machine.
.Sp
The filesystems are mounted on \fI/sysroot\fR in the rescue environment.
.IP "\fB\-\-memsize\fR MB" 4
.IX Item "--memsize MB"
Change the amount of memory allocated to the rescue system.  The
default is set by libguestfs and is small but adequate for running
system tools.  The occasional program might need more memory.  The
parameter is specified in megabytes.
.IP "\fB\-m\fR dev[:mountpoint[:options[:fstype]]]" 4
.IX Item "-m dev[:mountpoint[:options[:fstype]]]"
.PD 0
.IP "\fB\-\-mount\fR dev[:mountpoint[:options[:fstype]]]" 4
.IX Item "--mount dev[:mountpoint[:options[:fstype]]]"
.PD
Mount the named partition or logical volume on the given mountpoint
\&\fBin the guest\fR (this has nothing to do with mountpoints in the host).
.Sp
If the mountpoint is omitted, it defaults to \fI/\fR.  You have to mount
something on \fI/\fR.
.Sp
The filesystems are mounted under \fI/sysroot\fR in the rescue environment.
.Sp
The third (and rarely used) part of the mount parameter is the list of
mount options used to mount the underlying filesystem.  If this is not
given, then the mount options are either the empty string or \f(CW\*(C`ro\*(C'\fR
(the latter if the \fI\-\-ro\fR flag is used).  By specifying the mount
options, you override this default choice.  Probably the only time you
would use this is to enable ACLs and/or extended attributes if the
filesystem can support them:
.Sp
.Vb 1
\& \-m /dev/sda1:/:acl,user_xattr
.Ve
.Sp
The fourth part of the parameter is the filesystem driver to use, such
as \f(CW\*(C`ext3\*(C'\fR or \f(CW\*(C`ntfs\*(C'\fR. This is rarely needed, but can be useful if
multiple drivers are valid for a filesystem (eg: \f(CW\*(C`ext2\*(C'\fR and \f(CW\*(C`ext3\*(C'\fR),
or if libguestfs misidentifies a filesystem.
.IP \fB\-\-network\fR 4
.IX Item "--network"
Enable QEMU user networking in the guest.  See "NETWORK".
.IP \fB\-r\fR 4
.IX Item "-r"
.PD 0
.IP \fB\-\-ro\fR 4
.IX Item "--ro"
.PD
Open the image read-only.
.Sp
The option must always be used if the disk image or virtual machine
might be running, and is generally recommended in cases where you
don't need write access to the disk.
.Sp
See also "OPENING DISKS FOR READ AND WRITE" in \fBguestfish\fR\|(1).
.IP \fB\-\-scratch\fR 4
.IX Item "--scratch"
.PD 0
.IP \fB\-\-scratch=N\fR 4
.IX Item "--scratch=N"
.PD
The \fI\-\-scratch\fR option adds a large scratch disk to the rescue
appliance.  \fI\-\-scratch=N\fR adds \f(CW\*(C`N\*(C'\fR scratch disks.  The scratch
disk(s) are deleted automatically when virt-rescue exits.
.Sp
You can also mix \fI\-a\fR, \fI\-d\fR and \fI\-\-scratch\fR options.  The scratch
disk(s) are added to the appliance in the order they appear on the
command line.
.IP \fB\-\-selinux\fR 4
.IX Item "--selinux"
This option is provided for backwards compatibility and does nothing.
.IP "\fB\-\-smp\fR N" 4
.IX Item "--smp N"
Enable N ≥ 2 virtual CPUs in the rescue appliance.
.IP \fB\-\-suggest\fR 4
.IX Item "--suggest"
This option was used in older versions of virt-rescue to suggest what
commands you could use to mount filesystems under \fI/sysroot\fR.  For
the current version of virt-rescue, it is easier to use the \fI\-i\fR
option instead.
.Sp
This option implies \fI\-\-ro\fR and is safe to use even if the guest is up
or if another virt-rescue is running.
.IP \fB\-v\fR 4
.IX Item "-v"
.PD 0
.IP \fB\-\-verbose\fR 4
.IX Item "--verbose"
.PD
Enable verbose messages for debugging.
.IP \fB\-V\fR 4
.IX Item "-V"
.PD 0
.IP \fB\-\-version\fR 4
.IX Item "--version"
.PD
Display version number and exit.
.IP \fB\-w\fR 4
.IX Item "-w"
.PD 0
.IP \fB\-\-rw\fR 4
.IX Item "--rw"
.PD
This changes the \fI\-a\fR, \fI\-d\fR and \fI\-m\fR options so that disks are
added and mounts are done read-write.
.Sp
See "OPENING DISKS FOR READ AND WRITE" in \fBguestfish\fR\|(1).
.IP \fB\-x\fR 4
.IX Item "-x"
Enable tracing of libguestfs API calls.
.SH "OLD-STYLE COMMAND LINE ARGUMENTS"
.IX Header "OLD-STYLE COMMAND LINE ARGUMENTS"
Previous versions of virt-rescue allowed you to write either:
.PP
.Vb 1
\& virt\-rescue disk.img [disk.img ...]
.Ve
.PP
or
.PP
.Vb 1
\& virt\-rescue guestname
.Ve
.PP
whereas in this version you should use \fI\-a\fR or \fI\-d\fR respectively
to avoid the confusing case where a disk image might have the same
name as a guest.
.PP
For compatibility the old style is still supported.
.SH NETWORK
.IX Header "NETWORK"
Adding the \fI\-\-network\fR option enables QEMU user networking
in the rescue appliance.  There are some differences between
user networking and ordinary networking:
.IP "ping does not work" 4
.IX Item "ping does not work"
Because the ICMP ECHO_REQUEST protocol generally requires root in
order to send the ping packets, and because virt-rescue must be able
to run as non-root, QEMU user networking is not able to emulate the
\&\fBping\fR\|(8) command.  The ping command will appear to resolve addresses
but will not be able to send or receive any packets.  This does not
mean that the network is not working.
.IP "cannot receive connections" 4
.IX Item "cannot receive connections"
QEMU user networking cannot receive incoming connections.
.IP "making TCP connections" 4
.IX Item "making TCP connections"
The virt-rescue appliance needs to be small and so does not include
many network tools.  In particular there is no \fBtelnet\fR\|(1) command.
You can make TCP connections from the shell using the magical
\&\fI/dev/tcp/<hostname>/<port>\fR syntax:
.Sp
.Vb 3
\& exec 3<>/dev/tcp/redhat.com/80
\& echo "GET /" >&3
\& cat <&3
.Ve
.Sp
See \fBbash\fR\|(1) for more details.
.SH "ESCAPE KEY"
.IX Header "ESCAPE KEY"
Virt-rescue supports various keyboard escape sequences which are
entered by pressing \f(CW\*(C`^]\*(C'\fR (Control key + \f(CW\*(C`]\*(C'\fR key).
.PP
You can change the escape key using the \fI\-e\fR option on the command
line (see above), and you can disable escapes completely using
\&\fI\-e none\fR.  The rest of this section assumes the default escape key.
.PP
The following escapes can be used:
.ie n .IP """^] ?""" 4
.el .IP "\f(CW^] ?\fR" 4
.IX Item "^] ?"
.PD 0
.ie n .IP """^] h""" 4
.el .IP "\f(CW^] h\fR" 4
.IX Item "^] h"
.PD
Prints a brief help text about escape sequences.
.ie n .IP """^] i""" 4
.el .IP "\f(CW^] i\fR" 4
.IX Item "^] i"
Prints brief libguestfs inspection information for the guest.  This
only works if you used \fI\-i\fR on the virt-rescue command line.
.ie n .IP """^] q""" 4
.el .IP "\f(CW^] q\fR" 4
.IX Item "^] q"
.PD 0
.ie n .IP """^] x""" 4
.el .IP "\f(CW^] x\fR" 4
.IX Item "^] x"
.PD
Quits virt-rescue immediately.
.ie n .IP """^] s""" 4
.el .IP "\f(CW^] s\fR" 4
.IX Item "^] s"
Synchronize the filesystems (sync).
.ie n .IP """^] u""" 4
.el .IP "\f(CW^] u\fR" 4
.IX Item "^] u"
Unmounts all the filesystems, except for the root (appliance)
filesystems.
.ie n .IP """^] z""" 4
.el .IP "\f(CW^] z\fR" 4
.IX Item "^] z"
Suspend virt-rescue (like pressing \f(CW\*(C`^Z\*(C'\fR except that it affects
virt-rescue rather than the program inside the rescue shell).
.ie n .IP """^] ^]""" 4
.el .IP "\f(CW^] ^]\fR" 4
.IX Item "^] ^]"
Sends the literal character \f(CW\*(C`^]\*(C'\fR (ASCII 0x1d) through to the rescue
shell.
.SH "CAPTURING CORE DUMPS"
.IX Header "CAPTURING CORE DUMPS"
If you are testing a tool inside virt-rescue and the tool (\fBnot\fR
virt-rescue) segfaults, it can be tricky to capture the core dump
outside virt-rescue for later analysis.  This section describes one
way to do this.
.IP 1. 4
Create a scratch disk for core dumps:
.Sp
.Vb 3
\& truncate \-s 4G /tmp/corefiles
\& virt\-format \-\-partition=mbr \-\-filesystem=ext2 \-a /tmp/corefiles
\& virt\-filesystems \-a /tmp/corefiles \-\-all \-\-long \-h
.Ve
.IP 2. 4
When starting virt-rescue, attach the core files disk last:
.Sp
.Vb 1
\& virt\-rescue \-\-rw [\-a ...] \-a /tmp/corefiles
.Ve
.Sp
\&\fBNB.\fR If you use the \fI\-\-ro\fR option, then virt-rescue will silently
not write any core files to \fI/tmp/corefiles\fR.
.IP 3. 4
Inside virt-rescue, mount the core files disk.  Note replace
\&\fI/dev/sdb1\fR with the last disk index.  For example if the core files
disk is the last of four disks, you would use \fI/dev/sdd1\fR.
.Sp
.Vb 2
\& ><rescue> mkdir /tmp/mnt
\& ><rescue> mount /dev/sdb1 /tmp/mnt
.Ve
.IP 4. 4
Enable core dumps in the rescue kernel:
.Sp
.Vb 3
\& ><rescue> echo \*(Aq/tmp/mnt/core.%p\*(Aq > /proc/sys/kernel/core_pattern
\& ><rescue> ulimit \-Hc unlimited
\& ><rescue> ulimit \-Sc unlimited
.Ve
.IP 5. 4
Run the tool that caused the core dump.  The core dump will be written
to \fI/tmp/mnt/core.PID\fR.
.Sp
.Vb 4
\& ><rescue> ls \-l /tmp/mnt
\& total 1628
\& \-rw\-\-\-\-\-\-\- 1 root root 1941504 Dec  7 13:13 core.130
\& drwx\-\-\-\-\-\- 2 root root   16384 Dec  7 13:00 lost+found
.Ve
.IP 6. 4
Before exiting virt-rescue, unmount (or at least sync) the disks:
.Sp
.Vb 2
\& ><rescue> umount /tmp/mnt
\& ><rescue> exit
.Ve
.IP 7. 4
Outside virt-rescue, the core dump(s) can be removed from the disk
using \fBguestfish\fR\|(1).  For example:
.Sp
.Vb 3
\& guestfish \-\-ro \-a /tmp/corefiles \-m /dev/sda1
\& ><fs> ll /
\& ><fs> download /core.NNN /tmp/core.NNN
.Ve
.SH "ENVIRONMENT VARIABLES"
.IX Header "ENVIRONMENT VARIABLES"
Several environment variables affect virt-rescue.  See
"ENVIRONMENT VARIABLES" in \fBguestfs\fR\|(3) for the complete list.
.SH FILES
.IX Header "FILES"
.ie n .IP $XDG_CONFIG_HOME/libguestfs/libguestfs\-tools.conf 4
.el .IP \f(CW$XDG_CONFIG_HOME\fR/libguestfs/libguestfs\-tools.conf 4
.IX Item "$XDG_CONFIG_HOME/libguestfs/libguestfs-tools.conf"
.PD 0
.ie n .IP $HOME/.libguestfs\-tools.rc 4
.el .IP \f(CW$HOME\fR/.libguestfs\-tools.rc 4
.IX Item "$HOME/.libguestfs-tools.rc"
.ie n .IP $XDG_CONFIG_DIRS/libguestfs/libguestfs\-tools.conf 4
.el .IP \f(CW$XDG_CONFIG_DIRS\fR/libguestfs/libguestfs\-tools.conf 4
.IX Item "$XDG_CONFIG_DIRS/libguestfs/libguestfs-tools.conf"
.IP /etc/libguestfs\-tools.conf 4
.IX Item "/etc/libguestfs-tools.conf"
.PD
This configuration file controls the default read-only or read-write
mode (\fI\-\-ro\fR or \fI\-\-rw\fR).
.Sp
See \fBlibguestfs\-tools.conf\fR\|(5).
.SH "SEE ALSO"
.IX Header "SEE ALSO"
\&\fBguestfs\fR\|(3),
\&\fBguestfish\fR\|(1),
\&\fBvirt\-cat\fR\|(1),
\&\fBvirt\-edit\fR\|(1),
\&\fBvirt\-filesystems\fR\|(1),
\&\fBlibguestfs\-tools.conf\fR\|(5),
http://libguestfs.org/.
.SH AUTHOR
.IX Header "AUTHOR"
Richard W.M. Jones http://people.redhat.com/~rjones/
.SH COPYRIGHT
.IX Header "COPYRIGHT"
Copyright (C) 2009\-2023 Red Hat Inc.
.SH LICENSE
.IX Header "LICENSE"
This 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.
.PP
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.
.PP
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.
.SH BUGS
.IX Header "BUGS"
To get a list of bugs against libguestfs, use this link:
https://bugzilla.redhat.com/buglist.cgi?component=libguestfs&product=Virtualization+Tools
.PP
To report a new bug against libguestfs, use this link:
https://bugzilla.redhat.com/enter_bug.cgi?component=libguestfs&product=Virtualization+Tools
.PP
When reporting a bug, please supply:
.IP \(bu 4
The version of libguestfs.
.IP \(bu 4
Where you got libguestfs (eg. which Linux distro, compiled from source, etc)
.IP \(bu 4
Describe the bug accurately and give a way to reproduce it.
.IP \(bu 4
Run \fBlibguestfs\-test\-tool\fR\|(1) and paste the \fBcomplete, unedited\fR
output into the bug report.