Xen users - May 2007 - problem upgrading to 3.1.0

Does the xm config file format change between 3.0.3 and 3.1.0?

I''m running fedora 6 and I just built and installed the xen HV and
tools
from source but left the kernel in place.  That means I''m running a
3.0.3 kernel on Dom0 with 3.1.0 HV and tools.

Anyway, I go to start a DomU that was working fine before upgrading
the HV and tools and I get 

Using config file "/etc/xen/tintin2".
Error: (22, ''Invalid argument'')

Not a very helpful error message.  I poked around in create.py and found a
place to print a traceback, and it looks like this:

Traceback (most recent call last):
  File "/usr/lib64/python2.4/xen/xm/create.py", line 1051, in
make_domain
    dominfo = server.xend.domain.create(config)
  File "/usr/lib64/python2.4/xmlrpclib.py", line 1096, in __call__
    return self.__send(self.__name, args)
  File "//usr/lib64/python/xen/util/xmlrpcclient.py", line 118, in
__request
  File "/usr/lib64/python2.4/xmlrpclib.py", line 1383, in __request
    verbose=self.__verbose
  File "//usr/lib64/python/xen/util/xmlrpcclient.py", line 55, in
request
  File "/usr/lib64/python2.4/xmlrpclib.py", line 1147, in request
    return self._parse_response(h.getfile(), sock)
  File "/usr/lib64/python2.4/xmlrpclib.py", line 1286, in
_parse_response
    return u.close()
  File "/usr/lib64/python2.4/xmlrpclib.py", line 744, in close
    raise Fault(**self._stack[0])

Since the error is coming from something that seems to be for parsing
XML and my config file is the same old non-xml config file I was using
with 3.0.3, I''m wondering if my config file is supposed to be XML now.
If so, is there a tool to convert a 3.0.3 config file to the XML
format?

Thanks
-Dylan
 

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

Dylan Martin wrote:
> Does the xm config file format change between 3.0.3 and 3.1.0?
> 
> I''m running fedora 6 and I just built and installed the xen HV and
tools
> from source but left the kernel in place.  That means I''m running
a
> 3.0.3 kernel on Dom0 with 3.1.0 HV and tools.
> 
> Anyway, I go to start a DomU that was working fine before upgrading
> the HV and tools and I get 
> 
> Using config file "/etc/xen/tintin2".
> Error: (22, ''Invalid argument'')
I had a similar problem when I upgraded from 3.0.3 to 3.0.4. In my domU
config files I had
cpus = ""
which caused 3.0.4 to give me a "Invalid argument" (if I recall
correctly), upon running xm create.
Commenting this out helped for me.


/Håkan


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