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-devel

RE: [Xen-devel] [PATCH] make qemu handle drbd properly

To: James Harper <james.harper@xxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] [PATCH] make qemu handle drbd properly
From: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
Date: Tue, 30 Aug 2011 15:37:48 +0100
Cc: "rshriram@xxxxxxxxx" <rshriram@xxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>, Stefano Stabellini <Stefano.Stabellini@xxxxxxxxxxxxx>
Delivery-date: Tue, 30 Aug 2011 07:30:36 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <AEC6C66638C05B468B556EA548C1A77D01E5DA18@trantor>
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: <AEC6C66638C05B468B556EA548C1A77D01BB92B8@trantor> <BANLkTind3O2QvpLE4VN08SBBOMvdZe7QwA@xxxxxxxxxxxxxx> <19977.52972.272583.269113@xxxxxxxxxxxxxxxxxxxxxxxx> <CAP8mzPNFWXMbVU1FxFncXB6q390L2WaBNcoVKuikzMFbdOnTKA@xxxxxxxxxxxxxx> <AEC6C66638C05B468B556EA548C1A77D01E5D9E9@trantor> <alpine.DEB.2.00.1108301130280.12963@kaball-desktop> <AEC6C66638C05B468B556EA548C1A77D01E5DA18@trantor>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Alpine 2.00 (DEB 1167 2008-08-23)
On Tue, 30 Aug 2011, James Harper wrote:
> > I don't think qemu needs any knowledge of the backend type: the
> > toolstack (block scripts and/or libxenlight) should just setup a phy
> > backend and pass to qemu the right device name from the start.
> > Regarding the retries, it is probably better to handle them in the
> block
> > scripts, qemu doesn't seem the right place to put them.
> 
> Does xen wait for the block-* scripts to complete before starting qemu?
> When I tested where to put the delay last time it didn't seem to work
> without putting it in qemu-dm.
 
Currently libxenlight does not support block-* script, but it should, it
is one of the missing features.

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

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