Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #81652 > unrolled thread

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

Back to article view | Back to linux.debian.kernel

Contents

  Bug#1061445: linux-image-6.7-cloud-amd64: Built CONFIG_VIRTIO_BLK into kernel Paul Menzel <pmenzel@molgen.mpg.de> - 2024-01-24 18:30 +0100
    Processed: Re: Bug#1061445: linux-image-6.7-cloud-amd64: Built  CONFIG_VIRTIO_BLK into kernel "Debian Bug Tracking System" <owner@bugs.debian.org> - 2024-01-24 21:10 +0100
    Bug#1061445: linux-image-6.7-cloud-amd64: Built CONFIG_VIRTIO_BLK into kernel Bastian Blank <waldi@debian.org> - 2024-01-24 21:10 +0100
      Bug#1061445: linux-image-6.7-cloud-amd64: Built CONFIG_VIRTIO_BLK into kernel Paul Menzel <pmenzel@molgen.mpg.de> - 2024-01-26 14:00 +0100
    Bug#1061445: linux-image-6.7-cloud-amd64: Built CONFIG_VIRTIO_BLK into kernel Paul Menzel <pmenzel@molgen.mpg.de> - 2024-04-06 09:50 +0200
      Bug#1061445: linux-image-6.7-cloud-amd64: Built CONFIG_VIRTIO_BLK into kernel Paul Menzel <pmenzel@molgen.mpg.de> - 2024-04-06 09:52 +0200
      Bug#1061445: linux-image-6.7-cloud-amd64: Built CONFIG_VIRTIO_BLK into kernel Noah Meyerhans <noahm@debian.org> - 2024-04-18 02:10 +0200
    Bug#1061445: marked as done (linux-image-6.7-cloud-amd64: Built  CONFIG_VIRTIO_BLK into kernel) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2024-04-06 09:51 +0200

#81652 — Bug#1061445: linux-image-6.7-cloud-amd64: Built CONFIG_VIRTIO_BLK into kernel

Package: linux-image-6.7-cloud-amd64
Version: 6.6.13-1
Severity: normal


Dear Debian folks,


Trying to quickly start a VM, it’d be great to not use an initrd image, 
and also use the Virtio features, for example with the command below:

     qemu-system-x86_64 -M q35 -m 32G -enable-kvm -cpu host -smp cpus=32 
-device virtio-rng-pci -net nic,model=virtio-net-pci -net 
user,hostfwd=tcp::22225-:22 -drive 
if=virtio,file=/scratch/local2/debian-linux-build.img -vga none -nographic

Currently, that is not possible, as the driver is only available as 
module `virtio_blk.ko` (`CONFIG_VIRTIO_BLK=m`). It’d be great, if it 
could be built into the Linux kernel cloud image.


Kind regards,

Paul

[toc] | [next] | [standalone]

#81657 — Processed: Re: Bug#1061445: linux-image-6.7-cloud-amd64: Built CONFIG_VIRTIO_BLK into kernel

Processing control commands:

> tags -1 wontfix
Bug #1061445 [linux-image-6.7-cloud-amd64] linux-image-6.7-cloud-amd64: Built CONFIG_VIRTIO_BLK into kernel
Added tag(s) wontfix.

-- 
1061445: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061445
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#81658

Control: tags -1 wontfix

On Wed, Jan 24, 2024 at 06:13:05PM +0100, Paul Menzel wrote:
> Trying to quickly start a VM, it’d be great to not use an initrd image, and
> also use the Virtio features, for example with the command below:

Please use virtiofs in this case.

>     qemu-system-x86_64 -M q35 -m 32G -enable-kvm -cpu host -smp cpus=32
> -device virtio-rng-pci -net nic,model=virtio-net-pci -net
> user,hostfwd=tcp::22225-:22 -drive
> if=virtio,file=/scratch/local2/debian-linux-build.img -vga none -nographic

But you don't specify a kernel, so it boots fine using the initramfs
within.  So this already boots quite fine.

I don't see what exactly you mean will be easier.

Bastian

-- 
Those who hate and fight must stop themselves -- otherwise it is not stopped.
		-- Spock, "Day of the Dove", stardate unknown

[toc] | [prev] | [next] | [standalone]

#81666

Dear Bastian,


Thank you for your reply.

Am 24.01.24 um 21:01 schrieb Bastian Blank:
> Control: tags -1 wontfix
> 
> On Wed, Jan 24, 2024 at 06:13:05PM +0100, Paul Menzel wrote:
>> Trying to quickly start a VM, it’d be great to not use an initrd image, and
>> also use the Virtio features, for example with the command below:
> 
> Please use virtiofs in this case.
> 
>>      qemu-system-x86_64 -M q35 -m 32G -enable-kvm -cpu host -smp cpus=32 -device virtio-rng-pci -net nic,model=virtio-net-pci -net user,hostfwd=tcp::22225-:22 -drive if=virtio,file=/scratch/local2/debian-linux-build.img -vga none -nographic
> 
> But you don't specify a kernel, so it boots fine using the initramfs
> within.  So this already boots quite fine.

Yes, it boots fine, but slow.

> I don't see what exactly you mean will be easier.

With

     @@ -2113,7 +2115,7 @@
      CONFIG_ATA_OVER_ETH=m
      CONFIG_XEN_BLKDEV_FRONTEND=m
      CONFIG_XEN_BLKDEV_BACKEND=m
     -CONFIG_VIRTIO_BLK=m
     +CONFIG_VIRTIO_BLK=y
      CONFIG_BLK_DEV_RBD=m
      CONFIG_BLK_DEV_UBLK=m
      CONFIG_BLKDEV_UBLK_LEGACY_OPCODES=y

and

     $ 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.


Kind regards,

Paul


PS: I know, there are more things to speed up the boot time, but this 
change is quite easy.

[toc] | [prev] | [next] | [standalone]

#82143

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

[toc] | [prev] | [next] | [standalone]

#82171

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

[toc] | [prev] | [next] | [standalone]

#82267

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

[toc] | [prev] | [next] | [standalone]

#82168 — Bug#1061445: marked as done (linux-image-6.7-cloud-amd64: Built CONFIG_VIRTIO_BLK into kernel)

[Multipart message — attachments visible in raw view] — view raw

Your message dated Mon, 1 Apr 2024 22:29:46 +0200
with message-id <20240401202946.6ceo6ecebrrwzvh7@shell.thinkmo.de>
and subject line Re: Bug#1061445: linux-image-6.7-cloud-amd64: Built CONFIG_VIRTIO_BLK into kernel
has caused the Debian Bug report #1061445,
regarding linux-image-6.7-cloud-amd64: Built CONFIG_VIRTIO_BLK into kernel
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1061445: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061445
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web