Re: [Xen-users] xm save -c

["Nick Couchman" <Nick.Couchman@xxxxxxxxx>]

Mike,
I'd also be interested in those patches and that code - something like an "xm checkpoint" would be great, which sounds like what you're suggesting or going for in your code there.

Thanks,
Nick


-----Original Message-----
From: Mike Sun <msun@xxxxxxxxxx>
To: Fabian Flägel <fabigant@xxxxxxxxxxxxxx>
Cc: Nick Couchman <Nick.Couchman@xxxxxxxxx>, XEN Mailing List <xen-users@xxxxxxxxxxxxxxxxxxx>, xen-research@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] xm save -c
Date: Fri, 14 Nov 2008 12:22:38 -0500

Hi Fabian,

We're still working to finish the paper first, but I'll certainly
cleanup and provide the prototype code after we're done.

Thanks,
Mike

On Fri, Nov 14, 2008 at 4:42 AM, Fabian Flägel <fabigant@xxxxxxxxxxxxxx> wrote:
> Hi Mike,
>
> i'd like to see your code. :)
>
> Regards
> Fabian
>
> 2008/11/14 Mike Sun <msun@xxxxxxxxxx>
>>
>> Hi Nick,
>>
>> > I was wondering if anyone knows of a way to "checkpoint" without pausing
>> > the
>> > domain?  I can't do something like an hourly checkpoint if the domain
>> > pauses
>> > every hour - the users on the domUs would kill me.  Is "seamless
>> > checkpointing" something that's being developed, something that can be
>> > done
>> > another way, or something I should just give up on now?
>>
>> I've been working on something for my research that probably addresses
>> what you're looking for: low latency/downtime checkpointing.  There
>> are two ways I know this can be done.
>>
>> You can modify the live-migration mechanism in Xen to save a
>> checkpoint instead of migrating to another host.  I don't know why
>> this hasn't been provided in the xm save tool, but it's a pretty
>> simple hack to get working since the xm migrate and xm save codebase
>> is basically the same.  If you're interested, I can send patches to
>> allow you to do that.  Then basically on a checkpoint, pre-copying
>> would be used to cut the actual time the domU has to be paused.
>>
>> The other way that I've implemented for my research project is to use
>> copy-on-write.  I've implemented a prototype and in the middle of
>> writing paper for publication.  It's not suited for production use,
>> but I'd be glad to contribute the code if there's interest.
>>
>> Mike
>>
>> _______________________________________________
>> Xen-users mailing list
>> Xen-users@xxxxxxxxxxxxxxxxxxx
>> http://lists.xensource.com/xen-users
>
>

---

This e-mail may contain confidential and privileged material for the sole use of the intended recipient. If this email is not intended for you, or you are not responsible for the delivery of this message to the intended recipient, please note that this message may contain SEAKR Engineering (SEAKR) Privileged/Proprietary Information. In such a case, you are strictly prohibited from downloading, photocopying, distributing or otherwise using this message, its contents or attachments in any way. If you have received this message in error, please notify us immediately by replying to this e-mail and delete the message from your mailbox. Information contained in this message that does not relate to the business of SEAKR is neither endorsed by nor attributable to SEAKR.

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