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] [PATCH] Block device bringup using Xenstore

To: Xen Mailing List <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] [PATCH] Block device bringup using Xenstore
From: Rusty Russell <rusty@xxxxxxxxxxxxxxx>
Date: Thu, 07 Jul 2005 18:05:36 +1000
Cc: Mike Wray <mike.wray@xxxxxxxxxx>, Christian Limpach <Christian.Limpach@xxxxxxxxxxxx>
Delivery-date: Thu, 07 Jul 2005 08:05:06 +0000
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/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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
This megapatch updates the xenstore daemon, updates the xenbus code, and
hacks the block devices to use the store rather than control messages
for initialization.

We just got this to bring a block device up; tomorrow we'll be cleaning
it up, getting destroy, suspend and resume working.

You'll need Anthony's experimental store-enabled vm-tools: he's sending
email about it now.

A bad analogy is like a leaky screwdriver -- Richard Braakman

Attachment: diff.bz2
Description: application/bzip

Xen-devel mailing list
<Prev in Thread] Current Thread [Next in Thread>