kernel-packages team mailing list archive

[Dimitri John Ledkov <launchpad@xxxxxxxxxxxx>]

Public bug reported:

If VIRTIO_BLK and VIRTIO_NET become =m, instead of current =y the
following should happen:

VIRTIO_NET should be in the nic-modules udeb, and seeded into the d-i
builds.

VIRTIO_BLK can stay in block-modules-udeb, and in general is not needed
in the d-i build, as it can be fetched over the VIRTIO_NET provided
network.

VIRTIO_BLK needs to be available (e.g. server udebs pool, for offline
s390x installations)


on the kernel side

virtio-blk and virtio-nic most certainly need to be the in the "main"
package of a flavor, and not in -extra.

** Affects: debian-installer (Ubuntu)
     Importance: Undecided
         Status: New

** Affects: linux (Ubuntu)
     Importance: Undecided
         Status: New

** Also affects: debian-installer (Ubuntu)
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1533382

Title:
  A note on virtio blk and net modules

Status in debian-installer package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  If VIRTIO_BLK and VIRTIO_NET become =m, instead of current =y the
  following should happen:

  VIRTIO_NET should be in the nic-modules udeb, and seeded into the d-i
  builds.

  VIRTIO_BLK can stay in block-modules-udeb, and in general is not
  needed in the d-i build, as it can be fetched over the VIRTIO_NET
  provided network.

  VIRTIO_BLK needs to be available (e.g. server udebs pool, for offline
  s390x installations)

  
  on the kernel side

  virtio-blk and virtio-nic most certainly need to be the in the "main"
  package of a flavor, and not in -extra.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1533382/+subscriptions