[Bug 857662] Re: Should xenbus_probe_frontend be built-in?

[Colin Watson]

OK.  So in that case you can close the linux task - thanks for the
explanation, and I will deal with this in the installer.

I don't want to change the flavour that the Xen netboot images are based
on a few weeks before release, especially since I can't test that
myself; I will change that for P.  I'll work around this in hw-detect
for Natty/Oneiric, and recommend that people install the -virtual kernel
flavour in the target so that we don't need to change normal userspace.

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

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

** Also affects: hw-detect (Ubuntu P-series)
   Importance: Undecided
       Status: New

** Also affects: linux (Ubuntu P-series)
   Importance: Undecided
       Status: New

** Changed in: linux (Ubuntu P-series)
       Status: New => Invalid

** Changed in: hw-detect (Ubuntu P-series)
       Status: New => Invalid

** Changed in: debian-installer (Ubuntu Natty)
       Status: New => Won't Fix

** Changed in: debian-installer (Ubuntu Oneiric)
       Status: New => Won't Fix

** Changed in: debian-installer (Ubuntu)
   Importance: Undecided => Medium

** Changed in: debian-installer (Ubuntu)
       Status: New => Triaged

** Changed in: debian-installer (Ubuntu P-series)
   Importance: Undecided => Medium

** Changed in: debian-installer (Ubuntu P-series)
       Status: New => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to hw-detect in Ubuntu.
https://bugs.launchpad.net/bugs/857662

Title:
  Should xenbus_probe_frontend be built-in?

Status in “debian-installer” package in Ubuntu:
  Triaged
Status in “hw-detect” package in Ubuntu:
  Triaged
Status in “linux” package in Ubuntu:
  Confirmed
Status in “debian-installer” source package in Natty:
  Won't Fix
Status in “hw-detect” source package in Natty:
  Triaged
Status in “linux” source package in Natty:
  Confirmed
Status in “debian-installer” source package in Oneiric:
  Won't Fix
Status in “hw-detect” source package in Oneiric:
  Triaged
Status in “linux” source package in Oneiric:
  Confirmed
Status in “debian-installer” source package in p-series:
  Triaged
Status in “hw-detect” source package in p-series:
  Invalid
Status in “linux” source package in p-series:
  Invalid

Bug description:
  xenbus_probe_frontend is currently modular in several flavours,
  notably in the i386/generic-pae and amd64/generic flavours which we
  use to build d-i Xen netboot images.  The purpose of
  xenbus_probe_frontend appears to be to connect to the Xen bus and then
  emit uevents for any devices it finds there.  Once it's loaded,
  autoloading for such things as xen-netfront works fine, allowing the
  guest to find its network interface.  I believe that xen-blkfront
  works in a similar way.

  However, with xenbus_probe_frontend modular, the early stages of the
  installer plus the early stages of normal system boot need to load
  xenbus_probe_frontend in order to find block and network devices.  If
  we're going to do this, it seems as though we might as well just build
  xenbus_probe_frontend into the kernel.  It seems to me that it should
  be pretty harmless on non-Xen systems, although of course somebody
  knowledgeable should verify that.

  Right now, it's built in for the -virtual flavours, but we aren't
  currently building installer images from that, and I think I'm happier
  building them directly from -generic-pae / -generic anyway.

  This is true in both Natty and Oneiric.  If you can't do this for
  Oneiric and/or are unwilling to do this in a stable update for Natty,
  then please let me know so that I can add a workaround to the
  installer in time.  Thanks!

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