Xen 
 
Home About Xen.org Xen Xen Summit Wiki Mailing List Bug Tracker Xen Downloads
 
   
 

xen-devel

Re: [Xen-devel] Writing a tool for Shared Persistent Windows Boot Image

To: "Alan Cox" <alan@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Writing a tool for Shared Persistent Windows Boot Image
From: "Jim Burnes" <jvburnes@xxxxxxxxx>
Date: Thu, 28 Jun 2007 11:40:27 -0600
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 28 Jun 2007 10:38:23 -0700
Dkim-signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=Ibj22j/eDYGnUwsYRBkkrjuGObW5GfpQFKnNwh3+VWhkhEXYcDQ2JENtCkRnQkFGaUz6Mpj1R8YN0COzd2/VhK0KoFi4QTSeh4l7VLXQ3/CiDuvx7rx06+1itu2eWilsE23FJQkLhKCXm5Omn6dIQUQsp7K3pmgP9mxlqgnCTbU=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=LOvFqKo5mnh8X/aLciA6vHWjtxxQhNtaqJz/wiB1w3aRD09AWuZuVepPzECb/mZt7jt4mbvunX3NAmnAAqVqyO7zfdwKwVKB91aq8mJIbh4JaRRk/eGf3DnoIzovyxNKFyun66mKrBB5LfZ6MYmyGDpU3BZeNq6zSmUxxPCHs4g=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20070621230331.575e3129@xxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <2BB087BE-D323-4D8E-82F7-794C76ED2BCD@xxxxxxxxx> <20070621230331.575e3129@xxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Alan, thanks for your comment.   Sorry the reply too so long.   I believe that primitive support for dom0 is available.

So far I've been able to implement persistent copy-on-write snapshots with LVM snapshotting, however that method seems to consume way to too much main memory.  We're limited to about 7 VMs of 256M of memory each.  I'm trying to fit about 12 VMs on our 4 GB test box.

To achieve that we'll probably have to move over to qcow copy-on-write files.  They seem to be the ideal way to implement our solution, however I've had the devil's own time getting them to work.  I created the required qcow image files and updated my configuration, but 'xm create <vmname>' just runs and the VM immediately quits with no debugging information.

I'm wondering whether (1) I've screwed up the qcow images or (2) I'm using a set of RPMs that don't support tap:qcow (using 3.1 RPMS from XenSource) or (3) The default RHEL 5 Xen kernel doesn't include TAP support.

Jim Burnes
Boulder, CO


I'd like to use qcow files, since they seem to do

On 6/21/07, Alan Cox < alan@xxxxxxxxxxxxxxxxxxx> wrote:
> Is this supported natively in Xen?  What does everyone else who needs
> to run a lot of Windows VMs do?  There must be a way to support
> shared images.

The Linux dom0 kernel has some snapshotting support which seems to be
what you are asking for ?


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