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

On Tue, 2005-10-04 at 14:56 +0200, Jacob Gorm Hansen wrote:
> (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

I doubt that mkdir will work.  I would expect that you would have to go
through xenstored to modify the store.  vm-tools contained a utility to
submit an arbitrary transaction to xenstored.

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

Ouch, don't shoot the messenger.

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


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