On Oct 22 26, Cornelia Huck wrote: > What would make the most sense logically to me is to use > qemu-system-aarch64 to launch an aarch64 machine and qemu-system-s390x > to launch an s390x machine (at least from an user perspective.) That > said, I haven't looked at this series yet, but it does sound like a good > idea in general regardless of how we plan to launch different arch guests.
Just to clarify -- nobody has any intention of using anything other than qemu-system-aarch64 to start aarch64 guests, especially not qemu-system-s390x. What we are doing for arm64-on-s390 KVM is enable KVM accel for qemu-system-aarch64 on s390x hosts, alongside the KVM accel for qemu-system-s390x. that being said, if it were ever the case that qemu-system-s390x and qemu-system-aarch64 were the same binary (which is what I understand qemu is moving towards) then this would require that single binary to understand both s390x and aarch64 flavours of KVM, warts and all. There is another technical challenge in all of this, which is how the qemu build can consume the arm64 KVM uapi when built on and for an s390x host. I'm hoping that this will also be a lot easier to do if the surface of the KVM architecture details is contained behind a KVMCpuOps structure. Best, -A
