Xen devel - Oct 2005 - Xenbus problems solved (soft of)

hi,

I discovered that if I do not call xs_interface_close() in my tools
(especially the one calling xs_init() and introducing dom0), all
following xenbus transactions fail silently. They are logged as (T) in
the trace-file, but have no effect on what is actually in the store. I
suppose this is a bug in xenstored.

Also, with the evtchn fix from Stephan Berger I am now able to
successfully connect  a physical block device to my domU :-)

Another thing that I discovered is that the use of xenstore for error
messages is problematic. The backend will typically have a watch on
the node it is logging the error message to, causing infinite watch
trigger -> log error -> watch trigger loops.
The use of the store for error should probably be reconsidered.

Jacob

--
Save time and bandwidth with EDelta: http://www.diku.dk/~jacobg/edelta/

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

On Thu, Oct 06, 2005 at 12:41:21PM +0200, Jacob Gorm Hansen wrote:
> Another thing that I discovered is that the use of xenstore for error
> messages is problematic. The backend will typically have a watch on
> the node it is logging the error message to, causing infinite watch
> trigger -> log error -> watch trigger loops.
I agree that this is problematic.  I have assigned it bug #286.

Ewan.

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