[DO NOT MERGE] Diagnostic test for QEMU s390x netlink issue#506
Closed
[DO NOT MERGE] Diagnostic test for QEMU s390x netlink issue#506
Conversation
2584170 to
6999a69
Compare
Contributor
Author
|
packit copr-build |
2bd727d to
4b7db2c
Compare
4b7db2c to
541f8cc
Compare
46b2a4f to
d8e8b40
Compare
d8e8b40 to
d33b52a
Compare
ESoapW
added a commit
that referenced
this pull request
Apr 9, 2026
COPR lost native s390x builders around March 2026 and switched to QEMU user-mode emulation on x86_64. QEMU doesn't properly byte-swap netlink RTM_GETLINK rtattr structs when emulating big-endian s390x on a little-endian host, causing Go's net.InterfaceByName() to fail with 'parsenetlinkrouteattr: invalid argument'. We confirmed this is a QEMU bug, not a code issue: - Native s390x (Koji): all tests pass - Native x86_64: all tests pass - QEMU s390x (COPR): only netlink RTM_GETLINK tests fail - Diagnostic test (PR #506) shows RTM_GETADDR works, RTM_GETLINK doesn't, sysfs/procfs alternatives work fine A patch has been submitted to QEMU upstream. Removing s390x from COPR targets until the QEMU fix lands. This only affects CI testing, not the official Fedora package. Koji still builds s390x with real hardware and Fedora users are unaffected.
meta-codesync Bot
pushed a commit
that referenced
this pull request
Apr 9, 2026
Summary: COPR lost native s390x builders around March 2026 and switched to QEMU user-mode emulation on x86_64. QEMU doesn't properly byte-swap netlink RTM_GETLINK rtattr structs when emulating big-endian s390x on a little-endian host, causing Go's net.InterfaceByName() to fail with 'parsenetlinkrouteattr: invalid argument'. We confirmed this is a QEMU bug, not a code issue: - Native s390x (Koji): all tests pass - Native x86_64: all tests pass - QEMU s390x (COPR): only netlink RTM_GETLINK tests fail - Diagnostic test (PR #506) shows RTM_GETADDR works, RTM_GETLINK doesn't, sysfs/procfs alternatives work fine A patch has been submitted to QEMU upstream. Removing s390x from COPR targets until the QEMU fix lands. This only affects CI testing, not the official Fedora package. Koji still builds s390x with real hardware and Fedora users are unaffected. https://gitlab.com/qemu-project/qemu/-/work_items/2485#note_3236597357 Pull Request resolved: #508 Reviewed By: vvfedorenko Differential Revision: D100185224 Pulled By: ESoapW fbshipit-source-id: 9070472bd76975b7dbb94de3514ffa300ba19f50
Contributor
Author
|
Closing this PR. The diagnostic test served its purpose and we found the root cause. What we foundThe netdiag test helped us trace the issue to a one-character off-by-one bug in QEMU's Key evidence from the diagnostic
StatusThe bug has been in QEMU since 2016 (commit |
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
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.
DO NOT MERGE - diagnostic only
Adding a test package (netdiag/) to figure out exactly which network interface detection methods break under QEMU s390x emulation. We've been seeing parsenetlinkrouteattr: invalid argument on COPR s390x builds since they lost native builders around Mar 13.
This tests netlink, sysfs, procfs, and raw socket paths independently and prints a summary table. Expecting netlink methods to fail while sysfs/procfs alternatives work fine, which would confirm the issue is QEMU's incomplete byte-order translation of netlink rtattr structs.
Will close after reviewing COPR build logs.