Your message dated Thu, 17 Sep 2015 18:03:40 +0200
with message-id <[email protected]>
and subject line Re: Bug#799253: virtio ens3 network interface
has caused the Debian Bug report #799253,
regarding virtio ens3 network interface
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
799253: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799253
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Package: udev
Version: 226-2
Since I upgraded my KVM host the NIC (virtio) is called "ens3"
instead of "eth0". Looking at udev's changelog for 226-2 I had
the impression that this is not supposed to happen.
Regards
Harri
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQEcBAEBCAAGBQJV+oQRAAoJEAqeKp5m04HLGpUH/2oFkq5VSvyQ3z3BCJSr+ue4
cYC3HJMSWA3YbysbeP/vTLgmqoWqpI2B4oQITF3N1QgK0zyZYwT6hweSgl1288Qn
UBDC1OgZIfef/5/76SuwPU+VcYvedXmMSnWlowdkEZ0hTzhVQm+WQgIec5m5o8qZ
hbMMJawiWhel5DgzvK3p6/WaCRkjBXzvOPfYjp6XEoKxF5/cJovH7JoekmgYCqOS
UodTp6V0P0tkykAcmuO07IfffoirQ5AT7ONU76ZqJCQT0b3oE5f6PCEVgUDN/MtW
BtJRA4CaPDoOTjfI4naMh/ozH1yeWSWY21c9V44KCJryMfQp3hznC7PUsWWOvgc=
=vMjb
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
Hello Harald,
Harald Dunkel [2015-09-17 17:55 +0200]:
> Ah, I see. The udev.postinst script is hardware dependent and evaluated
> only once at upgrade time, breaking dpkg-reconfigure.
Right. This isn't "configuration", it's an one-time upgrade fix.
> The system in question is a bootable USB stick, supposed to run on all
> my hardware. I boot it in kvm only for maintenance (e.g. for the
> upgrade). This time the upgrade was done on a real laptop and booted
> in kvm later.
Ah! So at the time of the upgrade there just was no virtio interface,
I figure. In your manual there was, so the file is there now.
> Wouldn't it be more reasonable to add this virtio specific code
> unconditionally? There might be 2 or more real or virtual network
> interfaces at upgrade time, e.g. both e1000 and virtio. This
> shouldn't affect the outcome.
In such a scenario you can already not rely on stable interface names,
as they would change with the changing hardware (unless you have an
existing 70-persistent-net-names.rules from jessie, then it's okay
again).
So in this kind of image you need to be able to deal with different
network devices anyway, and you can't hardcode their names in
/etc/network/interfaces and the like.
> My suggestion would be to add a debconf dialog to enable/disable
> the "network renaming code" (independent from the network interface
> driver). Using dpkg-reconfigure we would have the usual config
> interface for this feature, giving everybody a way to choose and
> to change later.
Argh, no -- this isn't something an user ever has to think about.
> I don't see why this is a different case. Using kvm the e1000 is as
> virtual as the virtio interface. And its affected by the same broken
> network configuration after the udev upgrade.
It is a different case because the upstream change in question
specifically applies to virtio_net devices only.
Thanks for clarifying! Closing now, as I don't think there's anything
to actually fix here.
Martin
--
Martin Pitt | http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
signature.asc
Description: Digital signature
--- End Message ---
_______________________________________________
Pkg-systemd-maintainers mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
