This bug was fixed in the package systemd - 247.1-4ubuntu1
---------------
systemd (247.1-4ubuntu1) hirsute; urgency=medium
[ Dan Streetman ]
* d/p/lp1905044-test-use-cap_last_cap-for-max-supported-cap-number-n.patch:
Fix test use of new cap numbers with 5.8 kernel (LP: #1905044)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=d55c6f8186cb2cb73f61d6ff5b2e0ded82ef265c
[ Balint Reczey ]
* Merge to Ubuntu from Debian unstable
* Refresh patches
- Dropped changes:
* debian/patches/dhcp-Allow-setting-request-options-again.patch
(Upstream code has been changed in a similar way)
*
debian/patches/Revert-network-do-not-drop-foreign-config-if-interface-is.patch
debian/patches/network-Set-link-state-to-LINK_STATE_PENDING-instead-of-t.patch
(Revert-network-prevent-interfaces-to-be-initialized-multi.patch is
still kept)
*
debian/patches/lp1845909/0002-network-add-link-setting_genmode-flag.patch
* d/p/lp1905044-test-use-cap_last_cap-for-max-supported-cap-number-n.patch
(Present in upstream 247.)
* debian/udev.NEWS: Mention udev rules changes in 247
File: debian/udev.NEWS
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=9f33f19683c2b864384c2ae59b312b2c844ed633
* Don't start systemd-udev-trigger.service in containers.
It fails and is not likely to be useful.
File:
debian/patches/units-Don-t-start-systemd-udev-trigger.service-in-a-conta.patch
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=7b04fe5f98a4d204f73a1ec22884b9b3053a9a82
* test: use modern qemu numa arguments (LP: #1908259)
File: debian/patches/test-use-modern-qemu-numa-arguments.patch
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=158106e74d452cf6cd5cd737432cbe6b7d47286c
systemd (247.1-4) unstable; urgency=medium
[ наб ]
* debian/extra/kernel-install.d/85-initrd.install: Don't install initrd when
an explicit path was passed (Closes: #970213)
* debian/extra/kernel-install.d/85-initrd.install: Match initrd installation
messages and uninstallation to 90-loaderentry.install
[ Michael Biebl ]
* sd-device: keep escaped strings in DEVLINK= property (Closes: #976699)
systemd (247.1-3) unstable; urgency=medium
* d/t/timedated: Ignore return code of dbus-monitor in wait_mon()
We are not really interested in the return code and error messages from
dbus-monitor after killing it, so ignore them to avoid undesired
autopkgtest failures.
systemd (247.1-2) unstable; urgency=medium
[ Michael Biebl ]
* Upload to unstable
* Revert "d/t/timedated: use /bin/bash to work around job handling issue in
dash"
[ Balint Reczey ]
* debian/tests/timedated: Wait for the killed child only.
There may be other children of the script due to autopkgtest machinery
and they exit after the script exited. (LP: #1904406)
systemd (247.1-1) experimental; urgency=medium
* New upstream version 247.1
systemd (247-1) experimental; urgency=medium
* New upstream version 247
* Rebase patches
* Update symbol versions for the v247 release
systemd (247~rc2-3) experimental; urgency=medium
* Merge changes from unstable
* sd-device: make sd_device_has_current_tag() compatible with udev database
generated by older udevd
(Closes: #974730)
* Add Breaks: udev (<< 247~) to systemd.
This ensures that udev is upgraded alongside systemd and both support
the new udev tags concept introduced in v247. (Closes: #975554)
systemd (247~rc2-2) experimental; urgency=medium
* missing: define several syscall numbers for MIPS arch (Closes:
#974619)
systemd (247~rc2-1) experimental; urgency=medium
[ Michael Biebl ]
* New upstream version 247~rc2
- tmpfiles: Handle filesystems without ACL support in more cases
(Closes: #972135)
* Rebase patches
* Explicitly disable oomd
* Use -Dmode=release as we want a release, not developer, build
* Update symbols file for libudev1 and libsystemd0
[ Luca Boccassi ]
* systemd-container: install systemd-dissect binary.
Required for TEST-50-DISSECT since:
https://github.com/systemd/systemd/pull/16046
* d/t/control: install squashfs-tools for upstream test.
Required by TEST-50-DISSECT since upstream PR:
https://github.com/systemd/systemd/pull/16046
[ Dan Streetman ]
* d/control: update meson minimum version
https://github.com/systemd/systemd/pull/13842#issuecomment-601105975
* d/t/upstream: convert 'blacklist' term to 'deny-list'
Support transition for upstream-ci from
https://github.com/systemd/systemd/pull/16262
-- Balint Reczey <rbal...@ubuntu.com> Wed, 16 Dec 2020 10:27:06 +0100
** Changed in: systemd (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1908259
Title:
TEST-36-NUMAPOLICY fails with qemu 5.2
Status in systemd:
Unknown
Status in qemu package in Ubuntu:
Fix Released
Status in systemd package in Ubuntu:
Fix Released
Bug description:
Hi,
this test now fails as seen on ppc here
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/ppc64el/s/systemd/20201214_224336_8b0d8@/log.gz
+ /bin/qemu-system-ppc64 -smp 1 -net none -m 512M -nographic -vga none
-kernel /boot/vmlinux-5.8.0-25-generic -drive
format=raw,cache=unsafe,file=/var/tmp/systemd-test.qFc3xq/default.img -numa
node,nodeid=0 -initrd /boot/initrd.img-5.8.0-25-generic -append '
root=/dev/sda1 rw raid=noautodetect rd.luks=0 loglevel=2
init=/lib/systemd/systemd console=hvc0 selinux=0
SYSTEMD_UNIT_PATH=/usr/lib/systemd/tests/testdata/testsuite-36.units:/usr/lib/systemd/tests/testdata/units:
systemd.unit=testsuite.target systemd.wants=testsuite-36.service
systemd.wants=end.service '
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-system-x86_64 -smp 1 -net none -m 512M -nographic -vga none
-kernel /boot/vmlinuz-5.8.0-25-generic -drive
format=raw,cache=unsafe,file=/var/tmp/systemd-test.8Hqpmk/default.img -numa
node,nodeid=0 -initrd /boot/initrd.img-5.8.0-25-generic -append '
root=/dev/sda1 rw raid=noautodetect rd.luks=0 loglevel=2
init=/lib/systemd/systemd console=ttyS0 selinux=0
SYSTEMD_UNIT_PATH=/usr/lib/systemd/tests/testdata/testsuite-36.units:/usr/lib/systemd/tests/testdata/units:
systemd.unit=testsuite.target systemd.wants=testsuite-36.service
systemd.wants=end.service '
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-system-x86_64 -smp 1 -net none -m 512M -nographic -vga none
-kernel /boot/vmlinuz-5.8.0-25-generic -numa node,nodeid=0 -initrd
/boot/initrd.img-5.8.0-25-generic -append 'console=ttyS0 selinux=0'
Upgrading to 5.2 makes this:
$ /bin/qemu-system-x86_64 -smp 1 -net none -m 512M -nographic -vga none
-kernel /boot/vmlinuz-5.8.0-25-generic -numa node,nodeid=0 -initrd
/boot/initrd.img-5.8.0-25-generic -append 'console=ttyS0 selinux=0'
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=512M,nodeid=0
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-backend-ram,id=mem0,size=512M -numa node,memdev=mem0,nodeid=0
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-36-NUMAPOLICY/test.sh
QEMU_OPTIONS="-numa node,nodeid=0"
Fixing that to a new form should help.
To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1908259/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
