[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1295ed070903120044s63b4da71i68add51703952d0f@mail.gmail.com>
Date: Thu, 12 Mar 2009 09:44:44 +0200
From: Pantelis Koukousoulas <pktoss@...il.com>
To: Rusty Russell <rusty@...tcorp.com.au>, netdev@...r.kernel.org
Subject: Re: [PATCH] Make virtio_net support carrier detection
On Thu, Mar 12, 2009 at 9:29 AM, Rusty Russell <rusty@...tcorp.com.au> wrote:
> On Wednesday 11 March 2009 22:27:22 Pantelis Koukousoulas wrote:
>> For now the semantics are simple: There is always carrier.
>>
>> This allows a seamless experience with e.g., qemu/kvm
>> where NetworkManager just configures and sets up
>> everything automagically.
>
> So, NetworkManager ignores the device because it doesn't support
> carrier detection?
It doesn't ignore it, it just doesn't enable it by default, like it does for
those that do report carrier.
But the user experience is that on real hardware you just boot a livecd
and see your network "just working" (and the familiar icon with the 2
computers indicating that), while under e.g., KVM/virtio you get
non-working network / an icon with a red X and you have to
figure out to left click on it and select eth0 to get things to work.
Some newer versions of NetworkManager seem to assume that
if no carrier detection is supported then carrier is on by default
so it should work for those, but that assumption seems like
a worse hack than this patch :)
(And in any case this patch helps all those who don't run
the latest unstable branch of their distro, while causing
no harm as far as I can see)
Pantelis
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists