virt-edit [--options] disk.img [disk.img ...] file
+=head1 WARNING
+
+You must I<not> use C<virt-edit> on live virtual machines. If you do
+this, you risk disk corruption in the VM. C<virt-edit> tries to stop
+you from doing this, but doesn't catch all cases.
+
=head1 DESCRIPTION
C<virt-edit> is a command line tool to edit C<file> where C<file>
exists in the named virtual machine (or disk image).
-B<Note> you must I<not> use virt-edit on live virtual machines. If
-you do this, you risk disk corruption in the VM.
-
If you want to just view a file, use L<virt-cat(1)>. For more complex
cases you should look at the L<guestfish(1)> tool.
virt-rescue [--options] disk.img [disk.img ...]
+=head1 WARNING
+
+You must I<not> use C<virt-rescue> on live virtual machines. Doing so
+will probably result in disk corruption in the VM. C<virt-rescue>
+tries to stop you from doing this, but doesn't catch all cases.
+
+However if you use the I<--ro> (read only) option, then you can attach
+a shell to a live virtual machine, but the results might be strange or
+inconsistent at times (but you won't get disk corruption).
+
=head1 DESCRIPTION
virt-rescue gives you a rescue shell and some simple recovery tools
# mount /dev/vg_f11x64/lv_root /sysroot
# ls /sysroot
-B<Note> that the virtual machine must not be powered on when you use
-this tool. Doing so will probably result in disk corruption in the
-VM. However if you use the I<--ro> (read only) option, then you can
-attach a shell to a running machine, but the results might be strange
-or inconsistent.
-
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 L<guestfs(3)>. To get a structured shell, use