This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] save/restore image format

On Tue, Sep 26, 2006 at 10:50:28PM +0800, Dong, Eddie wrote:

> > I still believe we should use more or less the same format for core
> > files too; in that respect we need a header field for the /type/ of
> > image. This could also identify HVM images, etc.
> Using ELF like format or not is defintely an arguable topics, but it is
> not addressed in this doc yet. If we want to move to ELF, the whole
> format will be changed both for para VM and HVM, but hopefully through
> this discussion we can first identify the items we need to put in the
> image file.


> Another curious question for save/restore in my opnion is that should we
> encrypt the saved image or not? 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.

I'm not sure I understand. Machine migration will happen over a secure
transport as part of the Xen API changes, or so the plan is. Local dom0
save files can surely be managed via permissions.


Xen-devel mailing list