Control: reassign -1 udev/228-2 On 29 December 2015 at 13:08, Neil Williams <[email protected]> wrote: > Package: systemd > Version: 228-2+b1 > Severity: normal
This is udev, not systemd. > > This particular issue arises from this documentation: > http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/ > > It may also be related to #789439. > > I adapted vmdebootstrap to mask udev's rule file, as advised in the first of > the > documented methods of disabling this support. > "You disable the assignment of fixed names, so that the unpredictable kernel > names are used again. For this, simply mask udev's rule file for the default > policy: ln -s /dev/null /etc/udev/rules.d/80-net-setup-link.rules" > > http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/tree/vmdebootstrap/base.py?id=vmdebootstrap-1.3#n208 > > That worked during testing. Since releasing that change, systemd has > apparently dropped > support for this method and a VM built with this change no longer raises a > network interface > using DHCP. > > $ sudo vmdebootstrap --image=sid.img --distribution=unstable --grub > --enable-dhcp --verbose Do you have a log that you can share? Also, is the interface not named as expected, or is the interface named correctly but not brought up? There were recent changes in the ifupdown/systemd integration, that may be related. > QEMU is capable of booting images with different network configurations, so > it is not > simple for vmdebootstrap to know in advance what names systemd will generate > - hence > the change to assert the previous behaviour. vmdebootstrap is also used to > generate > images for use on ARM dev boards like beaglebone-black and cubietruck, so > having a > consistent interface that can be configured to use DHCP at boot is important. Do the systems booted by vmdebootstrap use systemd? If so, it may be simpler to use systemd-networkd: echo <<EOF > /etc/systemd/network/99-dhcp-all.network [Match] Name=* [Network] DHCP=yes EOF -- Saludos, Felipe Sateler
