From: Anthony Liguori <aliguori@us.ibm.com>
To: "Dong, Eddie" <eddie.dong@intel.com>
Cc: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>,
xen-devel@lists.xensource.com, "Zhai,
Edwin" <edwin.zhai@intel.com>,
John Levon <levon@movementarian.org>
Subject: Re: save/restore image format
Date: Tue, 26 Sep 2006 13:20:47 -0500 [thread overview]
Message-ID: <45196F7F.9090607@us.ibm.com> (raw)
In-Reply-To: <0E6FE5D295DE5B4B8D9070C26A227987056884@pdsmsx411.ccr.corp.intel.com>
Dong, Eddie wrote:
> Another curious question for save/restore in my opnion is that should we
> encrypt the saved image or not?
The qcow v2 format has the ability to save memory images (actually,
multiple snapshots). Plus, qcow supports encryption. May be something
to consider.
Regards,
Anthony Liguori
> Given an usage model where people share
> physical computers, say an University Lab, but everybody own an virtual
> machine that is saved on network but can be restore and executed at any
> physical box. In this case, encryption to the image file is a must.
> Even for live migration, probably encryption is a must in future. With
> data file encrypted, probably the existing tools like objdump can no
> longer work the save image file even we use ELF.
>
>
> thx,eddie
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
>
next prev parent reply other threads:[~2006-09-26 18:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-26 14:50 save/restore image format Dong, Eddie
2006-09-26 15:22 ` John Levon
2006-09-26 18:20 ` Anthony Liguori [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-09-26 4:54 Nakajima, Jun
2006-09-26 3:17 Zhai, Edwin
2006-09-26 11:37 ` John Levon
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=45196F7F.9090607@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=eddie.dong@intel.com \
--cc=edwin.zhai@intel.com \
--cc=levon@movementarian.org \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--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.