Skip to content

Conversation

nicholasbishop
Copy link
Member

This was accidentally dropped when porting build.py to Rust. On AArch64,
check that qemu exits 0, and on x86_64, expect an exit code of 3.

@nicholasbishop
Copy link
Member Author

nicholasbishop commented Feb 6, 2022

Hmm, maybe a repro of #259?

Error: qemu was terminated by a signal: ExitStatus(unix_wait_status(139))

139 == 0x8b, which I believe means a segfault occurred (signal 11 == 0xb, with 0x80 indicating a core dump was produced).

I downloaded the ubuntu-20.04 aarch64 ovmf files from https://packages.ubuntu.com/focal/all/qemu-efi-aarch64/download and tested locally, no crash. So most likely this is something that has been fixed in qemu sometime between 4.2 and 6.1.

@nicholasbishop
Copy link
Member Author

Added in a backports PPA (https://launchpad.net/%7Ecanonical-server/+archive/ubuntu/server-backports/) to get a newer version of qemu, that fixed it.

@GabrielMajeri
Copy link
Collaborator

Ah, I tried using GH's built-in rebase but CI is now failing. I think we need some changes now that we also have IA32 as an enum option for arch.

This was accidentally dropped when porting build.py to Rust. On AArch64,
check that qemu exits 0, and on x86_64, expect an exit code of 3.
@GabrielMajeri GabrielMajeri merged commit eced5be into rust-osdev:main Feb 7, 2022
@nicholasbishop nicholasbishop deleted the bishop-fix-exit-check branch February 15, 2022 19:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants