virt-install versions and support for installing a virtual ubuntu 22.04

A few weeks ago I had smoothly used virt-install to install a virtual Ubuntu 22.04 machine on a physical Ubuntu 20.04 desktop.

Here's the full virt-install command example that worked:

    virt-install --cdrom ~/Downloads/ubuntu-22.04.3-desktop-amd64.iso --memory 4096 --vcpus 4 --disk size=8 --name ubuntu-22.04 --osinfo detect=on,require=on

Fast forward to today, it seems that my virt-install command on the physical Ubuntu 20.04 desktop has changed:

1. It no longer accepts the argument --osinfo detect=on,require=on which I had used in the past for a smooth-sailing virt-install from a Ubuntu 22.04 ISO image like in the command above.
2. Running osinfo-query os | grep ubuntu does not have Ubuntu 22.04 on its output, it only goes up to 20.04, as if implying that directly specifying 22.04 for virt-install is not currently supported by it.

Does this indicate I am missing any updates or might be using packages which aren't what I think I'm getting through the automatic updates mechanism, or does this reproduce for anyone right now? Should I enable Ubuntu Pro for this?

My virt-install --version is currently only 2.2.1 on the Ubuntu 20.04 where this happens. On a different physical machine which is Ubuntu 22.04 virt-install is currently 4.0.0.

I apt removed and re-installed virt-install without any errors, but still get the same behavior as described above. Here's the install command and output:

$ sudo apt install virtinstReading package lists... DoneBuilding dependency tree       Reading state information... DoneThe following NEW packages will be installed:  virtinst0 upgraded, 1 newly installed, 0 to remove and 15 not upgraded.Need to get 183 kB of archives.After this operation, 837 kB of additional disk space will be used.Get:1 http://archive.ubuntu.com/ubuntu focal-updates/universe amd64 virtinst all 1:2.2.1-3ubuntu2.2 [183 kB]Fetched 183 kB in 1s (202 kB/s)   Selecting previously unselected package virtinst.(Reading database ... 376358 files and directories currently installed.)Preparing to unpack .../virtinst_1%3a2.2.1-3ubuntu2.2_all.deb ...

After apt install completes successfully, the issue is the same.

a disclaimer:

I might be to blame by neglecting to dive into solving the following on my system where this is happening:

Image may be NSFW.
Clik here to view.

Not that it's a great excuse but the usability of that message is not something directly guiding you where to go or look in your system.