Backlog #2637

Clone a running virtual machine to another instance

Added by Kiran Ranjane over 7 years ago. Updated over 3 years ago.

Status:ClosedStart date:01/13/2014
Priority:HighDue date:
Assignee:-% Done:

0%

Category:Core & System
Target version:-

Description

Instead of reverting the VM directly to a particular snapshot we can clone it and check if data is intact on that particular snapshot, also this feature will help in checking the integrity of the snapshot. We should have option of linked or full clone option while cloning from snapshot.

This functionality should work without snapshoting, i.e. clonning a complete VM from a running (or suspended/stopped) state.


Related issues

Related to Feature #2051: Clone a VM Closed 05/15/2013

History

#1 Updated by Ruben S. Montero over 7 years ago

  • Tracker changed from Feature to Request

Moving temporarily it to Request track

#2 Updated by Ruben S. Montero over 7 years ago

  • Tracker changed from Request to Backlog
  • Subject changed from Clone a virtual machine from a given point in time snapshot. to Clone a running virtual machine to another instance
  • Description updated (diff)
  • Category set to Core & System
  • Priority changed from Normal to High

Just re-word the issue to be more generic. This is very interesting indeed.

#3 Updated by Carlos Martín over 7 years ago

#4 Updated by Ruben S. Montero about 7 years ago

Consider saving only template information. From the mailing list:

It seems to be, although the empasis of #2637 seems to be on the entire
vm including image or image snapshot. I was thinking about templates. In
order to fix #2637 it should be possible to clone a vm template as well.
You might split this functionality into two parts:

- save
- clone

Saving would commit changes to original template, cloning would create a
new template and possibly image for a new vm based on current vm.

#5 Updated by Ruben S. Montero over 3 years ago

  • Status changed from Pending to Closed

Also available in: Atom PDF