On 02/10/2014 01:43 PM, Orion Poplawski wrote:
On 02/10/2014 10:29 AM, Jan Grulich wrote:
> Dne Po 10. Ășnora 2014 09:51, Orion Poplawski napsal(a):
>> - I have some virbr0 interfaces:
>>
>> 3: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
state
>> DOWN group default
>> link/ether 52:54:00:6c:03:49 brd ff:ff:ff:ff:ff:ff
>> inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
>> valid_lft forever preferred_lft forever
>> 4: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast master
virbr0
>> state DOWN group default qlen 500
>> link/ether 52:54:00:6c:03:49 brd ff:ff:ff:ff:ff:ff
>>
>> - in the widget virbr0 shows up in the available connections as
"Connecting"
>> and has a spinner going. I'm not sure if this was present under the old
>> version or not - but it seems not correct to me.
>>
>
> According to google, virbr device (virtual bridge) comes from libvirt and it's
possible that NetworkManager is trying to activate them, but without success, because
it's not probably properly configured, so I would suggest to disable autoconnect.
It's working fine. I'm more thinking that kde shouldn't even show it -
perhaps not show any bridge connections? But perhaps there is some other bug
that:
# nmcli c show virbr0
....
GENERAL.STATE: activating
which is probably why the kde widget shows the spinner.
This turns out to be a NetworkManager issue. Downgrading from
NetworkManager-0.9.9.0-29.git20140131.fc20 to
NetworkManager-0.9.9.0-28.git20131003.fc20 remove virbr0 from the list of
active connections.
--
Orion Poplawski
Technical Manager 303-415-9701 x222
NWRA, Boulder/CoRA Office FAX: 303-415-9702
3380 Mitchell Lane orion(a)nwra.com
Boulder, CO 80301
http://www.nwra.com