https://bugzilla.suse.com/show_bug.cgi?id=1219180 https://bugzilla.suse.com/show_bug.cgi?id=1219180#c30 --- Comment #30 from Fabian Vogt <fvogt@suse.com> --- (In reply to Claudio Fontana from comment #29)
(In reply to Fabian Vogt from comment #28)
(In reply to Dario Faggioli from comment #27)
(In reply to Fabian Vogt from comment #26)
(In reply to Claudio Fontana from comment #25)
I do not see anything to do here, can we close?
The bug report is about efifb not working with qemu-system-aarch64.
Right, so...
(In reply to Fabian Vogt from comment #7)
So a question for the virtualization team (qemu + ovmf): What's the right controller to use to get this to work? I guess ramfb might work but it's too limited to be usable in practice.
...I may still be missing something (not an ARM guy), but my impression is that it's either virtio-gpu-pci or nothing (and I'm talking about upstream).
There's also ramfb, but that's not really usable in practice.
And I still don't think I understand what you meant with this:
(In reply to Fabian Vogt from comment #7)
That explains it. Looking at the EDK II source, the driver for virtio-gpu-pci does not expose a linear framebuffer, only virtio-vga does (https://github.com/tianocore/edk2/blob/ 952b5cf94c8727b65e04d3d507c0134743be2a66/OvmfPkg/Virtio10Dxe/Virtio10. c#L1029). virtio-vga is not available in qemu-system-aarch64 though.
What is it that we're missing?
I guess either virtio-vga support for aarch64 or somehow support for a linear framebuffer with virtio-gpu-pci.
unfortunately I think if ramfb is not enough, we do not have any other option available for AArch64 at the moment.
Seems that this has been a missing feature on AArch64 for a while, see for example also this bug from 2019 that has a good description:
https://bugzilla.redhat.com/show_bug.cgi?id=1679680
I would have to close this as FEATURE for now, since making progress on this would require implementing a new feature for ARM upstream.
So where do we go from here? JIRA ticket? -- You are receiving this mail because: You are on the CC list for the bug.