Pkg xen devel - Aug 2008 - NetworkManager problems with xen bridging

I've noticed that with NetworkManager running in dom0, there is a lot
of bad behaviour on the bridge interface

After xend creates the bridge (using the sample network-bridge script
in the package), the real interface is known as peth0

NetworkManager starts dhclient on peth0, which means the following:
- peth0 gets it's own IP, maybe not the same as the bridge IP
- a second default route is added to the routing table
- the resolv.conf file sometimes becomes screwed up, depending on what
values come back from the DHCP server

This all seems quite messy.  NetworkManager seems to be installed by
default in lenny.  Is it safe to remove with dpkg --purge?

 Can anyone suggest other strategies for dealing with this?

Could the xen bridge script do something to stop NetworkManager
getting it's hands on this interface?

 Should the xen package warn about this?

At 1220215423 time_t, Sally-Anne Edwards wrote:
> This all seems quite messy.  NetworkManager seems to be installed by
> default in lenny.  Is it safe to remove with dpkg --purge?
Yes.
>  Can anyone suggest other strategies for dealing with this?
Don't use NetworkManager.
> Could the xen bridge script do something to stop NetworkManager
> getting it's hands on this interface?
No. I can't also arrest you if you want to shut down the bridge or the
entire machine.
And just don't use the Xen script, configure it manually in /e/n/i.
>  Should the xen package warn about this?
Kidding, right?

Cheers,
-- 
Julien Danjou
.''`.  Debian Developer
: :' : http://julien.danjou.info
`. `'  http://people.debian.org/~acid
  `-   9A0D 5FD9 EB42 22F6 8974  C95C A462 B51E C2FE E5CD
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
Url :
http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20080901/772b10d8/attachment.pgp

Sally-Anne Edwards writes ("[Pkg-xen-devel] NetworkManager problems with
xen bridging"):
> This all seems quite messy.  NetworkManager seems to be installed by
> default in lenny.  Is it safe to remove with dpkg --purge?
Is n-m really installed (and started) by default ?  If so then I would
hope there is some way for other packages to hit it on the head.  Xen
is far from the only situation where n-m's crazy behaviours are going
to cause trouble.

Ian.