New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Predictable interface names changed in Qemu VMs #29197

Closed
fpletz opened this Issue Sep 10, 2017 · 4 comments

Comments

Projects
4 participants
@fpletz
Member

fpletz commented Sep 10, 2017

On different machines with different Qemu-based virtualizations (libvirt from nixpkgs, $cloudhosters), the network interfaces namens changed from 17.03 to 17.09. Presumably this has to do with a systemd upgrade. It's due to a kernel config change, see #29197 (comment).

For example: enp0s3 becomes ens3.

This breaks existing networking configs and renders the machine unreachable via the network if a static configuration is used or dhcpcd is configured to run on specific interfaces.

This either needs to be fixed before the release (use old naming by patching system or similar) or we need a big fat warning in the release notes.

@fpletz fpletz added this to the 17.09 milestone Sep 10, 2017

@fpletz fpletz added this to Already being worked on in Blocking Issues 17.09 Sep 10, 2017

@fpletz fpletz self-assigned this Sep 10, 2017

@fadenb

This comment has been minimized.

Show comment
Hide comment
@fadenb

fadenb Sep 10, 2017

Contributor

Do interface names starting with "enp" still exist with the newer systemd?
If not we could (in addition to the big fat warning) implement an assertion stopping users from bricking their systems (we all know that not every one studies the release notes as carefully as they should ;) )

Contributor

fadenb commented Sep 10, 2017

Do interface names starting with "enp" still exist with the newer systemd?
If not we could (in addition to the big fat warning) implement an assertion stopping users from bricking their systems (we all know that not every one studies the release notes as carefully as they should ;) )

@dezgeg

This comment has been minimized.

Show comment
Hide comment
@dezgeg

dezgeg Sep 14, 2017

Contributor

enp* still exist. I think the change is not in systemd but rather in the kernel / firmware presenting some additional information of the device that systemd now prefers. (Given that https://github.com/systemd/systemd/blob/master/src/udev/udev-builtin-net_id.c hasn't seen any major changes).

Contributor

dezgeg commented Sep 14, 2017

enp* still exist. I think the change is not in systemd but rather in the kernel / firmware presenting some additional information of the device that systemd now prefers. (Given that https://github.com/systemd/systemd/blob/master/src/udev/udev-builtin-net_id.c hasn't seen any major changes).

@groxxda

This comment has been minimized.

Show comment
Hide comment
@groxxda

groxxda Sep 19, 2017

Contributor

Probably caused by 5ac0026

According to https://github.com/systemd/systemd/blob/master/src/udev/udev-builtin-net_id.c#L41-L42 the naming is based on hotplug slot index number.

Contributor

groxxda commented Sep 19, 2017

Probably caused by 5ac0026

According to https://github.com/systemd/systemd/blob/master/src/udev/udev-builtin-net_id.c#L41-L42 the naming is based on hotplug slot index number.

@fpletz

This comment has been minimized.

Show comment
Hide comment
@fpletz

fpletz Sep 28, 2017

Member

It seems only QEMU is affected. The first interface in VirtualBox VMs is still enp0s3.

Member

fpletz commented Sep 28, 2017

It seems only QEMU is affected. The first interface in VirtualBox VMs is still enp0s3.

fpletz added a commit that referenced this issue Sep 28, 2017

@fpletz fpletz closed this in 49f175c Sep 28, 2017

@fpletz fpletz moved this from Already being worked on to Done in Blocking Issues 17.09 Sep 28, 2017

csingley added a commit to csingley/nixpkgs that referenced this issue Oct 29, 2017

InfernalKnight added a commit to InfernalKnight/nixpkgs that referenced this issue Nov 13, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment