[Fedora-xen] A different problem with the new xen 3.0.2 package

[Ben]

After upgrading to the new kernel and xen userspace packages, I'm  
seeing this in my xend.log when I try to start it:

[2006-10-21 09:37:24 xend 2674] INFO (SrvDaemon:283) Xend Daemon started
[2006-10-21 09:37:24 xend 2674] INFO (SrvDaemon:287) Xend changeset:  
unavailable .
[2006-10-21 09:37:24 xend 2674] ERROR (SrvDaemon:297) Exception  
starting xend ((111, 'Connection refused'))
Traceback (most recent call last):
   File "/usr/lib64/python2.4/site-packages/xen/xend/server/ 
SrvDaemon.py", line 291, in run
     servers = SrvServer.create()
   File "/usr/lib64/python2.4/site-packages/xen/xend/server/ 
SrvServer.py", line 108, in create
     root.putChild('xend', SrvRoot())
   File "/usr/lib64/python2.4/site-packages/xen/xend/server/ 
SrvRoot.py", line 40, in __init__
     self.get(name)
   File "/usr/lib64/python2.4/site-packages/xen/web/SrvDir.py", line  
82, in get
     val = val.getobj()
   File "/usr/lib64/python2.4/site-packages/xen/web/SrvDir.py", line  
52, in getobj
     self.obj = klassobj()
   File "/usr/lib64/python2.4/site-packages/xen/xend/server/ 
SrvDomainDir.py", line 39, in __init__
     self.xd = XendDomain.instance()
   File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomain.py",  
line 636, in instance
     inst.init()
   File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomain.py",  
line 71, in init
     xstransact.Mkdir(VMROOT)
   File "/usr/lib64/python2.4/site-packages/xen/xend/xenstore/ 
xstransact.py", line 345, in Mkdir
     complete(path, lambda t: t.mkdir(*args))
   File "/usr/lib64/python2.4/site-packages/xen/xend/xenstore/ 
xstransact.py", line 351, in complete
     t = xstransact(path)
   File "/usr/lib64/python2.4/site-packages/xen/xend/xenstore/ 
xstransact.py", line 20, in __init__
     self.transaction = xshandle().transaction_start()
   File "/usr/lib64/python2.4/site-packages/xen/xend/xenstore/ 
xsutil.py", line 18, in xshandle
     xs_handle = xen.lowlevel.xs.xs()
Error: (111, 'Connection refused')


Interestingly (?) my normal xend processes remain running, even if  
xend doesn't seem to be working:

root      2761  0.0  0.0 105000  5908 ?        S    09:45   0:00  
python /usr/sbin/xend start
root      2762  0.5  0.0 115240  6748 ?        Sl   09:45   0:00  
python /usr/sbin/xend start

[root at johnny xen]# uname -a
Linux johnny 2.6.18-1.2200.fc5xen0 #1 SMP Sat Oct 14 17:36:54 EDT  
2006 x86_64 x86_64 x86_64 GNU/Linux
[root at johnny xen]# rpm -q libvirt libvirt-devel xen
libvirt-0.1.7-2.FC5
libvirt-devel-0.1.7-2.FC5
xen-3.0.2-5.fc5