Did some more testing and it doesn't seem to be a QEMU problem. I have an s390x VM and if I mount that image I can chroot into it just fine (after copying qemu-s390x-static).
Not sure what's going on. As a test, I copied /lib and /bin from the VM image into the chroot and after that I was able to chroot into the chroot dir just fine. Any ideas?
Btw, this process (using qemu-debootstrap) works just fine for building an arm64 chroot (on an amd64 host).
Did some more testing and it doesn't seem to be a QEMU problem. I have an s390x VM and if I mount that image I can chroot into it just fine (after copying qemu-s390x-static).
strace shows that chroot is hanging on a futex:
rt_sigprocmask( SIG_BLOCK, ~[RTMIN RT_1], ~[BUS KILL SEGV STOP], 8) = 0 SIG_SETMASK, ~[BUS KILL SEGV STOP], NULL, 8) = 0
getpid() = 19585
gettid() = 19585
tgkill(19585, 19585, SIGABRT) = 0
rt_sigprocmask(
--- SIGSEGV {si_signo=SIGSEGV, si_code=SI_KERNEL, si_addr=NULL} ---
futex(0x604eff00, FUTEX_WAIT_PRIVATE, 2, NULL
Not sure what's going on. As a test, I copied /lib and /bin from the VM image into the chroot and after that I was able to chroot into the chroot dir just fine. Any ideas?
Btw, this process (using qemu-debootstrap) works just fine for building an arm64 chroot (on an amd64 host).