Comment 1 for bug 2003226

Wow, interesting - thanks for the report.

With this CPU definition you already have almost all advanced features disabled.
And you said you even tried others - well done.

You also said that the same HW worked (with 16.04 instead of 22.04).
That is interesting.

Sadly, until we'd have access to comparable hardware that exposes this (I've tried two, not too similar, not showing the same), the best we could do it trying to corner the change that broke it.

So I wonder if you could try a few things, how possible (or not) would it be to:
- try newer code from [1], if it works we could bisect looking for a fix
- try older code, we do not yet know if it is qemu, libvirt, kernel or anything else.
  We could check them once the hard way - e.g. if you say you can do so we could
  bisect between qemu 2.5 (as in xenial) and 6.2 (as in jammy). Before I go in detail how
  to do so, would that even be possible? Or are those production machines not to be
  messed with too much?

[1]: https://launchpad.net/~canonical-server/+archive/ubuntu/server-backports