*** Bug 731035 has been marked as a duplicate of this bug. ***
note: 3.1 has 'clone vm from snapshot' which solves some of this use case.
(In reply to comment #3) > note: 3.1 has 'clone vm from snapshot' which solves some of this use case. Itamar, why some and not all? i.e. why isn't this closed currentrelease?
(In reply to comment #4) > (In reply to comment #3) > > note: 3.1 has 'clone vm from snapshot' which solves some of this use case. > > Itamar, why some and not all? i.e. why isn't this closed currentrelease? because it forces user to create a snapshot. i want to stand on a VM and either: 1. clone it while it is down 2. have the system create the snapshot and delete it later. personally i'm fine with providing #1 in this RFE (cold clone), and relying on something like storage based snapshots for #2 when they are available.
is cold clone enough here, or live clone needed as well? I suggest we separate the two, as the former is easier.
If you mean "cold" in that you would have to shut down the VM in order to one-click clone, then, no, "cold" is not enough. The ideal situation is to take any VM, regardless of state (running, stopped, template, etc) and be able to right-click and create a new instance of whatever it is. Cold clone is definitely a step forward from where we are today, but it's not "enough".
we'll try to see how complicated is it through snapshots which would work both for off and running VMs
Verified using vt7: rhevm-3.5.sanlock-2.8-1.el6.x86_64 libvirt-0.10.2-46.el6_6.1.x86_64 qemu-kvm-rhev-0.12.1.2-2.448.el6.x86_64 vdsm-4.16.7.1-1.el6ev.x86_64 0-0.17.beta.el6ev.noarch Aslo bug 1128150 is related to this PRD.
Posting original request: 2) What is the nature and description of the request? The user would like to be able to duplicate virtual machines directly for staging and other tests without having to create a template. 3) Why is it needed? This is both for convenience and performance issues. The time and storage required is more than should be necessary for making a single duplicate of a vm. 4) Functional requirements: Select a vm, and either click a "clone" button or have a "clone" option in the context menu
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2015-0158.html