p
2007-Mar-23 11:27 UTC
[Xen-devel] dom0 crash on second xen related command - problem for xen devel
Hi there,
this problem was posted twice on xen-users mailing list and they said we
should forward it to the devel list ;)
--- --- --- --- --- --- --- --- --- --- --- ---
---
Description 1:
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...)
--- --- --- --- --- --- --- --- --- --- --- ---
---
Description 2:
Hi all,
I had installed the Xen 3.0.3 on a opensuse 10.2 (64 bits) on new
quadcore intel processors with VT support, on a Dell Power Edge 1955
blade. I had many machines working. This installation had a poor network
performance when using hardware virtualization. My applications for MPI
require low network latencies.
I try to upgrade to Xen 3,0.4 to check the network performance.
I downloaded the tarball, and I installed it.
Now my machines doesn''t run. Aditionally at the secont xm related
comand
used the dom0 crashs ... causes a system crash.
Any help is wellcomed
regards, cesar
My /var/log/xen/xend.log says:
[2007-03-19 15:34:57 xend 3391] INFO (SrvDaemon:283) Xend Daemon started
[2007-03-19 15:34:57 xend 3391] INFO (SrvDaemon:287) Xend changeset: Mon
Jan 08 14:09:25 2007 +0000 13130:4d34be661f31.
[2007-03-19 15:34:58 xend.XendDomainInfo 3391] DEBUG
(XendDomainInfo:212) XendDomainInfo.recreate({''paused'': 0,
''cpu_time''
: 16194471880L, ''ssidref'': 0, ''handle'': [0,
0, 0, 0, 0, 0, 0, 0, 0, 0,
0, 0, 0, 0, 0, 0], ''shutdown_reason'': 0,
''dying'': 0
, ''dom'': 0, ''mem_kb'': 512144,
''maxmem_kb'': 17179869180, ''max_vcpu_id'':
7, ''crashed'': 0, ''running'': 1,
''shutdown'': 0, ''onli
ne_vcpus'': 8, ''blocked'': 0})
[2007-03-19 15:34:58 xend.XendDomainInfo 3391] INFO (XendDomainInfo:224)
Recreating domain 0, UUID 00000000-0000-0000-0000
-000000000000.
[2007-03-19 15:34:58 xend.XendDomainInfo 3391] WARNING
(XendDomainInfo:246) No vm path in store for existing domain 0
[2007-03-19 15:34:58 xend.XendDomainInfo 3391] DEBUG
(XendDomainInfo:712) Storing VM details: {''shadow_memory'':
''0'', ''uuid
'': ''00000000-0000-0000-0000-000000000000'',
''on_reboot'': ''restart'',
''on_poweroff'': ''destroy'',
''name'': ''Domain-0'', ''xend/res
tart_count'': ''0'', ''vcpus'':
''8'', ''vcpu_avail'': ''1'',
''memory'': ''501'',
''on_crash'': ''restart'',
''maxmem'': ''501''}
[2007-03-19 15:34:58 xend.XendDomainInfo 3391] DEBUG
(XendDomainInfo:747) Storing domain details:
{''cpu/1/availability'': ''
offline'', ''cpu/3/availability'':
''offline'', ''name'':
''Domain-0'',
''console/limit'': ''1048576'',
''cpu/2/availability'': ''offline''
, ''vm'':
''/vm/00000000-0000-0000-0000-000000000000'',
''domid'': ''0'',
''cpu/7/availability'': ''offline'',
''cpu/0/availability'': ''
online'', ''memory/target'': ''513024'',
''cpu/5/availability'': ''offline'',
''cpu/6/availability'': ''offline'',
''cpu/4/availability''
: ''offline''}
[2007-03-19 15:34:58 xend 3391] DEBUG (XendDomain:153) number of vcpus
to use is 0
[2007-03-19 15:34:58 xend.XendDomainInfo 3391] DEBUG
(XendDomainInfo:933) XendDomainInfo.handleShutdownWatch
xen04:/etc/init.d
--- --- --- --- --- --- --- --- --- --- --- ---
---
Meanwhile I found a solution for the first description, but I think it
is a kind of work around ;)
I used the xen-hypervisor and the xen-util out of the Ubuntu
repositories instead of compile my own.
In addition to this I didn''t used the xensource source code any more,
but instead the one (again) out of Ubuntu repos.
Using the same .config, this time there wasn''t a problem at all...
Therefore I think there is another hidden problem
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel