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.
