Scott Davenport wrote:
> Hi,
>         
> Upgraded to snv_98 and xvm/domains is no longer starting. Been
> through the archives and checked all of the things in this
> thread:
> http://www.mail-archive.com/[email protected]/msg02969.html
>   
> I did use an updated BFU; used the one from snv_98. Reset the
> VNC password with svccfg. As for Python, I believe I've got a
> sufficient version with ucred support:

Did you do the following too?
   /ws/onnv-gate/public/bin/update_xvm /ws/onnv-gate/packages/i386/snv_98-nd/



MRJ


> % pkginfo -l SUNWPython SUNWPython-devel |grep VERSION
>    VERSION:  2.4.4,REV=110.0.4.2007.07.23.11.30
>    VERSION:  2.4.4,REV=110.0.4.2007.07.23.11.30
>         
> Alas, xvm/domains is still unhappy. Is the above 2.4 insufficient?
> 
> svc log below.
> 
> Thanks
> --scott
> http://blogs.sun.com/sdaven
> 
> [ Sep 12 09:58:17 Method "start" exited with status 1. ]
> [ Sep 12 10:00:41 Leaving maintenance because clear requested. ]
> [ Sep 12 10:00:41 Enabled. ]
> [ Sep 12 10:00:42 Executing start method ("/lib/svc/method/xvm-domains
> start"). ]
> Traceback (most recent call last):
>   File "/lib/svc/method/xvm-domains", line 39, in ?
>     server.xend.domain.autostart()
>   File "/usr/lib/python2.4/xmlrpclib.py", line 1096, in __call__
>     return self.__send(self.__name, args)
>   File "/usr/lib/python2.4/site-packages/xen/util/xmlrpcclient.py", line
> 118, in __request
>   File "/usr/lib/python2.4/xmlrpclib.py", line 1383, in __request
>     verbose=self.__verbose
>   File "/usr/lib/python2.4/site-packages/xen/util/xmlrpcclient.py", line
> 55, in request
>   File "/usr/lib/python2.4/xmlrpclib.py", line 1137, in request
>     headers
> xmlrpclib.ProtocolError: <ProtocolError for /RPC2: -1 >
> [ Sep 12 10:00:42 Method "start" exited with status 1. ]
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> xen-discuss mailing list
> [email protected]
_______________________________________________
xen-discuss mailing list
[email protected]

Reply via email to