[Pkg-libvirt-commits] [libguestfs] 92/233: builder: Add note about cloning to man page.

Hilko Bengen bengen at moszumanska.debian.org
Wed Feb 19 21:11:21 UTC 2014


This is an automated email from the git hooks/post-receive script.

bengen pushed a commit to branch experimental
in repository libguestfs.

commit be5fd2fd349af5e306c7e139a23548c351701015
Author: Richard W.M. Jones <rjones at redhat.com>
Date:   Tue Jan 21 17:13:18 2014 +0000

    builder: Add note about cloning to man page.
---
 builder/virt-builder.pod | 18 ++++++++++++++++++
 1 file changed, 18 insertions(+)

diff --git a/builder/virt-builder.pod b/builder/virt-builder.pod
index 9e433e4..eee5492 100644
--- a/builder/virt-builder.pod
+++ b/builder/virt-builder.pod
@@ -1629,6 +1629,24 @@ etc are truly random when the guest boots.
 
 You should check digital signatures and not ignore any signing errors.
 
+=head2 CLONES
+
+If you wish to create many new guests of the same type, it is tempting
+to run virt-builder once and then copy the output file.  You should
+B<not> do this.  You should run virt-builder once for each new guest
+you need.
+
+The reason is that each clone needs to have (at least) a separate
+random seed, and possibly other unique features (such as filesystem
+UUIDs) in future versions of virt-builder.
+
+Another thing you should I<not> do is to boot the guest, then clone
+the booted disk image.  The reason is that some guests create unique
+machine IDs, SSH host keys and so on at first boot, and you would not
+want clones to have duplicate identities.
+
+See also: L<virt-sysprep(1)>.
+
 =head2 PERFORMANCE
 
 The most important aspect of getting good performance is caching.

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-libvirt/libguestfs.git



More information about the Pkg-libvirt-commits mailing list