qemu64 CPU model is incorrect

[The Lemon Man]

At the moment the "qemu64" CPU is defined as follows:

```
        .vendor = CPUID_VENDOR_AMD,
        .family = 6,
        .model = 6,
        .stepping = 3,
```

According to Wikipedia [1] this means the CPU is defined as part of the
K7 family while the AMD64 ISA was only introduced with the K8 series!

This causes some software such as LLVM to notice the problem (32-bit cpu
with 64-bit capability reported in the cpuid flag) and produce various
error messages.

The simple solution would be to upgrade this definition to use the Sledgehammer
family (15) instead.

[1] https://en.wikipedia.org/wiki/List_of_AMD_CPU_microarchitectures

[Daniel Berrange (berrange)]

Your analysis of the problem with family makes sense & we do have mechanism to fix this in QEMU while keeping back compat for existing deployments.

I'm curious as to the actual errors LLVM reports ?

FWIW, even though qemu64 is the default CPU, practically everyone would be better off choosing one of the other CPU models explicitly to better suit their desired use case. There is some guidance here https://qemu.weilnetz.de/doc/qemu-doc.html#cpu_005fmodels

[The Lemon Man (lemonboy)]

The error message is a rather cryptic "LLVM ERROR: 64-bit code requested on a subtarget
that doesn't support it!" as it knows Athlon CPUs don't support the AMD64 ISA.

I will relay the tip to the people managing the VMs, I guess this problem went unnoticed
for so long because there are not many `qemu64` users.

I'm available to test a patch whenever it becomes available, I didn't directly send one
because I was afraid of breaking the backward compatibility and some (many?) VMs.

[Thomas Huth (th-huth)]

The QEMU project is currently considering to move its bug tracking to
another system. For this we need to know which bugs are still valid
and which could be closed already. Thus we are setting older bugs to
"Incomplete" now.

If you still think this bug report here is valid, then please switch
the state back to "New" within the next 60 days, otherwise this report
will be marked as "Expired". Or please mark it as "Fix Released" if
the problem has been solved with a newer version of QEMU already.

Thank you and sorry for the inconvenience.

[Thomas Huth (th-huth)]

This is an automated cleanup. This bug report has been moved to QEMU's
new bug tracker on gitlab.com and thus gets marked as 'expired' now.
Please continue with the discussion here:

 https://gitlab.com/qemu-project/qemu/-/issues/191