[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: [fedora-virt] bridged guest networking in f12 with netcf
- From: Cole Robinson <crobinso redhat com>
- To: Dale Bewley <dlbewley lib ucdavis edu>
- Cc: Fedora Virtualization List <fedora-virt redhat com>
- Subject: Re: [fedora-virt] bridged guest networking in f12 with netcf
- Date: Mon, 16 Nov 2009 14:39:01 -0500
On 11/16/2009 01:51 PM, Dale Bewley wrote:
> ----- "Cole Robinson" <crobinso redhat com> wrote:
>>> = Network =
>>> And finally, after creating this bridge, it would be nice to create
>> a network which utilizes it as follows. That fails the way I attempted
>> to do it.
>>>
>>> [root tofu2 ~]# cat net-bridged.xml
>>> <network>
>>> <name>bridged</name>
>>> <forward mode='route'/>
>>> <bridge name='br0' />
>>> </network>
>>>
>>
>> Physical device bridges are referenced directly in the VM xml, not via
>> the
>> virtual network XML. Example interface device block to add to your
>> VM:
>>
>> <interface type='bridge'>
>> <source bridge='br0'/>
>> <mac address="11:22:33:44:55:66"/>
>> </interface>
>>
>> - Cole
>
> I understand that, but I did lose track of that in my mind. It doesn't
> make much sense to refer to it as a 'network'. I do see that br0 shows
> up in the network/interface selection dialog of the VM creation wizard.
>
> One thing I just noticed is that NetworkManager is taking ownership
> of eth0 and preventing the br0 from being created. One fix is to
>
> chkconfig NetworkManager off
> chkconfig network on
> service NetworkManager stop
> service network restart
>
> I suppose the other solution would be to educate NetworkManager
> about the new configuration, but I've never really used paid much
> attention to NM. I'd have to look into how to do that properly.
>
Yes, this NetworkManager pain is a long known deficiency. NM and bridges
just don't play well together.
- Cole
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]