WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] Migration and checkpointing

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] Migration and checkpointing
From: Mark Williamson <mark.williamson@xxxxxxxxxxxx>
Date: Thu, 1 May 2008 02:29:42 +0100
Cc: Ian Brown <ianbrn@xxxxxxxxx>
Delivery-date: Thu, 01 May 2008 08:11:17 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <d0383f90804272350q6712e5d9q5c0e0623c9b541ec@xxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <d0383f90804272350q6712e5d9q5c0e0623c9b541ec@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.9.9
The -c option to xm save doesn't handle the checkpointing of storage *at all*.  
As such, you're free to use any form of storage checkpointing you want.  The 
downside is that you have to sort out the storage checkpointing you want ;-p  
As a result I'm not sure that it's actually that usable for now although the 
existence of the functionality is cool and you could certainly set up some 
interesting stuff with it.

When playing with this stuff, do be a bit careful.  It's easy to corrupt disk 
images by messing around with suspend/resume in unexpected ways.  For 
instance, if you checkpoint a domain, let it run for a bit, then destroy the 
running copy and restore the checkpoint.  The resumed domain will try and 
write to the disk, but it'll have a completely different idea of what should 
be on the disk.  This is very likely to result in damage to or loss of the 
filesystem.

Ideally, when you checkpoint the guest you'd also checkpoint the storage.  
Then if you resume the checkpoint of the guest's runtime state, you could 
first copy the backup of the storage into place.  ISTR that if you checkpoint 
a paused domain, it'll do the checkpoint and then repause the domain - at 
this point you'd be able to backup the storage and then unpause.  This would 
allow you to create a complete and consistent backup of a running domain.

Cheers,
Mark

On Monday 28 April 2008, Ian Brown wrote:
> Hello,
>   I have xen-3.1.0-13.fc8 on Fedora Core 8.
> This version supports checkpointing for "xm save" command.
>
> When running :
>
> xm save --help
>
> I get:
> Usage: xm save [-c] <Domain> <CheckpointFile>
>
> Save a domain state to restore later.
>   -c, --checkpoint   Leave domain running after creating snapshot
>
> (Though in "man xm" , --checkpoint does not show).
>
> My question is : when using --checkpoint , should I use some shared
> storage (like iSCSI)?
> Or is it not a must ? can I use LVM ? are there any restrictions on
> which storage is to be used for Xen migration with checkpointing?
> Regards,
> Ian
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users



-- 
Push Me Pull You - Distributed SCM tool (http://www.cl.cam.ac.uk/~maw48/pmpu/)

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>
  • Re: [Xen-users] Migration and checkpointing, Mark Williamson <=