cool.
Rocky uses dracut with -H switch by default ("host only" drivers),
Ubuntu apparently doesn't although I remember at some point there was a
thing about optimizing it as well, perhaps it's just an option.
It can be worked around, but as I said, better to keep it "lean and
mean" and just add whatever extras in dracut.conf and re-run dracut.
On 2024-12-09 10:42, Muhammad Hanis Irfan Mohd Zaid wrote:
I've posted almost the same question on Rocky Linux forum here:
https://forums.rockylinux.org/t/rocky-linux-9-5-vm-with-virtio-not-booting-up/16773
Just to squeeze the tiny performance improvement, I will use
virtio_blk but still install virtio_scsi driver for compatibility.
Heard that Ubuntu might use Dracut to build initramfs images. I assume
a later version of Ubuntu might have this same issue.
On Mon, 9 Dec 2024 at 17:46, Nux <n...@li.nux.ro> wrote:
virtio-scsi is pretty good in most cases, even recommended in some
situations, as it's a proper SCSI implementation, so there shouldn't
be
major issues there.
virtio-blk is generally faster, but you probably won't see the
benefits
in day to day ops unless you're doing hard core stuff.
Problem with Rocky is it will only keep the install host drivers in
the
ramdisk. You can add more in /etc/dracut.conf.d/virtio.conf eg:
add_drivers+=" virtio_blk "
On 2024-12-08 10:19, Muhammad Hanis Irfan Mohd Zaid wrote:
I've been testing to create a template for Rocky Linux 9.5 and
Ubuntu
24.04.1. My process of creating the templates is creating them on
VirtualBox Version 7.1.0, select virtio-scsi for storage
controller and
virtio-net for the network adapter. After that, I convert the VDI
image
to
QCOW2 image using qemu-img. When trying to use the template on
CloudStack
and selecting virtio rootDiskController for both Rocky and Ubuntu,
only
Ubuntu is able to boot successfully while Rocky stucks at the
dracut
shell.
Changing the rootDiskController to scsi for Rocky fixes this
issue.
Further investigation found that selecting virtio as
rootDiskController,
the driver loaded is virtio_blk meanwhile selecting scsi as
rootDiskController, the driver loaded is virtio_scsi.
virtio as rootDiskController on Ubuntu:
https://imgur.com/a/liM4cet
scsi as rootDiskController on Rocky: https://imgur.com/a/K0JnVBw
I don't know in-depth about all this things but after reading this
article
looks like it should be okay to use virtio_scsi in most case:
https://mpolednik.github.io/2017/01/23/virtio-blk-vs-virtio-scsi/
What type of rootDiskController did you use? Happy to hear your
thoughts on
this.
