https://bugzilla.suse.com/show_bug.cgi?id=1219180 https://bugzilla.suse.com/show_bug.cgi?id=1219180#c26 --- Comment #26 from Fabian Vogt <fvogt@suse.com> --- (In reply to Claudio Fontana from comment #25)
(In reply to Fabian Vogt from comment #24)
(In reply to Claudio Fontana from comment #23)
Be careful that specifying an exact cpu as you are doing here
-cpu cortex-a72
is going to be very dependent on the exact machine you are going to run on. The meaning of -cpu is different than on x86.
Not sure what you mean by that.
I mean that when using KVM, named cpu models are not really working for ARM.
See: https://qemu-project.gitlab.io/qemu/system/arm/cpu-features.html
Does -cpu host work too? Because if it doesn't that is something we really want to fix.
Without KVM there's no -cpu host:
Yes. What I am saying here is:
* when using KVM, do not use qemu-kvm. The proper way to use it is qemu-system-aarch64 -accel kvm .
Without kvm, you must specifiy some -cpu. The default cpu is cortex-a15 which does not have AArch64.
qemu-system-aarch64 -cpu host -M virt qemu-system-aarch64: unable to find CPU model 'host'
Again, that is the supported and recommended option to use for ARM AArch64, I shared the relevant links above.
On the original request, I don't see anything here to do.
We know that virtio-gpu-pci works, and we see it working both with KVM and TCG.
I continue to recommend to test on actual hardware with KVM, and not with TCG, because that is what is actually supported by us for customers running actual workloads.
I do not see anything to do here, can we close?
The bug report is about efifb not working with qemu-system-aarch64. -- You are receiving this mail because: You are on the CC list for the bug.