WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

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

To: "Daniel P. Berrange" <berrange@xxxxxxxxxx>
Subject: Re: [Xen-devel] Re: Writing a tool for Shared Persistent Windows Boot Image
From: "Jim Burnes" <jvburnes@xxxxxxxxx>
Date: Thu, 28 Jun 2007 13:15:08 -0600
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, xen-users@xxxxxxxxxxxxxxxxxxx, Anthony Liguori <anthony@xxxxxxxxxxxxx>
Delivery-date: Thu, 28 Jun 2007 12:13:05 -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=DWPkhCKaxdD2lxdYFU4vINn392FBfBWZa/3xyYpeULP762VIXRM2Mn/tS5Wvi2fn/n3YpieHqbe1vt7d5wlDBEHssTRXeN1ee8+DdhF2kLMXr2u/ViyrkclxM96DmnSTPUEu44IDVAAOS2EVm6baHpFWTbC+ifmIbfUdpFSQAGk=
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=OVj0un9JEUmZciQXPilOy8bffSfroaG7MNUtyhj3K9PgLSe2vV6yD27rzHV/AeqHqmKDeQOOZsYx3jaGhKnRdLNgtMNLaCn1j9nhWoIzJ9FQSGWU6Frkg4eQPOIRU0P8f7oKeGgzbpGkkN4CE7Asv/p3PoB6GvJfqUugBCw1+eU=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20070628182736.GB12711@xxxxxxxxxx>
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> <467ABF50.50209@xxxxxxxxxxxxx> <13A934B9-F615-4838-8D26-4E33F0BCFF2E@xxxxxxxxx> <467AE21F.1020700@xxxxxxxxxxxxx> <37B43CC2-BED7-4336-9CC4-0CE1C7894458@xxxxxxxxx> <467AF0C6.5010101@xxxxxxxxxxxxx> <b3ec41ba0706281118k751e90bajf2f3095fd92d0939@xxxxxxxxxxxxxx> <20070628182736.GB12711@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Dan,

Since blktap looks broken on HVM for the forseeable future (a real shame if you ask me), what's the next best thing? LVM snapshots?  How can I get LVM snapshots to use use less main memory?  Will it help if I decrease the max size of the copy-on-write snapshot?  Usually our copy-on-write area is no larger than 20MB.

Jim Burnes


On 6/28/07, Daniel P. Berrange <berrange@xxxxxxxxxx> wrote:
On Thu, Jun 28, 2007 at 12:18:47PM -0600, Jim Burnes wrote:
> Anthony (and anyone else listening),
>
> I've installed Centos 5, Xen 3.1 (from the Xensource RPMs) and installed a
> base Windows image to an LVM to test.
>
> The installation wen't fairly well and I resolved various issues like
> getting the VMs to render to VNC displays properly.
>
> I even used LVM snapshotting to do some quick copy-on-write tests.  In that
> configuration I've had up to 7 Windows VMs running at the same time, on
> separate IPs, writing to LVM copy-on-write snapshots.  The only problem is
> that LVM cow snapshots consume too much main memory.
>
> So I proceeded to my final test which was to replace the LVM storage with
> QCOW storage and see how many Windows VMs I could run concurrently.  (I'm
> trying for 12).
>
> The only cow tool I had was qcow-create, so I downloaded the qemu RPMs and
> installed them.
>
> I used img2qcow to convert my installed Windows LVM image to the qcow base
> image.
> I used qcow-img to create a copy-on-write snapshot of the base image.
> I tried to boot with this as the new storage type by specifiying:
>
> disk = [ 'tap:qcow:/var/lib/xen/image/winflp.img,hda1,w',
> 'file:/var/lib/xen/install/winflp.iso,hdc:cdrom,r']
>
> (and other variations, by using 'hda' instead of 'hda1', using 'tap:aio'
> instead of 'tap:qcow')
>
> But everytime I try to start the vm by 'xm create' it seems to create the VM
> and the VM immediately exits, leaving hardly any trace of even booting.  I
> tried booting directly to hard drive C: and I tried booting to the CDROM.
> Booting to the CDROM worked fine but reported no attached hard drive.
>
> The only thing I see is a trace in the xend.log file which indicates that
> xend (or the VM) is attempting to generate some sort of hotplug event for
> tap.  Then the whole VM shuts down.
>
> Is there something I need to do before tap:qcow works?
>
> I suspect, but am having a hard time proving that either:
>
> (1) My version of Xen 3.1 doesn't support tap:qcow or

It is not possible to use  blktap with HVM guests - there was code which tried
to make it work, but its utterly broken[1]. In my spare time I'm trying to fix
it, but no ETA.

Dan.
[1] it is calling APIS in XenD which no longer exist & has a try..except
    block which silently catches & ignores the errors, so you never notice
    that it failed.
--
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/               -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=|

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