As my other repro-code didn't trigger the issue I looked at qemu again and found that before the failing ioctl->scv call there are plenty other even some very similar (same?) calls that work just fine.
I wonder if on guest setup qemu (or e.g. the rom we load) might set some arch-bits or such which then breaks the next "scv 0" call. I attached the full ioctl log here. ** Attachment added: "ioctl log of qemu until the crash happens" https://bugs.launchpad.net/qemu/+bug/1920784/+attachment/5480011/+files/qemu-ioctls-util-crash.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920784 Title: qemu-system-ppc64le fails with kvm acceleration To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1920784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
