From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: save/restore image format Date: Tue, 26 Sep 2006 13:20:47 -0500 Message-ID: <45196F7F.9090607@us.ibm.com> References: <0E6FE5D295DE5B4B8D9070C26A227987056884@pdsmsx411.ccr.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <0E6FE5D295DE5B4B8D9070C26A227987056884@pdsmsx411.ccr.corp.intel.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "Dong, Eddie" Cc: Ian Pratt , xen-devel@lists.xensource.com, "Zhai, Edwin" , John Levon List-Id: xen-devel@lists.xenproject.org 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 > >