feat(itf): add dual-QEMU ivshmem integration-test environment - #617
Merged
castler merged 2 commits intoJul 24, 2026
Merged
Conversation
Rahul-Sutariya
force-pushed
the
rasu_dual_qemu_intergation_test_plugin
branch
from
June 30, 2026 11:14
f56837b to
eedfda4
Compare
Rahul-Sutariya
force-pushed
the
rasu_dual_qemu_intergation_test_plugin
branch
4 times, most recently
from
July 13, 2026 07:14
5bd6beb to
38c934b
Compare
Rahul-Sutariya
marked this pull request as ready for review
July 13, 2026 10:00
Rahul-Sutariya
requested review from
LittleHuba,
bemerybmw,
castler,
crimson11,
hoe-jo and
limdor
as code owners
July 13, 2026 10:00
castler
reviewed
Jul 13, 2026
castler
left a comment
castler
left a comment
Contributor
There was a problem hiding this comment.
Let's first align on the test infrastructure - then we can check out the example :)
Comment on lines
+198
to
+201
| # Driving two real QNX guests under KVM has rare, environment-induced boot | ||
| # nondeterminism (e.g. a guest occasionally wedging during device bring-up). | ||
| # The fixtures already stagger boots and wait for stable SSH; mark the test | ||
| # flaky so bazel transparently retries such infrastructure hiccups. |
Contributor
There was a problem hiding this comment.
Ouch - is this possible to be fixed? Should we add a ticket with a todo?
Contributor
Author
There was a problem hiding this comment.
It's a KVM + QNX -kernel boot path timing issue — the second guest occasionally wedges during SMP AP startup when both initialize under the same KVM instance. The plugin already mitigates by booting VMs sequentially and using single-core guests, which makes it very rare but not fully eliminable from our side.
A proper fix would require either:
- QNX fixing the boot-path race in their -kernel loader (upstream QNX issue), or
- Using the -bios/UEFI boot path instead of -kernel (different QNX IFS packaging, not trivial).
Rahul-Sutariya
force-pushed
the
rasu_dual_qemu_intergation_test_plugin
branch
2 times, most recently
from
July 14, 2026 13:59
6c98422 to
01bea3d
Compare
castler
reviewed
Jul 15, 2026
Rahul-Sutariya
force-pushed
the
rasu_dual_qemu_intergation_test_plugin
branch
2 times, most recently
from
July 17, 2026 13:04
b783e72 to
535aa46
Compare
castler
reviewed
Jul 20, 2026
Rahul-Sutariya
force-pushed
the
rasu_dual_qemu_intergation_test_plugin
branch
from
July 21, 2026 06:38
535aa46 to
1b86c08
Compare
Member
|
@Rahul-Sutariya some checks are failing in your PR. Please adapt. |
Contributor
@anmittag as already stated in #617 (comment), this is right now blocked. |
Add a `dual_qemu` ITF/pytest plugin that boots two QNX VMs sharing one QEMU ivshmem-plain region, extending the upstream single-VM `qemu` plugin. - plugin: config.py, ivshmem_qemu.py, dual_qemu_process.py, __init__.py (target_a/target_b fixtures; sequential boot to avoid KVM race), BUILD, example config, README, example/run_example_manually.sh. - integration_testing.bzl: dual_qemu_integration_test macro (QNX-only, flaky). - example: offset_list.h + simple_ivshmem.cpp map the ivshmem BAR via pci-server and exchange a self-relative offset-pointer list, proving cross-VM pointer resolution; simple_ivshmem_test.py verifies both VMs.
note: Cross-VM shared memory forces the region onto the ivshmem PCI BAR (device/SHMCTL_PHYS memory), but the production lib-memory ControlBlock puts a process-shared pthread_mutex there and locks it during init. QNX refuses to operate a process-shared mutex on device-mapped BAR memory (returns EINVAL even with write-back caching), so the producer aborts — making the umbrella score::memory::shared unusable over ivshmem, unlike the mutex-free demo.
Rahul-Sutariya
force-pushed
the
rasu_dual_qemu_intergation_test_plugin
branch
from
July 24, 2026 04:34
1b86c08 to
ac16d8b
Compare
castler
approved these changes
Jul 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add a
dual_qemuITF/pytest plugin that boots two QNX VMs sharing one QEMU ivshmem-plain region, extending the upstream single-VMqemuplugin.