Hello
I don't know about Suse init scripts .. never messed too much with them,
but I belive that you can do some 'black magic' with the ifup scripts
and setup all your 'xen aware network' once you bring your interfaces up
(and before any daemon starts).
I starting making some test by not using any network script with xend,
doing all network/bridge/blahblah stuff by hand .. and testing what was
needed or not (and reading xen scripts). I have no problems anymore
related with the 'interface renaming' (notably bind and squid needed
restarts after xend).
[]'s
BTW, can someone set the list to force the reply-to address to the list
itself :-P .. so clicking in the reply button would reply to the list,
not to the email's author ?
On Mon, 2006-12-04 at 13:05 +0100, Ulrich Windl wrote:
> On 4 Dec 2006 at 11:33, Theo Cabrerizo Diem wrote:
>
> > and so on ... But (on debian unstable at least) I had some daemons
> > running before xend was started (bind for example, NFS mounts) and this
> > messed everything.
>
> Hi!
>
> In SLES10 there are also several networking services started before xend:
> NFS, SLP, SSH, NTP, ...
>
> I'm unsure whether this causes problems, because the correct configuration
> (XEN
> using bonding) did never work reliable (causing broadcast storms, etc.), but
> a
> somewhat illegal configuration seems to work (specifying the enslaved bonding
> interface to be added to the XEN bridge). I was unable to fix the provided
> scripts
> to make bonding work as expected...
>
> Regards,
> Ulrich
>
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home