Red Hat Bugzilla – Bug 878170
virt-clone(1) needs to reference virt-sysprep(1)
Last modified: 2014-02-01 15:21:49 EST
Description of problem:
virt-clone(1) manpage does not reference virt-sysprep(1).
Version-Release number of selected component (if applicable):
I checked on RHEL6 and on the Fedora 17 manpage online:
Steps to Reproduce:
1. Run `man virt-clone` on the command-line.
2. Read through the manpage, or search for sysprep.
I have run virt-clone to clone a VM and am wondering why the VM sometimes ends up (for example) with eth1 configured instead of eth0. I read the virt-clone(1) manpage but find nothing helpful in it. I throw my hands up in despair and give up on virt-clone as a useful tool.
I have run virt-clone to clone a VM and have seen the aforementioned problem. I read the virt-clone(1) manpage and realise that I should run the virt-sysprep(1) command as prior to running virt-clone. I find virt-clone, together with virt-sysprep, to be a useful and reliable tool that makes my life easier.
virt-clone(1) is in the package python-virtinst.
virt-sysprep(1) is in the package libguestfs-tools.
Moving to the upstream tracker
*** Bug 912993 has been marked as a duplicate of this bug. ***
virtinst has been merged into virt-manager.git. Moving all virtinst bugs to the virt-manager component.
virt-manager clone wizard should also explicitly point to virt-sysprep and mention potential issues with our dumb clone operation, like lack of network connectivity. or maybe a wiki page somewhere
*** This bug has been marked as a duplicate of bug 912993 ***