wired ethernet disabled between reboots, was: when startup delays become bugs

Reartes Guillermo rtguille at gmail.com
Thu May 16 21:05:08 UTC 2013


Adam,

> the groupinstall virtualization, and creating a VM with a NIC set to
> bridged mode.


Maybe this refers to creating a macvtap bridge NIC.

Cheers.

On Thu, May 16, 2013 at 6:01 PM, Adam Williamson <awilliam at redhat.com> wrote:
> On Thu, 2013-05-16 at 14:57 -0600, Chris Murphy wrote:
>> On May 16, 2013, at 2:17 PM, Chris Murphy <lists at colorremedies.com> wrote:
>>
>> >
>> > OK well this isn't right. On every reboot, wireless is activated and connected to. But the wired connection is disabled.
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=963952
>>
>> The most relevant line I'm finding is this:
>>
>> May 16 14:19:22 F19.localdomain NetworkManager[408]: <info> (p5p1): deactivating device (reason 'managed') [2]
>>
>>
>> This doesn't happen when booting from Live media, so something's
>> changed since then it seems. The only two things I can think of are
>> the groupinstall virtualization, and creating a VM with a NIC set to
>> bridged mode. But on F18, that same setup doesn't cause this behavior.
>
> I was still operating under the belief that KVM bridging isn't really
> compatible with NM; on my VM host box I disabled NM and used
> network.service. Is that no longer the case?
> --
> Adam Williamson
> Fedora QA Community Monkey
> IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
> http://www.happyassassin.net
>
> --
> devel mailing list
> devel at lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel


More information about the devel mailing list