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
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: linux-image-6.7-cloud-amd64: Built CONFIG_VIRTIO_BLK into kernel
- From: Paul Menzel <pmenzel@molgen.mpg.de>
- Date: Wed, 24 Jan 2024 18:13:05 +0100
- Message-id: <5d5626a3-66ce-44f4-a14f-b10fc7d5f7c6@molgen.mpg.de>
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 -nographicCurrently, 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
--- End Message ---
--- Begin Message ---
- To: Paul Menzel <pmenzel@molgen.mpg.de>, 1061445-done@bugs.debian.org
- Subject: Re: Bug#1061445: linux-image-6.7-cloud-amd64: Built CONFIG_VIRTIO_BLK into kernel
- From: Bastian Blank <waldi@debian.org>
- Date: Mon, 1 Apr 2024 22:29:46 +0200
- Message-id: <20240401202946.6ceo6ecebrrwzvh7@shell.thinkmo.de>
- Mail-followup-to: Bastian Blank <waldi@debian.org>, Paul Menzel <pmenzel@molgen.mpg.de>, 1061445-done@bugs.debian.org
- In-reply-to: <eafac79a-a07e-4ad9-acd4-d79205d01aa0@molgen.mpg.de>
- References: <5d5626a3-66ce-44f4-a14f-b10fc7d5f7c6@molgen.mpg.de> <20240124200108.4jpqovx7hh5dzvmw@shell.thinkmo.de> <5d5626a3-66ce-44f4-a14f-b10fc7d5f7c6@molgen.mpg.de> <eafac79a-a07e-4ad9-acd4-d79205d01aa0@molgen.mpg.de>
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. Bastian -- Schshschshchsch. -- The Gorn, "Arena", stardate 3046.2
--- End Message ---