Re: errors trying to start xend with new 3.3 kernel

[Manuel Bouyer <bouyer%antioche.eu.org@localhost>]

On Fri, Aug 29, 2008 at 06:39:45PM -0700, Michael Litchard wrote:
> I get these errors when trying to start xend.
> 
> # /usr/pkg/share/examples/rc.d/xend start
> Starting xend.
> Traceback (most recent call last):
>   File "/usr/pkg/sbin/xend", line 42, in ?
>     from xen.xend.server import SrvDaemon
>   File "usr/pkg/lib/python2.4/site-packages/xen/xend/server/SrvDaemon.py", 
> line
> 26, in ?
>   File "usr/pkg/lib/python2.4/site-packages/xen/xend/server/relocate.py", 
> line 2
> 6, in ?
>   File "usr/pkg/lib/python2.4/site-packages/xen/xend/XendDomain.py", line 35, 
> in
>  ?
>   File "usr/pkg/lib/python2.4/site-packages/xen/xend/XendCheckpoint.py", line 
> 22
> , in ?
>   File "usr/pkg/lib/python2.4/site-packages/xen/xend/XendConfig.py", line 28, 
> in
>  ?
>   File "usr/pkg/lib/python2.4/site-packages/xen/xend/XendDevices.py", line 
> 22, i
> n ?
>   File "usr/pkg/lib/python2.4/site-packages/xen/xend/server/netif.py", line 
> 30,
> in ?
>   File "usr/pkg/lib/python2.4/site-packages/xen/xend/XendXSPolicyAdmin.py", 
> line
>  26, in ?
>   File "usr/pkg/lib/python2.4/site-packages/xen/util/xsm/acm/acm.py", line 
> 39, i
> n ?
> AttributeError: XendOptionsFile instance has no attribute 
> 'get_xend_security_pat
> h'
> 
> 
> It looks like the python scripts did not get updated when I updated
> the kernel and tools
> # ls -l /usr/pkg/lib/python2.4/site-packages/xen/xend/server/SrvDaemon.py
> -rw-r--r--  1 root  wheel  12275 Aug 22 02:49
> /usr/pkg/lib/python2.4/site-packages/xen/xend/server/SrvDaemon.py
> # date
> Thu Aug 28 23:20:39 PDT 2008
> 
> And I think there may be a conflict in pkgsrc
> 
> xentools3-3.1.4     Userland Tools for Xen
> xenkernel33-3.3.0   Xen 3.3.0 Kernel
> xenconsole-0.15b1.1nb1 Console monitor for Xen
> xentools33-3.3.0    Userland Tools for Xen 3.3.x
> xentools3-hvm-3.1.4 Tools for Virtual Machine Extensions support in Xen
> 
> So, is there agreement that the python scripts need to be updated? And
> if so, could someone tell me the right way to do this?

remove xentools3*, and reinstall xentools33.
I'm not sure how you could go in this situation, as xentools33 has CONFLICTS
with xentools30-* xentools3-* xentools32-*

-- 
Manuel Bouyer <bouyer%antioche.eu.org@localhost>
     NetBSD: 26 ans d'experience feront toujours la difference
--