[Bug 857662] Re: Should xenbus_probe_frontend be built-in?
This bug was fixed in the package debian-installer - 20101020ubuntu77 --- debian-installer (20101020ubuntu77) precise; urgency=low * Bump powerpc netboot image size by a megabyte to allow for a slight kernel size increase. * Switch Xen images to the -virtual kernel flavour (LP: #857662). -- Colin WatsonSun, 20 Nov 2011 11:15:24 + ** Branch linked: lp:~ubuntu-core-dev/debian-installer/ubuntu ** Changed in: debian-installer (Ubuntu Precise) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/857662 Title: Should xenbus_probe_frontend be built-in? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/857662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 857662] Re: Should xenbus_probe_frontend be built-in?
This bug was fixed in the package hw-detect - 1.81ubuntu2.1 --- hw-detect (1.81ubuntu2.1) natty-proposed; urgency=low * Load xenbus_probe_frontend if we're running under the Xen hypervisor (LP: #857662). -- Colin WatsonFri, 23 Sep 2011 23:42:59 +0100 ** Changed in: hw-detect (Ubuntu Natty) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/857662 Title: Should xenbus_probe_frontend be built-in? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/857662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 857662] Re: Should xenbus_probe_frontend be built-in?
I've confirmed that this fixes network interface detection in a Xen installation with apt-setup/proposed=true, and that xenbus_probe_frontend is added to /etc/initramfs-tools/modules to ensure that things work properly after installation as well. Separately, I've confirmed that a non-Xen (in fact KVM) installation still works as normal, and doesn't have xenbus_probe_frontend loaded. Marking verification-done. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/857662 Title: Should xenbus_probe_frontend be built-in? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/857662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 857662] Re: Should xenbus_probe_frontend be built-in?
** Branch linked: lp:ubuntu/natty-proposed/hw-detect -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/857662 Title: Should xenbus_probe_frontend be built-in? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/857662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 857662] Re: Should xenbus_probe_frontend be built-in?
Hello Colin, or anyone else affected, Accepted hw-detect into natty-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance! ** Changed in: hw-detect (Ubuntu Natty) Status: Triaged => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/857662 Title: Should xenbus_probe_frontend be built-in? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/857662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 857662] Re: Should xenbus_probe_frontend be built-in?
** Branch linked: lp:ubuntu/hw-detect -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/857662 Title: Should xenbus_probe_frontend be built-in? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/857662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 857662] Re: Should xenbus_probe_frontend be built-in?
This bug was fixed in the package hw-detect - 1.81ubuntu3 --- hw-detect (1.81ubuntu3) oneiric; urgency=low * Load xenbus_probe_frontend if we're running under the Xen hypervisor (LP: #857662). -- Colin WatsonFri, 23 Sep 2011 23:21:48 +0100 ** Changed in: hw-detect (Ubuntu Oneiric) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/857662 Title: Should xenbus_probe_frontend be built-in? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/857662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 857662] Re: Should xenbus_probe_frontend be built-in?
** Description changed: + Stable update justification: + + Impact: When installing in a Xen domU, the installer fails to find any network interfaces. + Development branch: Fixed in hw-detect 1.81ubuntu3 by loading xenbus_probe_frontend if we seem to be running under the Xen hypervisor. (It should not be catastrophic if we load this even under other conditions, but it should be a bit more efficient this way.) + Patch: http://bazaar.launchpad.net/~ubuntu-core-dev/hw-detect/natty-proposed/revision/1466 + TEST CASE: Start up d-i in a Xen domU and run through to the point where it detects network interfaces. Without this patch, it should fail; with this patch, it should work. + Regression potential: I think the worst thing that can plausibly happen here is an error message via debconf if the module fails to load. The /sys/hypervisor/type and /sys/bus/xen checks around this code are mainly to defend against this possibility in non-Xen installations. + + Original report follows: + 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! ** Description changed: Stable update justification: Impact: When installing in a Xen domU, the installer fails to find any network interfaces. Development branch: Fixed in hw-detect 1.81ubuntu3 by loading xenbus_probe_frontend if we seem to be running under the Xen hypervisor. (It should not be catastrophic if we load this even under other conditions, but it should be a bit more efficient this way.) Patch: http://bazaar.launchpad.net/~ubuntu-core-dev/hw-detect/natty-proposed/revision/1466 - TEST CASE: Start up d-i in a Xen domU and run through to the point where it detects network interfaces. Without this patch, it should fail; with this patch, it should work. + TEST CASE: Start up d-i in a Xen domU and run through to the point where it detects network interfaces. Without this patch, it should fail; with this patch, it should work. Note that for testing you will need to use a kernel/initrd from natty-proposed (which I'll need to upload separately after this patch is accepted), and in production after this upload is validated you'll need to use a kernel/initrd from natty-updates. Regression potential: I think the worst thing that can plausibly happen here is an error message via debconf if the module fails to load. The /sys/hypervisor/type and /sys/bus/xen checks around this code are mainly to defend against this possibility in non-Xen installations. Original report follows: 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 / -gen
[Bug 857662] Re: Should xenbus_probe_frontend be built-in?
** Branch linked: lp:~ubuntu-core-dev/hw-detect/natty-proposed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/857662 Title: Should xenbus_probe_frontend be built-in? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/857662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 857662] Re: Should xenbus_probe_frontend be built-in?
** Branch linked: lp:~ubuntu-core-dev/hw-detect/ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/857662 Title: Should xenbus_probe_frontend be built-in? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/857662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 857662] Re: Should xenbus_probe_frontend be built-in?
** Changed in: linux (Ubuntu Natty) Status: Confirmed => Won't Fix ** Changed in: linux (Ubuntu Oneiric) Status: Confirmed => Won't Fix ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/857662 Title: Should xenbus_probe_frontend be built-in? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/857662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 857662] Re: Should xenbus_probe_frontend be built-in?
I would prefer to _not_ enable XEN_BLKDEV_FRONTEND for kernel flavours that are not intended for virtual environments. In order to do so you must first build in one of the front end device drivers such as CONFIG_XEN_BLKDEV_FRONTEND=y or CONFIG_XEN_NETDEV_FRONTEND=y. CONFIG_XEN_XENBUS_FRONTEND=y is not a separately selectable config option. Xen netboot images should be based on the -virtual flavour. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/857662 Title: Should xenbus_probe_frontend be built-in? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hw-detect/+bug/857662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 857662] Re: Should xenbus_probe_frontend be built-in?
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/857662 Title: Should xenbus_probe_frontend be built-in? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/857662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 857662] Re: Should xenbus_probe_frontend be built-in?
I mistakenly stated that we're using amd64/server - actually it's amd64/generic. I've edited the description to match reality. ** Changed in: hw-detect (Ubuntu Oneiric) Status: New => Triaged ** Changed in: hw-detect (Ubuntu Oneiric) Importance: Undecided => High ** Description changed: xenbus_probe_frontend is currently modular in several flavours, notably - in the i386/generic-pae and amd64/server flavours which we use to build + 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! ** Changed in: hw-detect (Ubuntu Natty) Status: New => Triaged ** Changed in: hw-detect (Ubuntu Natty) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/857662 Title: Should xenbus_probe_frontend be built-in? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hw-detect/+bug/857662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 857662] Re: Should xenbus_probe_frontend be built-in?
** Also affects: hw-detect (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/857662 Title: Should xenbus_probe_frontend be built-in? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hw-detect/+bug/857662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 857662] Re: Should xenbus_probe_frontend be built-in?
** Changed in: linux (Ubuntu Natty) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/857662 Title: Should xenbus_probe_frontend be built-in? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hw-detect/+bug/857662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 857662] Re: Should xenbus_probe_frontend be built-in?
** Also affects: linux (Ubuntu Natty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Oneiric) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/857662 Title: Should xenbus_probe_frontend be built-in? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hw-detect/+bug/857662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 857662] Re: Should xenbus_probe_frontend be built-in?
I don't believe log files are applicable to this, as a config change request with rationale. ** Description changed: xenbus_probe_frontend is currently modular in several flavours, notably in the i386/generic-pae and amd64/server 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 that isn't set - up such that we can build installer images from it, and I think I'm - happier building those directly from -generic-pae / -generic anyway. + 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! ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/857662 Title: Should xenbus_probe_frontend be built-in? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hw-detect/+bug/857662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 857662] Re: Should xenbus_probe_frontend be built-in?
** Changed in: linux (Ubuntu Natty) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux (Ubuntu Oneiric) Assignee: (unassigned) => Tim Gardner (timg-tpi) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/857662 Title: Should xenbus_probe_frontend be built-in? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hw-detect/+bug/857662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
