xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
* Cloning a VM and copy-on-write deduplicating memory using CoW page sharing in Xen 4+
@ 2012-02-02 19:14 Patrick Wilbur
  2012-02-02 19:23 ` Andres Lagar-Cavilla
  0 siblings, 1 reply; 2+ messages in thread
From: Patrick Wilbur @ 2012-02-02 19:14 UTC (permalink / raw)
  To: xen-devel; +Cc: andres


[-- 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

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Cloning a VM and copy-on-write deduplicating memory using CoW page sharing in Xen 4+
  2012-02-02 19:14 Cloning a VM and copy-on-write deduplicating memory using CoW page sharing in Xen 4+ Patrick Wilbur
@ 2012-02-02 19:23 ` Andres Lagar-Cavilla
  0 siblings, 0 replies; 2+ messages in thread
From: Andres Lagar-Cavilla @ 2012-02-02 19:23 UTC (permalink / raw)
  To: Patrick Wilbur; +Cc: xen-devel

> 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!

Patrick,
that is indeed painful and wasteful. That is why we added
xc_memshr_add_to_physmap. Now you can do Potemkin-/SnowFlock-like cloning
in a few lines of code. You still want the source VM to be paused,
obviously.

Yuengling is my favourite US beer ;)

Andres

>
> 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
>

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2012-02-02 19:23 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-02-02 19:14 Cloning a VM and copy-on-write deduplicating memory using CoW page sharing in Xen 4+ Patrick Wilbur
2012-02-02 19:23 ` Andres Lagar-Cavilla

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).