[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] XEN not working after reboot


  • To: xen-users@xxxxxxxxxxxxx
  • From: Rudi Ahlers <Rudi@xxxxxxxxxxx>
  • Date: Fri, 19 Jul 2013 08:13:35 +0200
  • Delivery-date: Fri, 19 Jul 2013 06:15:53 +0000
  • List-id: Xen user discussion <xen-users.lists.xen.org>

We moved some servers from one DC to another DC. The IP addresses and
routing stayed the same (DC handled this) but now XEN doesn't work on
one of the servers.


When I logged in, XEN wasn't running so I manually started it with
"/etc/init.d/xend restart" but then there's no network bridge at all.

Manually starting the network bridge gave me this error:

root@usaxen03:[~]$ /etc/xen/scripts/network-bridge start

Link veth0 is missing.
This may be because you have reached the limit of the number of interfaces
that the loopback driver supports.  If the loopback driver is a module, you
may raise this limit by passing it as a parameter (nloopbacks=<N>); if the
driver is compiled statically into the kernel, then you may set the parameter
using loopback.nloopbacks=<N> on the domain 0 kernel command line.


root@usaxen03:[~]$ uname -a
Linux usaxen03 2.6.18-348.12.1.el5xen #1 SMP Wed Jul 10 01:13:54 EDT
2013 x86_64 x86_64 x86_64 GNU/Linux
root@usaxen03:[~]$ more /etc/redhat-release
Scientific Linux SL release 5.7 (Boron)
root@usaxen03:[~]$



I get the same error in the logs:


root@usaxen03:[~]$ tail -f /var/log/xen/xend-debug.log
using loopback.nloopbacks=<N> on the domain 0 kernel command line.


Link veth0 is missing.
This may be because you have reached the limit of the number of interfaces
that the loopback driver supports.  If the loopback driver is a module, you
may raise this limit by passing it as a parameter (nloopbacks=<N>); if the
driver is compiled statically into the kernel, then you may set the parameter
using loopback.nloopbacks=<N> on the domain 0 kernel command line.



root@usaxen03:[~]$ tail -f /var/log/xen/xend.log
[2013-07-19 08:15:13 xend.XendDomainInfo 3805] DEBUG
(XendDomainInfo:1335) XendDomainInfo.handleShutdownWatch
[2013-07-19 08:19:21 xend 3804] INFO (SrvDaemon:190) Xend stopped due
to signal 15.
[2013-07-19 08:19:21 xend 4199] INFO (SrvDaemon:283) Xend Daemon started
[2013-07-19 08:19:21 xend 4199] INFO (SrvDaemon:287) Xend changeset:
unavailable.
[2013-07-19 08:19:21 xend.XendDomainInfo 4199] DEBUG
(XendDomainInfo:283) XendDomainInfo.recreate({'paused': 0, 'cpu_time':
24358134692L, 'ssidref': 0, 'vm': 0, 'shutdown_reason': 0, 'dying': 0,
'mem_kb': 524288L, 'domid': 0, 'max_vcpu_id': 7, 'crashed': 0,
'running': 1, 'maxmem_kb': 17179869180L, 'shutdon': 0, 'online_vcpus':
1, 'handle': [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0],
'blocked': 0})
[2013-07-19 08:19:21 xend.XendDomainInfo 4199] INFO
(XendDomainInfo:295) Recreating domain 0, UUID
00000000-0000-0000-0000-000000000000.
[2013-07-19 08:19:21 xend.XendDomainInfo 4199] DEBUG
(XendDomainInfo:1439) Setting maximum memory value of domain Domain-0
(0) to 16375 MiB.
[2013-07-19 08:19:21 xend 4199] DEBUG (XendDomain:166) number of vcpus
to use is 1
[2013-07-19 08:19:21 xend 4199] INFO (SrvServer:116) unix
path=/var/lib/xend/xend-socket
[2013-07-19 08:19:21 xend.XendDomainInfo 4199] DEBUG
(XendDomainInfo:1335) XendDomainInfo.handleShutdownWatch





Does anyone know what could cause this, or how to fix it?



-- 
Kind Regards
Rudi Ahlers
SoftDux

Website: http://www.SoftDux.com
Technical Blog: http://Blog.SoftDux.com
Cell: 082 554 7532
Fax: 086 268 8492

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.