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

    From Noah Meyerhans@21:1/5 to Paul Menzel on Thu Apr 18 02:10:01 2024
    XPost: linux.debian.kernel

    On Wed, Apr 03, 2024 at 06:26:46PM +0200, Paul Menzel wrote:
    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?

    The cloud kernel generally targets VM guests on the Microsoft Azure and
    Amazon EC2 cloud environments, neither of which benefit from VIRTIO_BLK
    driver being statically linked as you describe. I think that's the
    primary reason for reluctance to make your requested change.

    For background, the Azure and AWS clouds present well-defined device
    models, making it straightforward for us to construct targeted kernel
    configs for them.

    noah

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