5:33 a.m.
The desire to automatically install the autostarted network configuration
of libvirt broke my (and some other users on xen-users) setup. I suggest
to *remove* this network configuration as default and *not* put it into
xenstore as a stateful config.
*It does not work by default*
Worse is that it is almost impossible to debug if you don't know where to
find it.
Stefan
7:13 a.m.
On Fri, Jul 18, 2008 at 12:33:22PM +0200, Stefan de Konink wrote:
The desire to automatically install the autostarted network
configuration
of libvirt broke my (and some other users on xen-users) setup. I suggest
to *remove* this network configuration as default and *not* put it into
xenstore as a stateful config.
*It does not work by default*
It works just fine by default. If anything is breaking networking it is
XenD.
Daniel
--
|: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :|
|: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|
1:14 p.m.
On Fri, Jul 18, 2008 at 01:13:30PM +0100, Daniel P. Berrange wrote:
On Fri, Jul 18, 2008 at 12:33:22PM +0200, Stefan de Konink wrote:
> The desire to automatically install the autostarted network configuration
> of libvirt broke my (and some other users on xen-users) setup. I suggest
> to *remove* this network configuration as default and *not* put it into
> xenstore as a stateful config.
>
> *It does not work by default*
It works just fine by default. If anything is breaking networking it is
XenD.
You don't mention which version of Xen you have, but make sure you have
this changeset in it..
[quote]
changeset: 16625:44a98411d230
user: Keir Fraser <keir.fraser(a)citrix.com>
date: Sat Dec 15 18:26:52 2007 +0000
files: tools/python/xen/xend/XendNetwork.py
description:
xend: Prevent XenD touching externally managed bridges
With current XenD 3.0.4 or later try the following:
brctl addbr demo
ifconfig demo up
/etc/init.d/xend start
/etc/init.d/xend stop
ifconfig demo down
brctl delbr demo
Now, start XenD again....
/etc/init.d/xend start
And watch in horror as it re-creates your 'demo' bridge.
The problem is that the 'XendNetwork' class does not distinguish
between bridge devices that it is managing (ie those created via
XenAPI) and those which it does not manage (ie those created by OS
distro init scripts, or by apps like libvirt).
While initially I thought I could just make XenD ignore
externally-managed bridges completely, it seems to needs to know about
them otherwise it can't hook up guest VIFs to them correctly. So the
attached patch adds a 'managed' flag to the XendNetwork
class. Externally managed bridges have this set to False. At startup
XenD will now only re-create bridge devices which have the 'managed'
flag set to 'True' - ie those created via XenAPI.
Signed-off-by: Daniel P. Berrange <berrange(a)redhat.com>
[/quote]
Daniel
--
|: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :|
|: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|
1:20 p.m.
Daniel P. Berrange schreef:
On Fri, Jul 18, 2008 at 01:13:30PM +0100, Daniel P. Berrange wrote:
> On Fri, Jul 18, 2008 at 12:33:22PM +0200, Stefan de Konink wrote:
>> The desire to automatically install the autostarted network configuration
>> of libvirt broke my (and some other users on xen-users) setup. I suggest
>> to *remove* this network configuration as default and *not* put it into
>> xenstore as a stateful config.
>>
>> *It does not work by default*
> It works just fine by default. If anything is breaking networking it is
> XenD.
You don't mention which version of Xen you have, but make sure you have
this changeset in it..
3.2.1, that looks much later than the patch you send, and the last time
I check the bridge was created due to the network.xml stateful xenstore
config.
Stefan
1:15 p.m.
Daniel P. Berrange schreef:
On Fri, Jul 18, 2008 at 12:33:22PM +0200, Stefan de Konink wrote:
> The desire to automatically install the autostarted network configuration
> of libvirt broke my (and some other users on xen-users) setup. I suggest
> to *remove* this network configuration as default and *not* put it into
> xenstore as a stateful config.
>
> *It does not work by default*
It works just fine by default. If anything is breaking networking it is
XenD.
The default is xenbr0... and since xend is still required for all
operations, it is a bit strange to claim it breaks itself...
Stefan
1:25 p.m.
On Fri, Jul 18, 2008 at 08:15:20PM +0200, Stefan de Konink wrote:
Daniel P. Berrange schreef:
>On Fri, Jul 18, 2008 at 12:33:22PM +0200, Stefan de Konink wrote:
>>The desire to automatically install the autostarted network configuration
>>of libvirt broke my (and some other users on xen-users) setup. I suggest
>>to *remove* this network configuration as default and *not* put it into
>>xenstore as a stateful config.
>>
>>*It does not work by default*
>
>It works just fine by default. If anything is breaking networking it is
>XenD.
The default is xenbr0... and since xend is still required for all
operations, it is a bit strange to claim it breaks itself...
The 'default' is whatever your management app decides is the default
(if any), which has nothing todo with what XenD creates by default.
virt-install will default to the bridge associated with the default
route, if none is found it'll use the first libvirt virtual network
it finds. Fedora does not create 'xenbr0' in a standard install so
the virbr0 will always be used unless the admin has configured full
bridging. Even if the admin has got bridging configured, the prescence
of virbr0 does not impact that functionality.
Daniel
--
|: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :|
|: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|
5971
days inactive
5971
days old
5 comments
2 participants
participants (2)
-
Daniel P. Berrange -
Stefan de Konink