Re: [Xen-users] Error 22 on domU creation after installing 3.1 from source

[p <p@xxxxxxxx>]

p wrote:
> Hi all,
>
> I just compiled an installed the Xen Hypervisor, Tools and a new 
> Kernel from the 3.1 source.
> The dom0 is running without problem and the xm seems to work fine, too 
> (tried xm info, xm list, xm dmesg).
> Unforunately on creation of a domU I always get an error using a 
> config file and a domU image that is definitley working (at least with 
> 3.0.4):
> Using config file "/etc/xen/domU1.cfg".
> Error: (22, 'Invalid argument')
>
> Then log says:
>
> [2007-07-13 17:51:40 xend.XendDomainInfo 5298] DEBUG 
> (XendDomainInfo:190) XendDomainInfo.create(['vm', ['name', 'domU'], 
> ['memory', 128], ['vcpus', 1], ['image', ['linux', ['kernel', 
> '/boot/vmlinuz-2.6-xen'], ['ramdisk', '/boot/initramfs-2.6.18-xen'], 
> ['root', '/dev/hda1 ro'], ['args', '4']]], ['device', ['vbd', 
> ['uname', 'file:/srv/domU_1.img'], ['dev', 'hda1'], ['mode', 'w']]], 
> ['device', ['vif', ['bridge', 'xenbr0'], ['mac', '00:16:3e:00:00:13']]]])
> [2007-07-13 17:51:40 xend.XendDomainInfo 5298] DEBUG 
> (XendDomainInfo:296) parseConfig: config is ['vm', ['name', 'domU'], 
> ['memory', 128], ['vcpus', 1], ['image', ['linux', ['kernel', 
> '/boot/vmlinuz-2.6-xen'], ['ramdisk', '/boot/initramfs-2.6.18-xen'], 
> ['root', '/dev/hda1 ro'], ['args', '4']]], ['device', ['vbd', 
> ['uname', 'file:/srv/domU_1.img'], ['dev', 'hda1'], ['mode', 'w']]], 
> ['device', ['vif', ['bridge', 'xenbr0'], ['mac', '00:16:3e:00:00:13']]]]
> [2007-07-13 17:51:40 xend.XendDomainInfo 5298] DEBUG 
> (XendDomainInfo:395) parseConfig: result is {'shadow_memory': None, 
> 'uuid': None, 'on_crash': None, 'on_reboot': None, 'localtime': None, 
> 'image': ['linux', ['kernel', '/boot/vmlinuz-2.6-xen'], ['ramdisk', 
> '/boot/initramfs-2.6.18-xen'], ['root', '/dev/hda1 ro'], ['args', 
> '4']], 'on_poweroff': None, 'bootloader_args': None, 'cpus': None, 
> 'name': 'domU', 'backend': [], 'vcpus': 1, 'cpu_weight': None, 
> 'features': None, 'vcpu_avail': None, 'memory': 128, 'device': 
> [('vbd', ['vbd', ['uname', 'file:/srv/domU_1.img'], ['dev', 'hda1'], 
> ['mode', 'w']]), ('vif', ['vif', ['bridge', 'xenbr0'], ['mac', 
> '00:16:3e:00:00:13']])], 'bootloader': None, 'cpu': None, 'maxmem': None}
> [2007-07-13 17:51:40 xend.XendDomainInfo 5298] DEBUG 
> (XendDomainInfo:1262) XendDomainInfo.construct: None
> [2007-07-13 17:51:40 xend.XendDomainInfo 5298] ERROR (__init__:1021) 
> Domain construction failed
> Traceback (most recent call last):
>  File "/usr/lib/python2.5/site-packages/xen/xend/XendDomainInfo.py", 
> line 194, in create
>    vm.construct()
>  File "/usr/lib/python2.5/site-packages/xen/xend/XendDomainInfo.py", 
> line 1266, in construct
>    handle = uuid.fromString(self.info['uuid']))
> Error: (22, 'Invalid argument')
> [2007-07-13 17:51:40 xend.XendDomainInfo 5298] DEBUG 
> (XendDomainInfo:1458) XendDomainInfo.destroy: domid=None
> [2007-07-13 17:51:40 xend 5298] ERROR (__init__:1021) (22, 'Invalid 
> argument')
> Traceback (most recent call last):
>  File "/usr/lib/python2.5/site-packages/xen/util/xmlrpclib2.py", line 
> 162, in _marshaled_dispatch
>    response = self._dispatch(method, params)
>  File "SimpleXMLRPCServer.py", line 415, in _dispatch
>    return func(*params)
>  File 
> "/usr/lib/python2.5/site-packages/xen/xend/server/XMLRPCServer.py", 
> line 64, in domain_create
>    info = XendDomain.instance().domain_create(config)
>  File "/usr/lib/python2.5/site-packages/xen/xend/XendDomain.py", line 
> 228, in domain_create
>    dominfo = XendDomainInfo.create(config)
>  File "/usr/lib/python2.5/site-packages/xen/xend/XendDomainInfo.py", 
> line 194, in create
>    vm.construct()
>  File "/usr/lib/python2.5/site-packages/xen/xend/XendDomainInfo.py", 
> line 1266, in construct
>    handle = uuid.fromString(self.info['uuid']))
> Error: (22, 'Invalid argument')
>
> I hope someone can help ;)
>
> Kind Regards
>
> Philipp
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
Solved ;)
There was an old binary installation of the tools.

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