Cross s390x was always as unsupported as possible to avoid people migrating off.
Never seen it working, but let me try your case.
A little matrix:
Host/Guest->
v amd64 s390x ppc64el
amd64 Y N Y
s390x Y Y slow-Y
ppc64el slow-Y N Y
I'd think it is just not meant to fully work.
It is a qemu crash after all so I could take a look, but knowing some history
on how much good working s390x on x86 is "wanted" this is prio <low.
OTOH your Team has a set of real s390x KVM and z/VM systems, so for your
testing try to use some of those?
** Changed in: qemu (Ubuntu)
Status: New => Confirmed
** Changed in: qemu (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1712534
Title:
qemu-debootstrap second stage hangs indefinitely
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1712534/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
