Hi Wei,
Yes, the Unix socket interface works okay. Here’s a relevant part of the script
changed to use the socket:
import socket
sock = socket.socket(socket.AF_UNIX, socket.SOCK_STREAM)
sock.connect("/var/run/xenstored/socket")
fd = os.dup(sock.fileno())
try:
(CC'ing Linux maintainers)
OK. Thanks for all the information.
This seems to be a bug in Linux xenbus driver.
Relevant code snippet in
drivers/xen/xenbus/xenbus_dev_frontend.c:xenbus_write_watch()
/* Success. Synthesize a reply to say all is OK. */
{
struct {
On Fri, Feb 26, 2016 at 11:26:50AM +, Wei Liu wrote:
> Hello
>
> On Thu, Feb 25, 2016 at 03:54:14PM +0300, Sergei Lebedev wrote:
> > Hello list,
> >
> > I’m working on a Python client library for XenStore [1]. The library
> > implements two ways to access XenStore: via Unix socket and via
Hello
On Thu, Feb 25, 2016 at 03:54:14PM +0300, Sergei Lebedev wrote:
> Hello list,
>
> I’m working on a Python client library for XenStore [1]. The library
> implements two ways to access XenStore: via Unix socket and via /dev.
> The /dev interface turned out to be a bit problematic, because it
Hello list,
I’m working on a Python client library for XenStore [1]. The library implements
two ways to access XenStore: via Unix socket and via /dev. The /dev interface
turned out to be a bit problematic, because it ignores the req_id field for
WATCH requests.
The spec [2] requires all
