Hi Cris, Both behaviours are possible, depending on your storage model. With a non-shared storage, you need to successfully shutdown your VM, otherwise changes are not transferred back. In a shared storage scenario, you are using the 'master' image directly (opennebula creates a symlink)
We are trying to identify and document all these infrastructure details to improve the 3.0 documentation; you can read more at [1,2] Regards. [1] http://opennebula.org/documentation:rel3.0:sfs#considerations_limitations [2] http://opennebula.org/documentation:rel3.0:nsfs#considerations_limitations -- Carlos Martín, MSc Project Major Contributor OpenNebula - The Open Source Toolkit for Cloud Computing www.OpenNebula.org <http://www.opennebula.org/> | [email protected] On Wed, Aug 10, 2011 at 11:06 PM, Chris Cullen <[email protected]> wrote: > I'm curious as to when changes to an image are written to disc. A fellow > on irc the other day seemed to think that if your kernel paniced you > would lose any changes since the vm was started, and it would revert > back to that state of reboot. But from reading the docs it doesn't seem > like they would behave any differently than a physical machine in that > regard. I assume he was getting confused with non-persistent images, but > want to ask anyway. > > Chris > _______________________________________________ > 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
