Repository navigation
Prefer using qemu system instead of qemu user #829
Description
s390x-unknown-linux-gnu and sparc64-unknown-linux-gnu uses qemu system to run the tests. It seems more correct in terms of emulation to use full system emulation. So we may try to update the other targets to use system emulation.
Activity
kristate commentedon Feb 26, 2018
Circling back, what is the status?
alexcrichton commentedon Feb 26, 2018
This was added for s390x and sparc64, but other platforms aren't using this yet. Changing the others, though, to using this would be more than welcome!
gnzlbg commentedon Nov 22, 2018
Status update: @malbarbo added qemu-system support to cross - most targets can choose between using
qemu-userorqemu-systemwhen running tests.tgross35 commentedon Aug 12, 2024
Something to note here is that
qemu-systemseems to be significantly slower thanqemu-user. Most tests complete in ~3 minutes, but s390x is about 12m and sparc64 is about 25.Checking tier 1 and maybe some of the more popular tier 2 targets with
qemu-systemmay be worth it for accuracy and CI could be adjusted so they don't block anything (currently docker tier 2 blocks the linux build channels), but it doesn't seem like it would be worth the slowdown for many more targets.tgross35 commentedon Jun 24, 2026
There hasn't really been a push to do this ever and I can't think of any issues that it would solve, so I opted to close this. It might be better to give us some more control over the kernel we're testing against but in practice, that doesn't seem worth the added CI complexity and time.
ci: Test s390x with qemu-user rather than qemu-system
ci: Test s390x with qemu-user rather than qemu-system
ci: Test s390x with qemu-user rather than qemu-system