All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Prateek Sharma <prateeks@cs.umass.edu>, xen-devel@lists.xen.org
Cc: Andres Lagar-Cavilla <andres@lagarcavilla.org>
Subject: Re: Question on Lazy VM Restore
Date: Sat, 14 Dec 2013 16:28:29 +0000	[thread overview]
Message-ID: <52AC872D.3080702@citrix.com> (raw)
In-Reply-To: <alpine.LRH.2.03.1312131103160.1504@loki.cs.umass.edu>

On 13/12/2013 16:06, Prateek Sharma wrote:
> Hello all,
>     I was wondering if there is an existing mechanism in Xen for
> restoring a saved/checkpointed VM lazily. By that, I mean that the
> pages of the VM should be mapped only on access.
>     Currently, restoring a VM from a snapshot seems to take a long
> time [~20 seconds for 2 GB].
>     Assuming that there is no lazy-restore functionality, what would
> be a good way to implement this? Using parts of Xen-paging? Snowflock?
> Something else?
>
> Thanks!
> --Prateek

There is no current mechanism which I am aware of.  I recall a few
academic papers looking in to the possibility, but no code as a result.

The restoring from a shapshot has a number of large inefficiencies in
the datapath in the privcmd driver.  Fixing these would make quite an
improvement on those 20 seconds, which I suspect might be a rather
easier improvement than implementing lazy restore.

Having said that, if you are looking for a project to do, I suspect the
xen-paging infrastructure would be able to be used for lazy restore,
although Andres (author of xen-paging, CC'd) will likely be able to
speak rather more about the feasibility of it.

~Andrew

  reply	other threads:[~2013-12-14 16:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-13 16:06 Question on Lazy VM Restore Prateek Sharma
2013-12-14 16:28 ` Andrew Cooper [this message]
2013-12-18 16:53   ` Andres Lagar Cavilla

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=52AC872D.3080702@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=andres@lagarcavilla.org \
    --cc=prateeks@cs.umass.edu \
    --cc=xen-devel@lists.xen.org \
    /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.