[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] xenstore xenbus failure


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: Adam Wendt <thelsdj@xxxxxxxxx>
  • Date: Tue, 20 Jan 2009 11:12:02 -0800
  • Delivery-date: Tue, 20 Jan 2009 11:12:27 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=Tb2BUhId0LDNMFcOjJZxMAFK8GUCeX+FixrOYwkALulkgWfrUaALf3BkUJsxbvsxQi 0cpIZPTcWjqi6EJVKspowZ/NeZlWNlDMhj+CYCgzVnbqAtZn2AGj9xG/2EmsvY+Ivk8H 4zG32M5+gT2/Fyo2fBmHFVZm3Zvr++UK26HNM=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Hi,

Still having problems getting xenstore working without the socket interface. Here is output running simple xenstore-ls:

Got message DIRECTORY len 2 from 0x1451b80
Writing msg DIRECTORY (tool) out to 0x1451b80
xenstore-ls: xs_directory (/): Invalid argument
IN 0x1451b80 20090120 10:43:23 DIRECTORY (/ )
OUT 0x1451b80 20090120 10:43:23 DIRECTORY (tool vm local )

First 2 lines are verbose output of xenstored, middle line is output of the xenstore client and last 2 lines are trace log from xenstored.

'Invalid argument' seems to be coming from the write() call on line 98 of xs_lib.c.

Seems to happen the _second_ time that xs_write_all is called from xs_talkv (writing the parameters) in this case the "/" for the ls.

From the output above we can see that xenstored is receiving the write, and even the "/" parameter, so why would the write be failing with 'Invalid argument'?

Thanks,

Adam
Adam Wendt Consulting

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

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.