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] xenstore documentation

To: harry <harry@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] xenstore documentation
From: Jacob Gorm Hansen <jacobg@xxxxxxx>
Date: Tue, 4 Oct 2005 14:56:11 +0200
Delivery-date: Tue, 04 Oct 2005 12:54:02 +0000
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=hQggPKY7BZwBw3fBci81LsT5/FK59WV56wMlJCNFv6TiqVIQEqZKc5xDyc1V7U5cGcAfE+u+UHwoZfI8RIKF6vfAz3cLhBbRJPMfmh/w3KzfASJHzfqqIjnolLJBMRZNHXJKRMB4DaVpewVCp75z8FgJW8imxqlwkegQSsxGxgs=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1128430090.30221.16.camel@xxxxxxxxxxxxxxxxxxxxx>
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: <e08041f30510031003p6c4911b8n22dbf10bd1a1997f@xxxxxxxxxxxxxx> <ae5426fb0510032327r4589aaerc4d279825dca0ad8@xxxxxxxxxxxxxx> <e08041f30510040520g53e96456xa7d93168fa8cdf90@xxxxxxxxxxxxxx> <1128429737.30221.12.camel@xxxxxxxxxxxxxxxxxxxxx> <1128430090.30221.16.camel@xxxxxxxxxxxxxxxxxxxxx>
Reply-to: Jacob Gorm Hansen <jacobg@xxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
(longing for the days when all one had to do was poke a few values in /proc/xen)

On 10/4/05, harry <harry@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

> > Looking at the current code, it looks like 
> > domainpath/backend/device_class/frontend_uuid/device_id/transaction_stuff_here
> > for the back-end and and
> > domainpath/device_id/transaction_stuff_here
> > for the front-end.

Hmm why does the backend need to deal with the uuid, I thought that
was solely for the tools? So to recap, I have to:

- introduce dom0 to xenstore, with prefix=/local/domain/0
- mkdir /local/domain/0/backend
- mkdir /local/domain/0/device

And that will trigger the blkback-probe? Sorry if I am sounding
confused, but I am fairly confident this stuff is more complex than it
needs to be.

Thanks,
Jacob

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