TEST-36-NUMAPOLICY fails with qemu 5.2
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
systemd |
Unknown
|
Unknown
|
|||
qemu (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
systemd (Ubuntu) |
Fix Released
|
High
|
Balint Reczey |
Bug Description
Hi,
this test now fails as seen on ppc here
https:/
+ /bin/qemu-
E: QEMU failed with exit code 1
qemu-system-ppc64: total memory for NUMA nodes (0x0) should equal RAM size (0x20000000)
Reproducible in LP infra with systemd 246.6-5ubuntu1 and qemu 5.2
On other architectures this test is just skipped and ppc happened to complete
faster so I saw it earlier.
The same happens on amd64
+ /bin/qemu-
qemu-system-x86_64: total memory for NUMA nodes (0x0) should equal RAM size (0x20000000)
E: QEMU failed with exit code 1
Isolated this to a test without systemd:
$ apt install linux-image-generic qemu-system-x86
$ /bin/qemu-
Upgrading to 5.2 makes this:
$ /bin/qemu-
qemu-system-x86_64: total memory for NUMA nodes (0x0) should equal RAM size (0x20000000)
The numa spec is indeed a bit short
-numa node,nodeid=0
If I change this to
-numa node,mem=
It would work, but that kind of specification is forbidden >=5.1
Parameter -numa node,mem is not supported by this machine type
Use -numa node,memdev instead
You'd need also something like -M pc-i440fx-5.0 which isn't anything the test
wants to set in stone I guess.
Instead using memdev works:
-object memory-
This works fine and is in qemu since quite some time.
Properly documented since 2.12 but actually available since 2.1 (2014)
The argument for this test is in test/TEST-
QEMU_
Fixing that to a new form should help.
Related branches
- Ubuntu Release Team: Pending requested
-
Diff: 22 lines (+4/-0)1 file modifiedubuntu-release (+4/-0)
Changed in systemd (Ubuntu): | |
status: | New → In Progress |
assignee: | nobody → Balint Reczey (rbalint) |
tags: | added: block-proposed |
Added qemu task for update-excuse tag to be resolved.
I have a fix prepared that is building/testing right now. If successful I'll open an upstream issue&PR for it.