Re: [PATCH] build: prefer sigaltstack over ucontext on Linux

[Fabiano Rosas <farosas@suse.de>]

(tried to stitch the thread back together)

Elisey Konstantinov <elisey.konstantinov@gmail.com> writes:

> Fabiano Rosas <farosas@suse.de> writes:
>
>> Elisey Konstantinov <elisey.konstantinov@gmail.com> writes:
>>
>>> Oh, thanks for the feedback, however, could you please describe the environment you’re using?
>>
>> x86_64 host running Linux kernel 6.4.0. QEMU configured with:
>>
>> ../configure
>> --target-list=x86_64-softmmu,aarch64-softmmu,ppc64-softmmu,ppc-softmmu,s390x-softmmu,riscv64-softmmu,aarch64-linux-user,mips64-softmmu
>> --disable-plugins --enable-modules --enable-werror --enable-debug --disable-docs
>>
>> QEMU cmdline:
>>
>> qemu-system-ppc -machine mac99 -boot d -d guest_errors,unimp,cpu_reset
>> -cdrom osx_100_4k78_install.iso -prom-env "boot-args=-v"
>>
>> Connecting via VNC shows the machine runs up to and past the point shown
>> in the screenshot posted as the working example in:
>> https://gitlab.com/qemu-project/qemu/-/work_items/3276#note_3105980116
>>
>> Clicking around, the VM seems functional.
>
> Yeah, this sounds weird, could you please test on the old distribution,
> like Debian 12?See three of my latest messages in the main thread for
> more information

Sorry, I don't have the means to test this on Debian 12. It's not clear
from the thread, have you reproduced the issue using the HEAD of QEMU's
master branch? If so, then I think the best we could do is go back to
the original issue[1] on Gitlab and continue the investigation.

From the information you posted there, the execution should have gotten
past the happy mac screen. You could try running with -prom-env
"boot-args=-v" as I did above and see if it gives you any logging past
that screen. Post a screenshot of your VNC session showing those logs.

1- https://gitlab.com/qemu-project/qemu/-/work_items/3276