Jorge Viana
2010-Mar-19 18:59 UTC
[Xen-users] Instability and xend not starting after crashed
hi everybody, I''m have a huge problem!
I have 2 hosts, host 1 with xen 3.3.1 and host 2 with xen 3.4.2. Host 1 was
running some guests for some days and today morning all guests crashed, xm
non-responsive and some minutes after the entire host crashed, I had to do a
cold reboot.
I tried to start guests on host 2, when I started the second guest same
problem. The difference is the host 1 after reboot xend started normally and
hosts 2 xend is not starting anymore. So... actually I have 2 big problem,
(1) instability (2) xend not working after crashed.
( This is not the first time it happened... the both problems! )
Any ideias?
Host 1 - instability
/var/log/xen/xend.log
[2010-03-19 13:00:21 4961] DEBUG (XendDomainInfo:1359) Storing domain
details: {''image/entry'':
''18446744071564165120'', ''conso
le/port'': ''2'', ''image/loader'':
''generic'', ''vm'':
''/vm/4d14f873-ddfa-ef3c-dba7-7f4987946629'',
''control/platform-feature-multiprocessor-suspend'':
''1'', ''image/guest-os'':
''linux'',
''image/features/writable-descriptor-tables'':
''1'',
''image/virt-base'': ''18446744071562067968'',
''memory/target'': ''524288'',
''image/guest-version'': ''2.6'',
''image/features/supervisor-mode-kernel'':
''1'',
''console/limit'': ''1048576'',
''image/paddr-offset'':
''18446744071562067968'',
''image/hypercall-page'':
''18446744071564189696'',
''image/suspend-cancel'': ''1'',
''cpu/0/availability'': ''online'',
''image/features/pae-pgdir-above-4gb'': ''1'',
''image/features/writable-page-tables'': ''1'',
''console/type'': ''xenconsoled'',
''image/features/auto-translated-physmap'':
''1'', ''name'': ''Migracao'',
''domid'':
''1'', ''image/xen-version'':
''xen-3.0'', ''store/port'':
''1''}
[2010-03-19 13:00:21 4961] DEBUG (XendCheckpoint:247) restore:shadow=0x0,
_static_max=0x5dc00000, _static_min=0x0,
[2010-03-19 13:00:21 4961] DEBUG (balloon:132) Balloon: 15033208 KiB free;
need 524288; done.
[2010-03-19 13:00:21 4961] DEBUG (XendCheckpoint:264) [xc_restore]:
/usr/lib64/xen/bin/xc_restore 53 1 1 2 0 0 0
[2010-03-19 13:00:21 4961] INFO (XendCheckpoint:403) ERROR Internal error:
read: p2m_size
[2010-03-19 13:00:21 4961] INFO (XendCheckpoint:403) Restore exit with rc=1
[2010-03-19 13:00:21 4961] DEBUG (XendDomainInfo:2389)
XendDomainInfo.destroy: domid=1
[2010-03-19 13:00:21 4961] DEBUG (XendDomainInfo:2406)
XendDomainInfo.destroyDomain(1)
[2010-03-19 13:00:21 4961] ERROR (XendDomainInfo:2418)
XendDomainInfo.destroy: xc.domain_destroy failed.
Traceback (most recent call last):
File "/usr/lib/python2.5/site-packages/xen/xend/XendDomainInfo.py",
line
2413, in destroyDomain
xc.domain_destroy(self.domid)
Error: (3, ''No such process'')
[2010-03-19 13:00:21 4961] DEBUG (XendDomainInfo:1944) No device model
[2010-03-19 13:00:21 4961] DEBUG (XendDomainInfo:1946) Releasing devices
[2010-03-19 13:00:21 4961] DEBUG (XendDomainInfo:1952) Removing vif/0
[2010-03-19 13:00:21 4961] DEBUG (XendDomainInfo:888)
XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0
[2010-03-19 13:00:21 4961] DEBUG (XendDomainInfo:1952) Removing vbd/2048
[2010-03-19 13:00:21 4961] DEBUG (XendDomainInfo:888)
XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/2048
[2010-03-19 13:00:21 4961] DEBUG (XendDomainInfo:1952) Removing console/0
[2010-03-19 13:00:21 4961] DEBUG (XendDomainInfo:888)
XendDomainInfo.destroyDevice: deviceClass = console, device = console/0
[2010-03-19 13:00:21 4961] ERROR (XendDomain:1143) Restore failed
Traceback (most recent call last):
File "/usr/lib/python2.5/site-packages/xen/xend/XendDomain.py", line
1141,
in domain_restore_fd
return XendCheckpoint.restore(self, fd, paused=paused,
relocating=relocating)
File "/usr/lib/python2.5/site-packages/xen/xend/XendCheckpoint.py",
line
268, in restore
forkHelper(cmd, fd, handler.handler, True)
File "/usr/lib/python2.5/site-packages/xen/xend/XendCheckpoint.py",
line
391, in forkHelper
raise XendError("%s failed" % string.join(cmd))
XendError: /usr/lib64/xen/bin/xc_restore 53 1 1 2 0 0 0 failed
Host 2 - instability and xend not working after crashed
# xm list
Error: Unable to connect to xend: No such file or directory. Is xend
running?
/var/log/xen/xend.log
2010-03-19 14:03:58 7059] INFO (SrvDaemon:332) Xend Daemon started
[2010-03-19 14:03:58 7059] INFO (SrvDaemon:336) Xend changeset: unavailable.
[2010-03-19 14:03:58 7059] ERROR (SrvDaemon:349) Exception starting xend
([Errno 99] Cannot assign requested address)
Traceback (most recent call last):
File
"/usr/local/lib/python2.6/dist-packages/xen/xend/server/SrvDaemon.py",
line
339, in run
relocate.listenRelocation()
File
"/usr/local/lib/python2.6/dist-packages/xen/xend/server/relocate.py",
line 159, in listenRelocation
hosts_allow = hosts_allow)
File "/usr/local/lib/python2.6/dist-packages/xen/web/tcp.py", line
36, in
__init__
connection.SocketListener.__init__(self, protocol_class)
File "/usr/local/lib/python2.6/dist-packages/xen/web/connection.py",
line
89, in __init__
self.sock = self.createSocket()
File "/usr/local/lib/python2.6/dist-packages/xen/web/tcp.py", line
49, in
createSocket
sock.bind((self.interface, self.port))
File "<string>", line 1, in bind
error: [Errno 99] Cannot assign requested address
[2010-03-19 14:03:58 7057] INFO (SrvDaemon:220) Xend exited with status 1.
/var/log/xen/xend-debug.log
Xend started at Fri Mar 19 14:03:58 2010.
Exception starting xend: [Errno 99] Cannot assign requested address
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users