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/
Home Products Support Community News


Re: [Xen-devel] [PATCH 0 of 6] dm-userspace xen integration

To: Christian.Limpach@xxxxxxxxxxxx
Subject: Re: [Xen-devel] [PATCH 0 of 6] dm-userspace xen integration
From: Dan Smith <danms@xxxxxxxxxx>
Date: Tue, 22 Aug 2006 06:40:25 -0700
Cc: Dan Smith <danms@xxxxxxxxxx>, Ryan Grimm <grimm@xxxxxxxxxx>, Xen Devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 22 Aug 2006 06:41:37 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <3d8eece20608220203n51498659hdf973368460a0cd2@xxxxxxxxxxxxxx> (Christian Limpach's message of "Tue, 22 Aug 2006 10:03:40 +0100")
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: <20060821205451.GA10771@xxxxxxxxxxxxxxxxxxxxx> <3d8eece20608220203n51498659hdf973368460a0cd2@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.4 (gnu/linux)
CL> Has this been posted to the devicemapper list?  I think someone
CL> mentioned it had been, could you post a reference to any follow-up
CL> discussion?  

It has been posted to dm-devel, and through a few on-list and (mostly)
off-list mails, the maintainer has expressed interest in getting this
pushed into device-mapper proper soon.

CL> Is there clear indication that this will be picked up by
CL> devicemapper because 

Yes.  An older version is already in his staging tree, and the latest
version has been sent to him.

CL> I don't think we'll want to have to maintain this in-tree forever.

I strongly agree.

CL> This needs to be changed to fail gracefully if the auto* tools are
CL> not installed.  Is the use of auto* tools absolutely necessary?

Since xm-test was accepted with the use of autotools, we did not see
any reason why this wouldn't.

CL> Could we checkin the generated files as well?

I suppose, if that's what you want.  It will result in some relatively
large patches of apparent garbage every time we make a change to the
build system.

CL> Is this there because libdevmapper doesn't support this yet?  Is
CL> there any version of libdevmapper which supports this yet?

The libdevmapper changes are also being pushed to the device-mapper
maintainer.  For now, we are just compiling those directly into cowd
to avoid forcing people to patch their libdevmapper.

CL> Does this work for qemu domains?  If so how, if not, what are your
CL> plans to make it work for qemu domains?

I don't see why it would not work.  It just exports a block device, so
if a qemu domain can use an LVM or a partition, then this will work.
I can get access to an HVM machine and verify.

Dan Smith
IBM Linux Technology Center
Open Hypervisor Team
email: danms@xxxxxxxxxx

Attachment: pgpimwM71zyye.pgp
Description: PGP signature

Xen-devel mailing list