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] xl: Special case tap/aio for disk validation

To: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] xl: Special case tap/aio for disk validation
From: Jim Fehlig <jfehlig@xxxxxxxxxx>
Date: Fri, 28 Jan 2011 09:52:07 -0700
Cc: Kamala Narasimhan <kamala.narasimhan@xxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>, "Kamala Narasimhan \(3P\)" <kamala.narasimhan@xxxxxxxxxx>
Delivery-date: Fri, 28 Jan 2011 08:52:41 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <alpine.DEB.2.00.1101281623010.7277@kaball-desktop>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <4D407A06.1050902@xxxxxxxxx> <alpine.DEB.2.00.1101271506410.7277@kaball-desktop> <4D41EE90.5000907@xxxxxxxxx> <4D42E8B9.9060901@xxxxxxxxxx> <alpine.DEB.2.00.1101281623010.7277@kaball-desktop>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird (X11/20081112)
Stefano Stabellini wrote:
> On Fri, 28 Jan 2011, Jim Fehlig wrote:
>> Kamala Narasimhan wrote:
>>>> - phy:/path/to/device
>>>> - file:/path/to/file
>>>> - tap:/path/to/file
>>> Along with phy, file and tap for block device types there appear to be a 
>>> 'drdb' option too.  Do we actively support it?
>> The xend toolstack supports arbitrary external block device types.  We
>> have block-iscsi and block-npiv,  and the drbd project provides
>> block-drbd.  I'm quite sure I've seen other custom block types as well. 
>> Will these arbitrary block device types still be supported in the new
>> toolstack?
> Is it just a matter of forking and executing an external script to
> setup a block device and threat it as phy: afterwards?

Currently, IIUC, the external script is invoked by udev

SUBSYSTEM=="xen-backend", KERNEL=="tap*", RUN+="/etc/xen/scripts/blktap
SUBSYSTEM=="xen-backend", KERNEL=="vbd*", RUN+="/etc/xen/scripts/block

The block script will delegate to a helper if needed, which configures
the block device and writes some info (like resulting dev node) to
xenstore.  xend and/or qemu then read the info and continue configuring
the device from backend perspective.

> It shouldn't be too difficult but still non-trivial at this point of the
> release cycle.
> Maybe users could work around the lack of support in 4.1 calling the
> script themselves and using the name of the block device in the VM
> config file directly?

Yes, this is certainly a workaround.  One could argue this is the proper
solution and remove support for external block scripts.  But this
functionality has been around for years.


Xen-devel mailing list