[Xen-users] Error 22 - dom0 crash on domU start

[p <p@xxxxxxxx>]

Hi there,

I have a problem "porting" my domU to another kernel.

I had used the Ubtuntu 6.10 generic kernel, for both dom0 and domU, but 
since there was no module support I compiled my own.
dom0 is up and running again, but when I try to create the domU I get an 
error (had first a special domU kernel used, but also tried the dom0 
kernel. there was no difference)
root@main:~# xm cr -c /etc/xen/root.cfg
Using config file "/etc/xen/root.cfg".
Error: (22, 'Invalid argument')

---
/var/log/xen/xend.log

['root', '/dev/hda1 ro']]], ['device', ['vbd', ['uname', 
'file:/srv/images/root66_ext3.img'], ['dev', 'hda1'], ['mode', 'w']]], 
['device', ['vbd', ['uname', 'file:/srv/images/root66_swap.img'], 
['dev', 'hda2'], ['mode', 'w']]], ['device', ['vif', ['bridge', 
'xenbr0']]]])
[2007-03-19 16:43:13 xend.XendDomainInfo 3202] DEBUG (__init__:1072) 
parseConfig: config is ['vm', ['name', 'root66'], ['memory', 384], 
['vcpus', 1], ['image', ['linux', ['kernel', '/boot/vmlinuz-2.6-xen0'], 
['root', '/dev/hda1 ro']]], ['device', ['vbd', ['uname', 
'file:/srv/images/root66_ext3.img'], ['dev', 'hda1'], ['mode', 'w']]], 
['device', ['vbd', ['uname', 'file:/srv/images/root66_swap.img'], 
['dev', 'hda2'], ['mode', 'w']]], ['device', ['vif', ['bridge', 'xenbr0']]]]
[2007-03-19 16:43:13 xend.XendDomainInfo 3202] DEBUG (__init__:1072) 
parseConfig: result is {'shadow_memory': None, 'uuid': None, 'on_crash': 
None, 'on_reboot': None, 'localtime': None, 'image': ['linux', 
['kernel', '/boot/vmlinuz-2.6-xen0'], ['root', '/dev/hda1 ro']], 
'on_poweroff': None, 'bootloader_args': None, 'cpus': None, 'name': 
'root66', 'backend': [], 'vcpus': 1, 'cpu_weight': None, 'features': 
None, 'vcpu_avail': None, 'memory': 384, 'device': [('vbd', ['vbd', 
['uname', 'file:/srv/images/root66_ext3.img'], ['dev', 'hda1'], ['mode', 
'w']]), ('vbd', ['vbd', ['uname', 'file:/srv/images/root66_swap.img'], 
['dev', 'hda2'], ['mode', 'w']]), ('vif', ['vif', ['bridge', 
'xenbr0']])], 'bootloader': None, 'cpu': None, 'maxmem': None}
[2007-03-19 16:43:13 xend.XendDomainInfo 3202] DEBUG (__init__:1072) 
XendDomainInfo.construct: None
[2007-03-19 16:43:13 xend.XendDomainInfo 3202] ERROR (__init__:1072) 
Domain construction failed
Traceback (most recent call last):
File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 
194, in create
vm.construct()
File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 
1257, in construct
handle = uuid.fromString(self.info['uuid']))
Error: (22, 'Invalid argument')
[2007-03-19 16:43:13 xend.XendDomainInfo 3202] DEBUG (__init__:1072) 
XendDomainInfo.destroy: domid=None
[2007-03-19 16:43:13 xend 3202] ERROR (__init__:1072) (22, 'Invalid 
argument')
Traceback (most recent call last):
File "/usr/lib/python2.4/site-packages/xen/util/xmlrpclib2.py", line 
162, in _marshaled_dispatch
response = self._dispatch(method, params)
File "SimpleXMLRPCServer.py", line 406, in _dispatch
return func(*params)
File "/usr/lib/python2.4/site-packages/xen/xend/server/XMLRPCServer.py", 
line 64, in domain_create
info = XendDomain.instance().domain_create(config)
File "/usr/lib/python2.4/site-packages/xen/xend/XendDomain.py", line 
228, in domain_create
dominfo = XendDomainInfo.create(config)
File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 
194, in create
vm.construct()
File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 
1257, in construct
handle = uuid.fromString(self.info['uuid']))
Error: (22, 'Invalid argument')

---

cat /etc/xen/root.cfg

kernel = "/boot/vmlinuz-2.6-xen0"
memory = 384
name = "root66"
image = "linux"
disk = [ 
'file:/srv/images/root66_ext3.img,hda1,w','file:/srv/images/root66_swap.img,hda2,w' 
]
root = "/dev/hda1 ro"
vif = [ 'bridge=xenbr0' ]

---


In addition to this after executing the command (producing the error), 
the next xen related command e.g. xm list, xentop, ... causes a system 
crash.
It stops responding completly and only a hardware reset is getting it 
back to life. (But there's no entry in syslog about any failure...)
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users