.\" Automatically generated by Podwrapper::Man 1.44.2 (Pod::Simple 3.40)
.\"
.\" 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
..
.\" Set up some character translations and predefined strings.  \*(-- will
.\" give an unbreakable dash, \*(PI will give pi, \*(L" will give a left
.\" double quote, and \*(R" will give a right double quote.  \*(C+ will
.\" give a nicer C++.  Capital omega is used to do unbreakable dashes and
.\" therefore won't be available.  \*(C` and \*(C' expand to `' in nroff,
.\" nothing in troff, for use with C<>.
.tr \(*W-
.ds C+ C\v'-.1v'\h'-1p'\s-2+\h'-1p'+\s0\v'.1v'\h'-1p'
.ie n \{\
.    ds -- \(*W-
.    ds PI pi
.    if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch
.    if (\n(.H=4u)&(1m=20u) .ds -- \(*W\h'-12u'\(*W\h'-8u'-\"  diablo 12 pitch
.    ds L" ""
.    ds R" ""
.    ds C` ""
.    ds C' ""
'br\}
.el\{\
.    ds -- \|\(em\|
.    ds PI \(*p
.    ds L" ``
.    ds R" ''
.    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 "guestmount 1"
.TH guestmount 1 "2021-09-07" "libguestfs-1.44.2" "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"
guestmount \- Mount a guest filesystem on the host using FUSE and libguestfs
.SH "SYNOPSIS"
.IX Header "SYNOPSIS"
.Vb 1
\& guestmount [\-\-options] \-a disk.img \-m device [\-\-ro] mountpoint
\&
\& guestmount [\-\-options] \-a disk.img \-i [\-\-ro] mountpoint
\&
\& guestmount [\-\-options] \-d Guest \-i [\-\-ro] mountpoint
.Ve
.SH "WARNING"
.IX Header "WARNING"
Using \f(CW\*(C`guestmount\*(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`guestmount\*(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"
The guestmount program can be used to mount virtual machine
filesystems and other disk images on the host.  It uses libguestfs for
access to the guest filesystem, and \s-1FUSE\s0 (the \*(L"filesystem in
userspace\*(R") to make it appear as a mountable device.
.PP
Along with other options, you have to give at least one device (\fI\-a\fR
option) or libvirt domain (\fI\-d\fR option), and at least one mountpoint
(\fI\-m\fR option) or use the \fI\-i\fR inspection option or the \fI\-\-live\fR
option.  How this works is better explained in the \fBguestfish\fR\|(1)
manual page, or by looking at the examples below.
.PP
\&\s-1FUSE\s0 lets you mount filesystems as non-root.  The mountpoint must be
owned by you.  The filesystem will not be visible to any other users
unless you make configuration changes, see \*(L"\s-1NOTES\*(R"\s0 below.
.PP
To unmount the filesystem, use the \fBguestunmount\fR\|(1) command.
.SH "EXAMPLES"
.IX Header "EXAMPLES"
For a typical Windows guest which has its main filesystem on the
first partition:
.PP
.Vb 1
\& guestmount \-a windows.img \-m /dev/sda1 \-\-ro /mnt
.Ve
.PP
For a typical Linux guest which has a /boot filesystem on the first
partition, and the root filesystem on a logical volume:
.PP
.Vb 1
\& guestmount \-a linux.img \-m /dev/VG/LV \-m /dev/sda1:/boot \-\-ro /mnt
.Ve
.PP
To get libguestfs to detect guest mountpoints for you:
.PP
.Vb 1
\& guestmount \-a guest.img \-i \-\-ro /mnt
.Ve
.PP
For a libvirt guest called \*(L"Guest\*(R" you could do:
.PP
.Vb 1
\& guestmount \-d Guest \-i \-\-ro /mnt
.Ve
.PP
If you don’t know what filesystems are contained in a guest or
disk image, use \fBvirt\-filesystems\fR\|(1) first:
.PP
.Vb 1
\& virt\-filesystems \-d MyGuest
.Ve
.PP
If you want to trace the libguestfs calls but without excessive
debugging information, we recommend:
.PP
.Vb 1
\& guestmount [...] \-\-trace /mnt
.Ve
.PP
If you want to debug the program, we recommend:
.PP
.Vb 1
\& guestmount [...] \-\-trace \-\-verbose /mnt
.Ve
.PP
To unmount the filesystem after using it:
.PP
.Vb 1
\& guestunmount /mnt
.Ve
.SH "NOTES"
.IX Header "NOTES"
.SS "Other users cannot see the filesystem by default"
.IX Subsection "Other users cannot see the filesystem by default"
If you mount a filesystem as one user (eg. root), then other users
will not be able to see it by default.  The fix is to add the \s-1FUSE\s0
\&\f(CW\*(C`allow_other\*(C'\fR option when mounting:
.PP
.Vb 1
\& sudo guestmount [...] \-o allow_other /mnt
.Ve
.PP
\&\fBand\fR to enable this option in \fI/etc/fuse.conf\fR.
.SS "Enabling \s-1FUSE\s0"
.IX Subsection "Enabling FUSE"
On some distros, you may need to add yourself to a special group
(eg. \f(CW\*(C`fuse\*(C'\fR) before you can use any \s-1FUSE\s0 filesystem.  This is
necessary on Debian and derivatives.
.PP
On other distros, no special group is required.  It is not necessary
on Fedora or Red Hat Enterprise Linux.
.ie n .SS "fusermount error: ""Device or resource busy"""
.el .SS "fusermount error: ``Device or resource busy''"
.IX Subsection "fusermount error: Device or resource busy"
You can see this error when another process on the system jumps into
the mountpoint you have just created, holding it open and preventing
you from unmounting it.  The usual culprits are various \s-1GUI\s0 \*(L"indexing\*(R"
programs.
.PP
The popular workaround for this problem is to retry the \f(CW\*(C`fusermount \-u\*(C'\fR
command a few times until it works (\fBguestunmount\fR\|(1) does this
for you).  Unfortunately this isn't a reliable fix if (for example)
the mounted filesystem is particularly large and the intruding program
particularly persistent.
.PP
A proper fix is to use a private mountpoint by creating a new mount
namespace using the Linux-specific \fBclone\fR\|(2)/\fBunshare\fR\|(2) flag
\&\f(CW\*(C`CLONE_NEWNS\*(C'\fR.  Unfortunately at the moment this requires root and we
would also probably need to add it as a feature to guestmount.
.SS "Race conditions possible when shutting down the connection"
.IX Subsection "Race conditions possible when shutting down the connection"
When \fBguestunmount\fR\|(1)/\fBfusermount\fR\|(1) exits, guestmount may still
be running and cleaning up the mountpoint.  The disk image will not be
fully finalized.
.PP
This means that scripts like the following have a nasty race
condition:
.PP
.Vb 4
\& guestmount \-a disk.img \-i /mnt
\& # copy things into /mnt
\& guestunmount /mnt
\& # immediately try to use \*(Aqdisk.img\*(Aq ** UNSAFE **
.Ve
.PP
The solution is to use the \fI\-\-pid\-file\fR option to write the
guestmount \s-1PID\s0 to a file, then after guestunmount spin waiting for
this \s-1PID\s0 to exit.
.PP
.Vb 1
\& guestmount \-a disk.img \-i \-\-pid\-file guestmount.pid /mnt
\& 
\& # ...
\& # ...
\& 
\& # Save the PID of guestmount *before* calling guestunmount.
\& pid="$(cat guestmount.pid)"
\& 
\& # Unmount the filesystem.
\& guestunmount /mnt
\& 
\& timeout=10
\& 
\& count=$timeout
\& while kill \-0 "$pid" 2>/dev/null && [ $count \-gt 0 ]; do
\&     sleep 1
\&     ((count\-\-))
\& done
\& if [ $count \-eq 0 ]; then
\&     echo "$0: wait for guestmount to exit failed after $timeout seconds"
\&     exit 1
\& fi
\& 
\& # Now it is safe to use the disk image.
.Ve
.PP
Note that if you use the \f(CW\*(C`guestfs_mount_local\*(C'\fR \s-1API\s0 directly (see
\&\*(L"\s-1MOUNT LOCAL\*(R"\s0 in \fBguestfs\fR\|(3)) then it is much easier to write a safe,
race-free program.
.SH "OPTIONS"
.IX Header "OPTIONS"
.IP "\fB\-a\fR \s-1IMAGE\s0" 4
.IX Item "-a IMAGE"
.PD 0
.IP "\fB\-\-add\fR \s-1IMAGE\s0" 4
.IX Item "--add IMAGE"
.PD
Add a block device or virtual machine image.
.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 \s-1URI\s0" 4
.IX Item "-a URI"
.PD 0
.IP "\fB\-\-add\fR \s-1URI\s0" 4
.IX Item "--add URI"
.PD
Add a remote disk.  See \*(L"\s-1ADDING REMOTE STORAGE\*(R"\s0 in \fBguestfish\fR\|(1).
.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
\&\*(L"guestfs_add_drive_opts\*(R" in \fBguestfs\fR\|(3).
.IP "\fB\-c\fR \s-1URI\s0" 4
.IX Item "-c URI"
.PD 0
.IP "\fB\-\-connect\fR \s-1URI\s0" 4
.IX Item "--connect URI"
.PD
When used in conjunction with the \fI\-d\fR option, this specifies
the libvirt \s-1URI\s0 to use.  The default is to use the default libvirt
connection.
.IP "\fB\-d\fR LIBVIRT-DOMAIN" 4
.IX Item "-d LIBVIRT-DOMAIN"
.PD 0
.IP "\fB\-\-domain\fR LIBVIRT-DOMAIN" 4
.IX Item "--domain LIBVIRT-DOMAIN"
.PD
Add disks from the named libvirt domain.  If the \fI\-\-ro\fR option is
also used, then any libvirt domain can be used.  However in write
mode, only libvirt domains which are shut down can be named here.
.Sp
Domain UUIDs can be used instead of names.
.IP "\fB\-\-dir\-cache\-timeout\fR N" 4
.IX Item "--dir-cache-timeout N"
Set the readdir cache timeout to \fIN\fR seconds, the default being 60
seconds.  The readdir cache [actually, there are several
semi-independent caches] is populated after a \fBreaddir\fR\|(2) call with the
stat and extended attributes of the files in the directory, in
anticipation that they will be requested soon after.
.Sp
There is also a different attribute cache implemented by \s-1FUSE\s0
(see the \s-1FUSE\s0 option \fI\-o attr_timeout\fR), but the \s-1FUSE\s0 cache
does not anticipate future requests, only cache existing ones.
.IP "\fB\-\-echo\-keys\fR" 4
.IX Item "--echo-keys"
When prompting for keys and passphrases, guestfish normally turns
echoing off so you cannot see what you are typing.  If you are not
worried about Tempest attacks and there is no one else in the room
you can specify this flag to see what you are typing.
.IP "\fB\-\-fd=\fR\s-1FD\s0" 4
.IX Item "--fd=FD"
Specify a pipe or eventfd file descriptor.  When the mountpoint is
ready to be used, guestmount writes a single byte to this file
descriptor.  This can be used in conjunction with \fI\-\-no\-fork\fR in
order to run guestmount captive under another process.
.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
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 (\s-1CVE\-2010\-3851\s0).  See also
\&\*(L"guestfs_add_drive_opts\*(R" in \fBguestfs\fR\|(3).
.IP "\fB\-\-fuse\-help\fR" 4
.IX Item "--fuse-help"
Display help on special \s-1FUSE\s0 options (see \fI\-o\fR below).
.IP "\fB\-\-help\fR" 4
.IX Item "--help"
Display brief help and exit.
.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.
.IP "\fB\-\-key\fR \s-1SELECTOR\s0" 4
.IX Item "--key SELECTOR"
Specify a key for \s-1LUKS,\s0 to automatically open a \s-1LUKS\s0 device when using
the inspection.  \f(CW\*(C`ID\*(C'\fR can be either the libguestfs device name, or
the \s-1UUID\s0 of the \s-1LUKS\s0 device.
.RS 4
.ie n .IP "\fB\-\-key\fR ""ID"":key:KEY_STRING" 4
.el .IP "\fB\-\-key\fR \f(CWID\fR:key:KEY_STRING" 4
.IX Item "--key ID:key:KEY_STRING"
Use the specified \f(CW\*(C`KEY_STRING\*(C'\fR as passphrase.
.ie n .IP "\fB\-\-key\fR ""ID"":file:FILENAME" 4
.el .IP "\fB\-\-key\fR \f(CWID\fR:file:FILENAME" 4
.IX Item "--key ID:file:FILENAME"
Read the passphrase from \fI\s-1FILENAME\s0\fR.
.RE
.RS 4
.RE
.IP "\fB\-\-keys\-from\-stdin\fR" 4
.IX Item "--keys-from-stdin"
Read key or passphrase parameters from stdin.  The default is
to try to read passphrases from the user by opening \fI/dev/tty\fR.
.Sp
If there are multiple encrypted devices then you may need to supply
multiple keys on stdin, one per line.
.IP "\fB\-\-live\fR" 4
.IX Item "--live"
Connect to a live virtual machine.
(Experimental, see \*(L"\s-1ATTACHING TO RUNNING DAEMONS\*(R"\s0 in \fBguestfs\fR\|(3)).
.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 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\-\-no\-fork\fR" 4
.IX Item "--no-fork"
Don’t daemonize (or fork into the background).
.IP "\fB\-n\fR" 4
.IX Item "-n"
.PD 0
.IP "\fB\-\-no\-sync\fR" 4
.IX Item "--no-sync"
.PD
By default, we attempt to sync the guest disk when the \s-1FUSE\s0 mountpoint
is unmounted.  If you specify this option, then we don't attempt to
sync the disk.  See the discussion of autosync in the \fBguestfs\fR\|(3)
manpage.
.IP "\fB\-o\fR \s-1OPTION\s0" 4
.IX Item "-o OPTION"
.PD 0
.IP "\fB\-\-option\fR \s-1OPTION\s0" 4
.IX Item "--option OPTION"
.PD
Pass extra options to \s-1FUSE.\s0
.Sp
To get a list of all the extra options supported by \s-1FUSE,\s0 use the
command below.  Note that only the \s-1FUSE\s0 \fI\-o\fR options can be passed,
and only some of them are a good idea.
.Sp
.Vb 1
\& guestmount \-\-fuse\-help
.Ve
.Sp
Some potentially useful \s-1FUSE\s0 options:
.RS 4
.IP "\fB\-o\fR \fBallow_other\fR" 4
.IX Item "-o allow_other"
Allow other users to see the filesystem.  This option has no effect
unless you enable it globally in \fI/etc/fuse.conf\fR.
.IP "\fB\-o\fR \fBattr_timeout=N\fR" 4
.IX Item "-o attr_timeout=N"
Enable attribute caching by \s-1FUSE,\s0 and set the timeout to \fIN\fR seconds.
.IP "\fB\-o\fR \fBkernel_cache\fR" 4
.IX Item "-o kernel_cache"
Allow the kernel to cache files (reduces the number of reads
that have to go through the \fBguestfs\fR\|(3) \s-1API\s0).  This is generally
a good idea if you can afford the extra memory usage.
.IP "\fB\-o\fR \fBuid=N\fR \fB\-o\fR \fBgid=N\fR" 4
.IX Item "-o uid=N -o gid=N"
Use these options to map all UIDs and GIDs inside the guest filesystem
to the chosen values.
.IP "\fB\-o\fR \fBuse_ino\fR" 4
.IX Item "-o use_ino"
Preserve inode numbers from the underlying filesystem.
.Sp
Without this option, \s-1FUSE\s0 makes up its own inode numbers.  The inode
numbers you see in \fBstat\fR\|(2), \f(CW\*(C`ls \-i\*(C'\fR etc aren't the inode numbers
of the underlying filesystem.
.Sp
\&\fBNote\fR this option is potentially dangerous if the underlying
filesystem consists of multiple mountpoints, as you may see duplicate
inode numbers appearing through \s-1FUSE.\s0  Use of this option can confuse
some software.
.RE
.RS 4
.RE
.IP "\fB\-\-pid\-file\fR \s-1FILENAME\s0" 4
.IX Item "--pid-file FILENAME"
Write the \s-1PID\s0 of the guestmount worker process to \f(CW\*(C`filename\*(C'\fR.
.IP "\fB\-r\fR" 4
.IX Item "-r"
.PD 0
.IP "\fB\-\-ro\fR" 4
.IX Item "--ro"
.PD
Add devices and mount everything read-only.  Also disallow writes and
make the disk appear read-only to \s-1FUSE.\s0
.Sp
This is highly recommended if you are not going to edit the guest
disk.  If the guest is running and this option is \fInot\fR supplied,
then there is a strong risk of disk corruption in the guest.  We try
to prevent this from happening, but it is not always possible.
.Sp
See also \*(L"\s-1OPENING DISKS FOR READ AND WRITE\*(R"\s0 in \fBguestfish\fR\|(1).
.IP "\fB\-\-selinux\fR" 4
.IX Item "--selinux"
This option is provided for backwards compatibility and does nothing.
.IP "\fB\-v\fR" 4
.IX Item "-v"
.PD 0
.IP "\fB\-\-verbose\fR" 4
.IX Item "--verbose"
.PD
Enable verbose messages from underlying libguestfs.
.IP "\fB\-V\fR" 4
.IX Item "-V"
.PD 0
.IP "\fB\-\-version\fR" 4
.IX Item "--version"
.PD
Display the program version 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 \*(L"\s-1OPENING DISKS FOR READ AND WRITE\*(R"\s0 in \fBguestfish\fR\|(1).
.IP "\fB\-x\fR" 4
.IX Item "-x"
.PD 0
.IP "\fB\-\-trace\fR" 4
.IX Item "--trace"
.PD
Trace libguestfs calls and entry into each \s-1FUSE\s0 function.
.Sp
This also stops the daemon from forking into the background
(see \fI\-\-no\-fork\fR).
.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 "EXIT STATUS"
.IX Header "EXIT STATUS"
This program returns 0 if successful, or non-zero if there was an
error.
.SH "SEE ALSO"
.IX Header "SEE ALSO"
\&\fBguestunmount\fR\|(1),
\&\fBfusermount\fR\|(1),
\&\fBguestfish\fR\|(1),
\&\fBvirt\-inspector\fR\|(1),
\&\fBvirt\-cat\fR\|(1),
\&\fBvirt\-edit\fR\|(1),
\&\fBvirt\-tar\fR\|(1),
\&\fBlibguestfs\-tools.conf\fR\|(5),
\&\*(L"\s-1MOUNT LOCAL\*(R"\s0 in \fBguestfs\fR\|(3),
http://libguestfs.org/,
http://fuse.sf.net/.
.SH "AUTHORS"
.IX Header "AUTHORS"
Richard W.M. Jones (\f(CW\*(C`rjones at redhat dot com\*(C'\fR)
.SH "COPYRIGHT"
.IX Header "COPYRIGHT"
Copyright (C) 2009\-2020 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 \s-1GNU\s0 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
\&\s-1WITHOUT ANY WARRANTY\s0; without even the implied warranty of
\&\s-1MERCHANTABILITY\s0 or \s-1FITNESS FOR A PARTICULAR PURPOSE.\s0  See the \s-1GNU\s0
General Public License for more details.
.PP
You should have received a copy of the \s-1GNU\s0 General Public License along
with this program; if not, write to the Free Software Foundation, Inc.,
51 Franklin Street, Fifth Floor, Boston, \s-1MA 02110\-1301 USA.\s0
.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.