Yep done that and virtio_scsi did work. I've now loaded the virtio_blk
drivers to Rocky Linux and it can boot properly.
On Mon, 9 Dec 2024 at 18:51, Wei ZHOU wrote:
> Hi,
>
> Can you update the OS type of template (for new vm) or Stopped vm to "Other
> PV (Virtio-SCSI)" and retry ?
>
> -Wei
>
>
Hi,
Can you update the OS type of template (for new vm) or Stopped vm to "Other
PV (Virtio-SCSI)" and retry ?
-Wei
On Mon, Dec 9, 2024 at 11:42 AM Muhammad Hanis Irfan Mohd Zaid <
hanisirfan.w...@gmail.com> wrote:
> I've posted almost the same question on Rocky Linux forum here:
>
> https://f
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
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 mi
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
