Comment 22 for bug 1978064

I think it may be worth noting on the upstream bug (https://gitlab.com/libvirt/libvirt/-/issues/304) one of the key issues here. They did ask:

> Anyway, what is the actual issue here? The CPU model shown by virsh capabilities may be wrong, but that's mostly aesthetic issue as it is not used for anything.

The ticket got auto-closed as no one got back to them quickly enough.

That developer might be correct from a libvirt perspective, but perhaps not accurate from the wider software ecosystem perspective. If Nova *is* using "virsh capabilities" under the hood for its checks, that may be reason for them to take upstream action, or they may say Nova shouldn't do that, in which case it can be pushed to Nova.

I'm totally in favor of getting this to work on Ubuntu in some way, but we may want to add that context to the upstream ticket.