linux: please move dmi-sysfs.ko (CONFIG_DMI_SYSFS for SMBIOS support) from linux-modules-extra to linux-modules
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
Medium
|
You-Sheng Yang | ||
Jammy |
Fix Released
|
Medium
|
You-Sheng Yang | ||
Lunar |
Won't Fix
|
Undecided
|
Unassigned | ||
Mantic |
Fix Released
|
Medium
|
You-Sheng Yang | ||
Noble |
Fix Released
|
Medium
|
You-Sheng Yang |
Bug Description
SRU Justification
[Impact]
The dmi-sysfs.ko module (CONFIG_DMI_SYSFS) is currently shipped in linux-modules-
https:/
https:/
A user launching a VM using the linux-kvm kernel image is not able to specify SMBIOS strings to automatically configured userspace services and programs due to the lack of this kconfig. We make extensive use of these in systemd's upstream CI, which is running on Github Actions, which uses Jammy, so it would be great to have this backported.
For example:
qemu-system-x86_64 \
-machine type=q35,
-smp 2 \
-m 1G \
-cpu host \
-nographic \
-nodefaults \
-serial mon:stdio \
-drive if=none,
-device virtio-
-device scsi-hd,
-smbios type=11,
[Fix]
Please consider moving this module to linux-modules.
These are already enabled in the 'main' kernel config, and in other distros. In Debian/
To verify this works, it is sufficient to check that the /sys/firmware/
$ ls /sys/firmware/
0-0 126-1 126-4 126-8 130-0 133-0 136-0 140-2 15-0 18-0 21-1 221-1 24-0 7-1 8-2 8-6
1-0 126-10 126-5 126-9 131-0 134-0 14-0 140-3 16-0 19-0 219-0 221-2 3-0 7-2 8-3 9-0
12-0 126-2 126-6 127-0 131-1 135-0 140-0 140-4 17-0 2-0 22-0 221-3 4-0 8-0 8-4 9-1
126-0 126-3 126-7 13-0 132-0 135-1 140-1 14-1 17-1 21-0 221-0 222-0 7-0 8-1 8-5
Without this module installed and loaded, the directory won't be there. Once enabled, it will be there.
[Test]
1. pull built linux-modules packages for architectures with do_extras_package
set to true;
2. extract the deb and check if dmi-sysfs kernel module file exists:
$ dpkg-deb -R linux-modules-*.deb .
$ find . -name dmi-sysfs.ko\*
[Regression Potential]
Moving a module from a less-common to a more-common package should not have any negative side effects. The main effect will be a little more disk space used by the more common package, whether the module is in use or not. There will also be more functionality available in the default installation, which means a slightly increased surface and possibility of new bugs in case it gets used.
description: | updated |
Changed in linux-kvm (Ubuntu Jammy): | |
status: | New → Confirmed |
description: | updated |
Changed in linux (Ubuntu Noble): | |
importance: | High → Medium |
Changed in linux (Ubuntu Mantic): | |
importance: | High → Medium |
Changed in linux (Ubuntu Jammy): | |
importance: | High → Medium |
Changed in linux (Ubuntu Mantic): | |
status: | In Progress → Fix Committed |
Changed in linux (Ubuntu Jammy): | |
status: | In Progress → Fix Committed |
This shouldn't be an issue in Mantic and Noble as the linux-kvm flavor was replaced by linux-virtual which has the normal config set.