[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] Cloning VM's


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: "Molle Bestefich" <molle.bestefich@xxxxxxxxx>
  • Date: Wed, 14 Jun 2006 16:05:24 +0200
  • Delivery-date: Wed, 14 Jun 2006 07:06:01 -0700
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=qPPwWKF2oo16KExzSLrxvFLqjoKRbrpC3qSpTVkbVTMBG4c5IL3sDzXg8Hrrlei1g5YmhX9IyLy7N2kehUsYLbneyFWnfomNGNKVEN337KncnrUZFBMoVdiv43Gl+xjRJ15W7ft4Q6EjADWoCLBLPHm4AuoJ7ncJpq+qMFXjMIQ=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Emiliano Gabrielli (aka AlberT) wrote:
> We're using unionfs to share a basic VM on the file level on top of
> which is added an empty filesystem for each VM to contain it's
> changes.

it's an idea i'm looking to since time...
can you explain in depth the architecture you used ??

Sure.
(I don't know exactly what you need to know, but I'll try.)

To make the domUs boot and shutdown correctly, I modified the init /
shutdown scripts somewhat to be able to cope with two root
filesystems:
The domU which has only the base filesystem needs to mount that
read/write, so we can install updated software, perform fsck, etc.
All the other domUs needs to mount their "changes" filesystem
read/write, perform fsck on it at startup, etc. but mount the "base"
filesystem read-only.

That's about it, I think?

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.