Keir Fraser wrote:

Hmmm... not quite sure how my changes could have screwed that up, esp. just on 64-bit. Do your changes to allow watches to return varargs definitely work with x86/64?

Yes, Jon verified that this afternoon :-)
To clarify, I'm on x86_32 so it's on both platforms.
Regards,
Anthony Liguori

 -- Keir
On 10 Oct 2005, at 22:07, Anthony Liguori wrote:

I'm seeing this problem too.
Regards,
Anthony Liguori
Jon Mason wrote:

I am geting the following error when I start xend on x86 and amd64
# /etc/init.d/xend start
invalid token
Exception in thread Watcher:Traceback (most recent call last):
 File "/usr/lib/python2.3/threading.py", line 442, in __bootstrap
 self.run()
 File "/usr/lib/python2.3/threading.py", line 422, in run
 self.__target(*self.__args, **self.__kwargs)

File "/usr/lib/python/xen/xend/xenstore/xswatch.py", line 43, in watchMain

 we = cls.xs.read_watch()
RuntimeError: invalid token

I traced the problem back to the "Make libxenstore thread-safe. It also

spawns an internal" patch

(http://lists.xensource.com/archives/html/xen-changelog/2005-10/ msg00118.html). Not a big issue, as xend will start without problems the second time the

command is executed.
Thanks,
Jon
_______________________________________________
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

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