Skip to content

Naming conflict when booting with multiple virtio-net NICs #34082

@msekletar

Description

@msekletar

systemd version the issue has been seen with

256

Used distribution

CentOS Stream 10

Linux kernel version used

6.10.0-rc4

CPU architectures issue was seen on

x86_64

Component

systemd-udevd

Expected behaviour you didn't see

Multiple virtio-net NICs should use udev's stable network interface names and no naming conflicts should occur.

Unexpected behaviour you saw

However, as soon as I add second virtio-net NIC I am running into naming conflict (because both interfaces try to claim ens0 name) and one interface ends up with eth0 name. This is most likely caused by recent change 0a4ecc5.

Steps to reproduce the problem

  1. Boot latest CentOS Stream 10 with systemd-256-12
  2. Verify that single virtio NIC has ens0 interface name
  3. Shutdown the VM
  4. Add another virtio-net NIC
  5. Boot

Additional program output to the terminal or log subsystem illustrating the issue

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions