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] xend "invalid token" error

To: Anthony Liguori <aliguori@xxxxxxxxxx>
Subject: Re: [Xen-devel] xend "invalid token" error
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Mon, 10 Oct 2005 22:11:44 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Jon Mason <jdmason@xxxxxxxxxx>
Delivery-date: Mon, 10 Oct 2005 21:17:07 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <434AD7FB.2020504@xxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20051010205020.GA10245@xxxxxxxxxx> <434AD7FB.2020504@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
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?

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