Comment 7 for bug 2032933

Checking kernels:

1. This already uses linux-image-virtual, it is not the even bigger linux-image-generic.
2. The change of the image build sadly combined it all
  a) new image build/seeding by CPC
  b) different kernel type -kvm -> -virtual that uses generic
  c) switch of kernel versions

We did not yet think about 2c here afaics.

This is not just -kvm -> -generic.
But instead 6.2.0-1003-kvm -> 6.3.0-7-generic

6.3.0-7-kvm does not exist (not built anymore), so to check which of the changes broke this we might need to look at.

The closest comparison I'd find is
- https://launchpad.net/ubuntu/+source/linux/6.2.0-21.21
- https://launchpad.net/ubuntu/+source/linux-signed/6.2.0-21.21

Installing that on my system

The new system with the high memory consumption has:
  linux-image-6.3.0-7-generic 6.3.0-7.7+1
  linux-modules-6.3.0-7-generic 6.3.0-7.7

I'm comparing for:
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/bootstrap/+build/25980736/+files/linux-modules-6.2.0-21-generic_6.2.0-21.21_amd64.deb
https://launchpad.net/~canonical-signing/+archive/ubuntu/primary-2022v1/+build/25984194/+files/linux-image-6.2.0-21-generic_6.2.0-21.21_amd64.deb

root@m-old:~# cat /proc/meminfo
MemTotal: 955692 kB
MemFree: 630128 kB
MemAvailable: 653536 kB

So that lets us assume, that the move 6.2->6.3 was not what broke it (actually 6.3 is even a little bit better).
The cause really seems to be more the move -kvm -> -generic.

I'm sure some change was expected, but so much?
Adding Linux bug tasks for them to chime in.