Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.dist > #1055645

Bug#986741: Please enable CONFIG_IP_PNP_DHCP=y in cloud image

Cross-posted to 2 groups.

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

On Tue, Apr 13, 2021 at 11:36:11AM +0200, Bastian Blank wrote:
> > > Where was that discussed?
> > It was discussed in
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947759
> > , with responses from both Ben and Noah.
> 
> As this is incomplete at best, I intend to revert that change.
> 
> Otherwise it at least needs in addition:
> - hyperv pci support (for nvme),
> - hyperv block and
> - virtio-scsi.

This should probably be discussed in depth outside of this bug, but I do
not think this is the right approach.  The kernel config changes have
been in place for over a year, and were merged only after discussion
both on salsa and the BTS.  They accomplish the desired effect, which is
to allow the cloud kernel to boot without an initrd on common cloud
instance types (specifically AWS Nitro instance types).  While this is
not the default behavior for any of our cloud images, it is simple for
users to enable it on derivative images if they can benefit from the
reduced boot time.

If we want to support initrd-less booting on instances aside from Nitro
instance types, that's great, and we should consider doing that.  That
would be much more beneficial to our users than reverting the change.

> However this bug is about dhcp support.  If there is no network device
> support available, how does it do dhcp?

I'd also argue that NIC drivers (in particular ena.ko, used on Nitro
instances) should be left configured as modules, even if we do want to
support initrd-less booting.  AWS publishes an out-of-tree variant of
the ENA driver that may be ahead of what's in the stable kernel tree,
and some users may have a need to run that.

noah

Back to linux.debian.bugs.dist | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

Bug#986741: Please enable CONFIG_IP_PNP_DHCP=y in cloud image Josh Triplett <josh@joshtriplett.org> - 2021-04-10 23:20 +0200
  Bug#986741: Please enable CONFIG_IP_PNP_DHCP=y in cloud image Bastian Blank <waldi@debian.org> - 2021-04-10 23:30 +0200
    Bug#986741: Please enable CONFIG_IP_PNP_DHCP=y in cloud image Josh Triplett <josh@joshtriplett.org> - 2021-04-11 01:00 +0200
      Bug#986741: Please enable CONFIG_IP_PNP_DHCP=y in cloud image Ben Hutchings <ben@decadent.org.uk> - 2021-04-11 22:50 +0200
        Bug#986741: Please enable CONFIG_IP_PNP_DHCP=y in cloud image Josh Triplett <josh@joshtriplett.org> - 2021-04-12 03:50 +0200
          Bug#986741: Please enable CONFIG_IP_PNP_DHCP=y in cloud image Vincent Bernat <bernat@debian.org> - 2021-04-12 07:10 +0200
            Bug#986741: Please enable CONFIG_IP_PNP_DHCP=y in cloud image Josh Triplett <josh@joshtriplett.org> - 2021-04-12 07:10 +0200
          Bug#986741: Please enable CONFIG_IP_PNP_DHCP=y in cloud image Ben Hutchings <ben@decadent.org.uk> - 2021-04-12 23:30 +0200
            Bug#986741: Please enable CONFIG_IP_PNP_DHCP=y in cloud image Josh Triplett <josh@joshtriplett.org> - 2021-04-13 00:10 +0200
            Bug#986741: Please enable CONFIG_IP_PNP_DHCP=y in cloud image Bastian Blank <waldi@debian.org> - 2021-04-13 06:50 +0200
              Bug#986741: Please enable CONFIG_IP_PNP_DHCP=y in cloud image Josh Triplett <josh@joshtriplett.org> - 2021-04-13 07:40 +0200
                Bug#986741: Please enable CONFIG_IP_PNP_DHCP=y in cloud image Bastian Blank <waldi@debian.org> - 2021-04-13 11:40 +0200
                Bug#986741: Please enable CONFIG_IP_PNP_DHCP=y in cloud image Noah Meyerhans <noahm@debian.org> - 2021-04-13 21:20 +0200

csiph-web