WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] /etc/xen/scripts/network-bridge: line 118: sigerr: comm

> Just after removing the claim_lock* lines, I also specified the
> bridge in the file /etc/xen/xend-config.sxp as it follows:
> (network-script 'network-bridge bridge=xenbr0')
I don't know this syntax.
>
> I always set up that line in the following way since so far:
> (network-script network-bridge)
I do it this way. I made up a script "my-network-bridge" which calls
network-bridge with all my network cards.
>
> Now that I modified that line, I get the xenbr0 interface up at boot time,
> but
> there is also the peth0 interface (I don't want it).
This is the physical interface located in dom0 which is in the bridge.
Before xen came up it was named eth0. After xen created xenbr0 it gets
renamed to peth0.
I do it the way that if I only want a bridge to interconnect domU's then I
use dummy network interfaces to build up a xenbrX of. Then I have pdummy0.
I don't care about p*-interfaces.
>
> I simply had to perform a dhcpcd xenbr0 and the network came up.
> But this should happen automatically, I don't want to perform a dhcpcd
> each time.
I also had this kind of bug that the bridge wasn't always upped correctly
after xm startup.
I simply added "ifconfig xenbr0 0.0.0.0 up" to my /etc/conf.d/local.start.

Daniel


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users