From: Ewan Mellor <ewan@xensource.com>
To: Patrick O'Rourke <porourke@egenera.com>
Cc: Xen-devel <xen-devel@lists.xensource.com>
Subject: Re: An Introduction to the Xen-API Work
Date: Wed, 8 Nov 2006 18:45:56 +0000 [thread overview]
Message-ID: <20061108184556.GD32530@leeni.uk.xensource.com> (raw)
In-Reply-To: <4552221D.1080705@egenera.com>
On Wed, Nov 08, 2006 at 01:29:49PM -0500, Patrick O'Rourke wrote:
> Ewan Mellor wrote:
>
> > o xm suspend - Save a VM to a location under Xend's management
> > o xm resume - Resume a VM from that same location
>
> Does this preclude running Xen in an environment with no persistent
> storage? For example we now suspend to pipe which actually results in
> the suspend image being stored off the Xen host.
We've not taken xm save and xm restore away, so you can still use them if you
know what you're doing. We're trying to encourage people not to do that,
because of the non-obvious (but very real) risk to their data, but if it's
integrated into a wider protective framework, then that's fine of course.
Would you like an API call that better supported this use-case? In the long
run, might your integration be easier if Xend supported "save to this
address/port" or something like that?
Ewan.
next prev parent reply other threads:[~2006-11-08 18:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-04 15:29 An Introduction to the Xen-API Work Ewan Mellor
2006-11-06 20:44 ` Stefan Berger
2006-11-06 23:46 ` Ewan Mellor
2006-11-07 21:38 ` Stefan Berger
2006-11-08 15:02 ` Stefan Berger
2006-11-08 17:34 ` Jim Fehlig
2006-11-08 18:25 ` Ewan Mellor
2006-11-08 19:15 ` Stefan Berger
2006-11-08 18:29 ` Patrick O'Rourke
2006-11-08 18:45 ` Ewan Mellor [this message]
2006-11-08 19:22 ` Patrick O'Rourke
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=20061108184556.GD32530@leeni.uk.xensource.com \
--to=ewan@xensource.com \
--cc=porourke@egenera.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.