From: Patrick Wilbur <patrick.wilbur@gmail.com>
To: xen-devel@lists.xensource.com
Cc: andres@lagarcavilla.org
Subject: Cloning a VM and copy-on-write deduplicating memory using CoW page sharing in Xen 4+
Date: Thu, 2 Feb 2012 14:14:27 -0500 [thread overview]
Message-ID: <CABFkyn9EYfq7T0cmDDGyUQkpCce7_unLkzOrgDFDDhJHQhtTzw@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1067 bytes --]
Hey all,
Hey Andres,
I'm looking to clone a VM into several extremely-similar VMs, and I'm
hoping to also make use of your lovely new CoW page sharing capabilities in
Xen 4.
>From my understanding of a previous thread where Andres described the
process of sharing/coalescing memory between VMs, it sounds like I will
need to "manually" coalesce each page using a homebrew tool of mine. The
issue I have with doing this is it seems like I'd need to pause, save mem,
load mem in a new VM, coalesce, and resume two VMs, which seems painful and
wasteful of a process for cloning!
Is there an easier way to do this, or should we add a new feature for CoW
cloning of VMs in Xen via a userspace tool?
Thanks,
Pat Wilbur & team
--
Patrick F. Wilbur
Researcher, Consultant, Educator,
Computer Science Graduate at Clarkson University
DONE RIGHT THE FIRST TIME: Consulting and hiring information:
http://pdub.net/consulting/ & http://pdub.net/hiring/
patrick.wilbur@gmail.com
wilburpf@clarkson.edu
Check out our book: http://runningxen.com
My website: http://pdub.net
[-- Attachment #1.2: Type: text/html, Size: 1692 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next reply other threads:[~2012-02-02 19:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-02 19:14 Patrick Wilbur [this message]
2012-02-02 19:23 ` Cloning a VM and copy-on-write deduplicating memory using CoW page sharing in Xen 4+ 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=CABFkyn9EYfq7T0cmDDGyUQkpCce7_unLkzOrgDFDDhJHQhtTzw@mail.gmail.com \
--to=patrick.wilbur@gmail.com \
--cc=andres@lagarcavilla.org \
--cc=xen-devel@lists.xensource.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).