1. Forum
  2. Usenet
  3. LINUX.DEBIAN.KERNEL

  • Bug#1061445: linux-image-6.7-cloud-amd64: Built CONFIG_VIRTIO_BLK into

    From Paul Menzel@21:1/5 to All on Sat Apr 6 09:50:03 2024
    XPost: linux.debian.bugs.dist

    Dear Bastian,


    Am 01.04.24 um 22:29 schrieb Bastian Blank:
    On Fri, Jan 26, 2024 at 01:44:44PM +0100, Paul Menzel wrote:
    $ grep UUID /etc/default/grub
    # Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
    GRUB_DISABLE_LINUX_UUID=true

    I am now able to boot the VM image without an initrd, editing
    `/boot/grub/grub.cfg`, which saves a little time, as the initrd does not
    need to be loaded by GRUB and later dealt with (unpack/run) by the Linux
    kernel.

    Sou you already have all the infrastructure to create initrd. Please
    use virtiofs for this case.

    Sorry, I have the feeling we talk past each other. I do not want to
    create an initrd. I want to boot *without* an initrd, and the only
    missing piece is building VIRTIO_BLK into the Linux kernel.

    Ubuntu also builds this into their “kvm” flavour [1].

    If you think, that is unnecessary, could you please elaborate, how I
    would achieve the goal with virtiofs?


    Kind regards,

    Paul


    [1]: https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/tree/debian.master/config/annotations#n611

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Paul Menzel@21:1/5 to All on Sat Apr 6 09:52:03 2024
    XPost: linux.debian.bugs.dist

    Dear Bastian,


    Am 03.04.24 um 18:26 schrieb Paul Menzel:

    Am 01.04.24 um 22:29 schrieb Bastian Blank:
    On Fri, Jan 26, 2024 at 01:44:44PM +0100, Paul Menzel wrote:
         $ grep UUID /etc/default/grub
         # Uncomment if you don't want GRUB to pass "root=UUID=xxx"
    parameter to Linux
         GRUB_DISABLE_LINUX_UUID=true

    I am now able to boot the VM image without an initrd, editing
    `/boot/grub/grub.cfg`, which saves a little time, as the initrd does not >>> need to be loaded by GRUB and later dealt with (unpack/run) by the Linux >>> kernel.

    Sou you already have all the infrastructure to create initrd.  Please
    use virtiofs for this case.

    Sorry, I have the feeling we talk past each other. I do not want to
    create an initrd. I want to boot *without* an initrd, and the only
    missing piece is building VIRTIO_BLK into the Linux kernel.

    Ubuntu also builds this into their “kvm” flavour [1].

    I referenced the incorrect repository. With the help of #ubuntu-kernel@irc.libera.chat, from `annotations` in *linux-kvm*
    archive [2]:

    CONFIG_VIRTIO_BLK policy<{'amd64': 'y'}>

    If you think, that is unnecessary, could you please elaborate, how I
    would achieve the goal with virtiofs?


    Kind regards,

    Paul


    [1]: https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/tree/debian.master/config/annotations#n611
    [2]: https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-kvm/+git/jammy/tree/debian.kvm/config/annotations?h=master-next#n476

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)