You can take a look at the kernel boot parameters:
For example "max_loop=64" can help you solve your issue (To put in
your grub.conf boot file).
Have Fun,
2006年3月2日, Konstantinos Pachopoulos <kostaspaxos@xxxxxxxx>:
> Hi,
> The same thing happens for eth1. Why does it complain?
> veth0 isn't supposed to exist anyway.
> -----------------------------------------
> vakhos:/etc/xen/scripts# ./network-bridge start
> bridge=xenbr-clu netdev=dummy0
>
> 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.
> -----------------------------------------
> How can i pass the nloopbacks (dummy is a module)
> parameter, if this is necessary?
>
> I have also manually created a bridge and then edited
> the conf files of the domains accordingly. The virtual
> interfaces (all of them in the same subnet) of the
> domains were added on the bridge, but i couldn't ping
> from domain to domain. Why?
>
> Thanks
>
>
>
> ___________________________________________________________
> To help you stay safe and secure online, we've developed the all new Yahoo! 
> Security Centre. http://uk.security.yahoo.com 
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users 
>
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users