[one-users] Question about tm_mv.sh

Javier Fontan jfontan at fdi.ucm.es
Fri Feb 13 03:01:25 PST 2009


Stop is not shutdown, it is like suspend but transfers the images back  
to the frontend machine so this VM can be resumed in other physical  
node. After you resume the VM it is rescheduled and a new physical  
node is selected, images are transferred from the frontend to the node  
and the VM is resumed.


On Feb 13, 2009, at 8:21 AM, Niraj Tolia wrote:

> Hi,
> So, I was playing with OpenNebula's and seeing how its Transfer
> Manager plugins would be modified to work with a SAN. I seem to have
> figured it out but I am confused about why tm_mv.sh is being called
> when an image is marked with DISK = [clone = "no", ...] and the VM is
> stopped.
> [1] says that only "if the save qualifier is activated the image will
> be saved for later use under $ONE_LOCATION/var/<VID>/images." However,
> my VM template has no save section specified and [2] indicates that it
> should be OFF by default. So, is this a bug in the code and/or the
> documentation or am I misunderstanding something?
> Cheers,
> Niraj
> [1] http://www.opennebula.org/doku.php?id=documentation:rel1.2:sm
> [2] http://www.opennebula.org/doku.php?id=documentation:rel1.2:ug
> _______________________________________________
> Users mailing list
> Users at lists.opennebula.org
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org

Javier Fontan, Grid & Virtualization Technology Engineer/Researcher
DSA Research Group: http://dsa-research.org
Globus GridWay Metascheduler: http://www.GridWay.org
OpenNebula Virtual Infrastructure Engine: http://www.OpenNebula.org

More information about the Users mailing list