Comment 15 for bug 1902654

Changes:
- "any_layout" "off" no more present (all six entries of the bad compat are gone)
- 2.4 values in "qemu32-x86_64-cpu" "model-id" (matches Bionic now, formerly had 2.4+2.3 set)
- "migration" "send-configuration" (still present as before and as in Bionic)
- all other implied compat changes between 2.3/2.4 changed as well e.g. it now has "virtio-blk-device" "scsi" "true" (which is 2.4)

The above is great - all compat entries that Bionic had are now present and the bad ones that were too much are gone \o/.
But it isn't perfect yet there is a "tail" that repeats some of the compat entries.

The following "tail" is registered in the wily compat type twice now:
"virtio-blk-device" "scsi" "true"
"e1000" "extra_mac_registers" "off"
"virtio-pci" "x-disable-pcie" "on"
"virtio-pci" "migrate-extra" "off"
"fw_cfg_mem" "dma_enabled" "off"
"fw_cfg_io" "dma_enabled" "off"
"qemu32-x86_64-cpu" "model-id" "QEMU Virtual CPU version 2.4.0"
"qemu64-x86_64-cpu" "model-id" "QEMU Virtual CPU version 2.4.0"
"athlon-x86_64-cpu" "model-id" "QEMU Virtual CPU version 2.4.0"
"Haswell-x86_64-cpu" "abm" "off"
"Haswell-noTSX-x86_64-cpu" "abm" "off"
"Broadwell-x86_64-cpu" "abm" "off"
"Broadwell-noTSX-x86_64-cpu" "abm" "off"
"host-x86_64-cpu" "host-cache-info" "on"
"x86_64-cpu" "check" "off"
"qemu64-x86_64-cpu" "sse4a" "on"
"qemu64-x86_64-cpu" "abm" "on"
"qemu64-x86_64-cpu" "popcnt" "on"
"qemu32-x86_64-cpu" "popcnt" "on"
"Opteron_G2-x86_64-cpu" "rdtscp" "on"
"Opteron_G3-x86_64-cpu" "rdtscp" "on"
"Opteron_G4-x86_64-cpu" "rdtscp" "on"
"Opteron_G5-x86_64-cpu" "rdtscp" "on"

While functionally that should be no difference it needs to be analyzed as I hope to much to not touch this broken old type again that we should not let it slip this time int hat regard.

This is due to applying pc_i440fx_2_4_machine_options + pc_i440fx_wily_machine_options. The former does 2.4 proper and the latter the special wily things.
But since wily is this weird hybrid it needs "only" wily and no normal 2.4 to be called.
I think I have this fixed now, rebuilding for another test to be sure ...