--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: linux-image-amd64: Please enable CONFIG_VIRTIO_MMIO_CMDLINE_DEVICES
- From: Fryderyk Dziarmagowski <f.dziarmagowski@adito.de>
- Date: Fri, 06 Jan 2023 12:12:03 +0100
- Message-id: <167300352344.251822.5964624187113595799.reportbug@freddix.aditosoftware.local>
Package: linux-image-amd64
Severity: wishlist
X-Debbugs-Cc: fdziarmagowski@gmail.com
Dear Maintainer,
please consider enabling CONFIG_VIRTIO_MMIO_CMDLINE_DEVICES (required to run
Debian in firecracker microvm)
-- System Information:
Debian Release: 11.6
APT prefers stable
APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'stable-
security'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.0.0-6-amd64 (SMP w/6 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages linux-image-amd64 depends on:
pn linux-image-5.10.0-19-amd64 <none>
pn linux-image-5.10.0-20-amd64 <none>
pn linux-image-6.0.0-0.deb11.2-amd64 <none>
ii linux-image-6.0.0-6-amd64 6.0.12-1
linux-image-amd64 recommends no packages.
--- End Message ---
--- Begin Message ---
Hi
This bug was filed for a (very) old kernel or the bug is old itself
without resolution. Maybe it was for a feature enablement which nobody
acted on. We are sorry we were not able to timely deal with this issue.
There are many open bugs for the src:linux package and thus we are
closing older bugs where it's unclear if they still occur in newer
versions and are still relevant to the reporter. For an overview see:
https://bugs.debian.org/src:linux .
If you can reproduce your issue with
- the current version in unstable/testing
- the latest kernel from backports
or, if it was a feature addition/wishlist and still consider it
relevant, then:
Please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.
Please try to provide as much fresh details including kernel logs where
relevant. In particular were an issue is coupled with specific hardware we
might ask you to do additional debugging on your side as the owner of the
hardware.
Regards,
Salvatore
--- End Message ---