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

Xen doesn't start



Hi

When I try to start xend, I get the following error in
/var/log/xen/xend-debug.log:

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.

This happen when I pass somthing like
vif=[ 'mac=20:30:50:00:60:11, bridge=vif' ]
in /etc/xen/auto/vm01-config.sxp

How I should create a bridge for Xen or how I can solve this problem ?

Tail of /var/log/xen/xend.log:

[2006-11-10 19:43:36 xend 6386] INFO (__init__:1072) Xend Daemon started
[2006-11-10 19:43:36 xend 6386] INFO (__init__:1072) Xend changeset:
Thu Sep 21 17:56:14 2006 +0100 .
[2006-11-10 19:43:36 xend.XendDomainInfo 6386] DEBUG (__init__:1072)
XendDomainInfo.recreate({'paused': 0, 'cpu_time': 313939411975L,
'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': 65536,
'maxmem_kb': -4, 'max_vcpu_id': 0, 'crashed': 0, 'running': 1,
'shutdown': 0, 'online_vcpus': 1, 'blocked': 0})
[2006-11-10 19:43:36 xend.XendDomainInfo 6386] INFO (__init__:1072)
Recreating domain 0, UUID 00000000-0000-0000-0000-000000000000.
[2006-11-10 19:43:36 xend 6386] DEBUG (__init__:1072) number of vcpus
to use is 0
[2006-11-10 19:43:36 xend.XendDomainInfo 6386] DEBUG (__init__:1072)
XendDomainInfo.handleShutdownWatch


kernel version:
2.6.17-2-xen-686 #1 SMP Wed Sep 13 20:58:20 UTC 2006 i686 GNU/Linux

Installed packages for Xen:
xen-hypervisor-3.0-unstable-1-i386 3.0-unstable+hg11561-1
xen-ioemu-3.0-unstable             3.0-unstable+hg11561-1
xen-linux-system-2.6.17-2-xen-686  2.6.17-9
xen-utils-3.0-unstable-1           3.0-unstable+hg11561-1
xen-utils-common                   3.0+hg11624-2



Reply to: