Adding to that "stop" does not mean kill-the-vm. It will susped a VM and save its state/image in the frontend so it can be resumed in any other host. That's why it retrieves the image back to the frontend.
On Tue, Oct 26, 2010 at 2:29 PM, Tino Vazquez <[email protected]> wrote: > Dear Olivier, > > When using the Image Catalog, and not the old method of specifying the > full image path in the source attribute, the values of disk attributes > "save" and "clone" are overridden by the Image Catalog inferring them > from the image properties (persistency, save_as). > > If you want to save the image when using the Image Catalog, either > make it persistent or, if you want to save it as another image, use > the save_as functionality. > > Best regards, > > -Tino > > -- > Constantino Vázquez Blanco | dsa-research.org/tinova > Virtualization Technology Engineer / Researcher > OpenNebula Toolkit | opennebula.org > > > > On Tue, Oct 26, 2010 at 1:23 PM, Olivier Sallou <[email protected]> > wrote: >> Hi, >> I have a template with: >> DISK = [ >> image = "sampleraw2", >> save = "no" >> ] >> >> and when I do "onevm stop", one still tries to save the vm on the frontend. >> (I also tried with save=no instead of save="no"). >> >> Should I create a bug for this or is there something wrong in my template? >> >> Thanks >> >> Olivier >> _______________________________________________ >> Users mailing list >> [email protected] >> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org >> > _______________________________________________ > Users mailing list > [email protected] > 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 _______________________________________________ Users mailing list [email protected] http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
