All of lore.kernel.org
 help / color / mirror / Atom feed
From: Harry Butterworth <harry@hebutterworth.freeserve.co.uk>
To: "Andrew D. Ball" <aball@us.ibm.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: current domU lifecycle work ?
Date: Fri, 10 Mar 2006 10:09:48 +0000	[thread overview]
Message-ID: <1141985389.7680.3.camel@localhost.localdomain> (raw)
In-Reply-To: <4410A8B0.3060103@us.ibm.com>

On Thu, 2006-03-09 at 17:14 -0500, Andrew D. Ball wrote:

> (1) register a domU with xend (initializes a configuration
> in xenstore)
> (2) turn on that domU
> (3) turn off that domU (without removing it from xenstore)
> (4) unregister that domU with xend (this is destroying the
> domU).

> Is anyone working on stabilizing this?  Have I overlooked
> anything?

Nested within on and off there is save and restore.  Also, at any time
there is migration.  I guess there should be an option to clone.  Then
you have snapshotting and roll-back.  I expect there is more.

Harry.

  reply	other threads:[~2006-03-10 10:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-09 22:14 current domU lifecycle work ? Andrew D. Ball
2006-03-10 10:09 ` Harry Butterworth [this message]
2006-03-13 17:02 ` Ewan Mellor

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=1141985389.7680.3.camel@localhost.localdomain \
    --to=harry@hebutterworth.freeserve.co.uk \
    --cc=aball@us.ibm.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.