From: Daniel Veillard <veillard@redhat.com>
To: Steven Hand <Steven.Hand@cl.cam.ac.uk>
Cc: Noam Taich <noam.taich@qumranet.com>, xen-devel@lists.xensource.com
Subject: Re: Domain save/migrate issue
Date: Tue, 14 Feb 2006 09:57:05 -0500 [thread overview]
Message-ID: <20060214145705.GF9506@redhat.com> (raw)
In-Reply-To: <E1F91Pt-0000lP-00@mta1.cl.cam.ac.uk>
On Tue, Feb 14, 2006 at 02:44:29PM +0000, Steven Hand wrote:
>
> > On Tue, Feb 14, 2006 at 06:08:06AM -0800, Noam Taich wrote:
> > it would not be atomic anymore). Is there any strong reason a saved domain
> > must not be left running ?
>
> Unless you also have some way to simulataneously snapshot the file
> system, it is not safe to allow the guest to continue and then later
> resume the checkpointed version.
The problem already exists if you resume twice a guest from an image.
Restraining the API doesn't fix the problem, it just limits the probability
of hitting it by mistake. I'm not sure there is any way we can garantee
100% safe operations in all case, most FSes don't have snapshotting
capabilities anyway.
Daniel
--
Daniel Veillard | Red Hat http://redhat.com/
veillard@redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/
next prev parent reply other threads:[~2006-02-14 14:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-14 14:08 Domain save/migrate issue Noam Taich
2006-02-14 14:41 ` Daniel Veillard
2006-02-14 14:44 ` Steven Hand
2006-02-14 14:55 ` Anthony Liguori
2006-02-14 14:57 ` Daniel Veillard [this message]
2006-02-15 11:28 ` Jacob Gorm Hansen
-- strict thread matches above, loose matches on Subject: below --
2006-02-15 16:42 Noam Taich
2006-02-15 16:22 Noam Taich
2006-02-15 16:26 ` Anthony Liguori
2006-02-15 9:32 Noam Taich
2006-02-15 8:38 Noam Taich
2006-02-15 14:16 ` Anthony Liguori
2006-02-14 13:45 Noam Taich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060214145705.GF9506@redhat.com \
--to=veillard@redhat.com \
--cc=Steven.Hand@cl.cam.ac.uk \
--cc=noam.taich@qumranet.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.