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


[Xen-devel] Stubdom and blktap

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Stubdom and blktap
From: "Yang, Xiaowei" <xiaowei.yang@xxxxxxxxx>
Date: Sun, 28 Sep 2008 15:40:57 +0800
Delivery-date: Sun, 28 Sep 2008 00:41:36 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird (X11/20080724)
Recently we had a try of stubdom, whose general status is good.

One issue we found is with aio/sync blktap as backend, disk performance is obviously slower, and there are some IDE kernel error messages (like irq timeout) at boot time.

Another issue (not stubdom specific) comes from blktap's support for QCOW image which is based on a backing file. We never tried this configure before. The root cause is that in tdqcow_get_parent_id(), the backing file is hard-coded to be QCOW type and tdqcow_validate_parent() also presumes it, though the backing file is a raw image normally. With the image type set correctly and a good method for image validation, QCOW works.


Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>