[FS#3101] Kernel in armvirt images missing virtio drivers and UEFI support

OpenWrt Bugs openwrt-bugs at lists.openwrt.org
Thu Dec 17 03:58:13 EST 2020


THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#3101 - Kernel in armvirt images missing virtio drivers and UEFI support
User who did this - Yousong Zhou (yousong)

----------
The virtio drivers part should not be an issue.  I remember making virtio a priority when introducing armvirt target into OpenWrt.

```
➜  ~/git-repo/openwrt/openwrt git:(master) grep -i virtio target/linux/armvirt/config-5.4
CONFIG_BLK_MQ_VIRTIO=y
CONFIG_NET_9P_VIRTIO=y
CONFIG_SCSI_VIRTIO=y
CONFIG_VIRTIO=y
CONFIG_VIRTIO_BALLOON=y
CONFIG_VIRTIO_BLK=y
CONFIG_VIRTIO_CONSOLE=y
CONFIG_VIRTIO_MMIO=y
# CONFIG_VIRTIO_MMIO_CMDLINE_DEVICES is not set
CONFIG_VIRTIO_NET=y
CONFIG_VIRTIO_PCI=y
CONFIG_VIRTIO_PCI_LEGACY=y
```

We use armvirt mainly for dev/debug purposes.  Previously we had a target named realview for this purpose and removed it when armvirt was in place.

At the moment we have ./script/qemustart booting from the standalone initramfs kernel image.  The rootfs.ext4.img contains only rootfs only, no grub, no efi/ovmf etc.  Patches are welcome ;)
----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=3101#comment9175

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.



More information about the openwrt-bugs mailing list