summaryrefslogtreecommitdiffstats
path: root/tools
diff options
context:
space:
mode:
authorRichard Jones <rjones@redhat.com>2010-04-12 12:17:08 +0100
committerRichard Jones <rjones@redhat.com>2010-04-12 16:35:47 +0100
commitc53e64a156526adcb9937f63756f17f585f202d3 (patch)
tree7e8ad8902136723632325abd4fe405da2e9de92f /tools
parentde5607909b59d9068f64d87c4d9351286a873b42 (diff)
downloadlibguestfs-c53e64a156526adcb9937f63756f17f585f202d3.tar.gz
libguestfs-c53e64a156526adcb9937f63756f17f585f202d3.tar.xz
libguestfs-c53e64a156526adcb9937f63756f17f585f202d3.zip
virt-resize: Mention alternate tools like gparted in the documentation.
Diffstat (limited to 'tools')
-rwxr-xr-xtools/virt-resize17
1 files changed, 17 insertions, 0 deletions
diff --git a/tools/virt-resize b/tools/virt-resize
index ec1b5341..5ced4ddc 100755
--- a/tools/virt-resize
+++ b/tools/virt-resize
@@ -1219,6 +1219,22 @@ Windows may initiate a lengthy "chkdsk" on first boot after a resize,
if NTFS partitions have been expanded. This is just a safety check
and (unless it find errors) is nothing to worry about.
+=head1 ALTERNATIVE TOOLS
+
+There are several proprietary tools for resizing partitions. We
+won't mention any here.
+
+L<parted(8)> and its graphical shell gparted can do some types of
+resizing operations on disk images. They can resize and move
+partitions, but I don't think they can do anything with the contents,
+and they certainly don't understand LVM.
+
+L<guestfish(1)> can do everything that virt-resize can do and a lot
+more, but at a much lower level. You will probably end up
+hand-calculating sector offsets, which is something that virt-resize
+was designed to avoid. If you want to see the guestfish-equivalent
+commands that virt-resize runs, use the C<--debug> flag.
+
=head1 SEE ALSO
L<virt-list-partitions(1)>,
@@ -1232,6 +1248,7 @@ L<lvresize(8)>,
L<resize2fs(8)>,
L<ntfsresize(8)>,
L<virsh(1)>,
+L<parted(8)>,
L<Sys::Guestfs(3)>,
L<http://libguestfs.org/>.