--- Comment #12 from Fabian Vogt firstname.lastname@example.org --- (In reply to Michal Kubeček from comment #11)
(In reply to Fabian Vogt from comment #10)
IMO kernel-default-base should be the same as kernel-default but just exclude support for physical hardware. Anything else is just asking for trouble. I can definitely see use-cases for 9pfs in production.
Sounds like you are still assuming kernel-*-base subpackage was designed for use in general purpose VMs. AFAIK this is not true, even package description says something very different. What you want is rather closer to -ec2 flavor we have had earlier or kvmsmall config recently introduced in newer branches (it is meant for developer use but it's probably closer to your idea what -base subpackage should be than actual -base). Therefore my suggestions from comment 7.
Yes, the best option is IMO to have a hand-pickable kernel with modules sorted into independent groups. That would allow arbitrary combination of flavors. It also makes it possible to install some additional modules when needed instead of including them in every image just in case.
However, we can't do that now, so my suggestion for the near future is to make kernel-default-base complete enough to allow its use in all situations on virtual hardware.
Both options avoid having to open a bug with the same discussion for every module ;-)