x86: 0.951
graphic: 0.911
debug: 0.886
performance: 0.829
architecture: 0.806
ppc: 0.787
device: 0.744
mistranslation: 0.734
network: 0.725
user-level: 0.717
socket: 0.695
PID: 0.683
files: 0.681
semantic: 0.663
register: 0.658
peripherals: 0.644
hypervisor: 0.621
kernel: 0.611
i386: 0.606
permissions: 0.600
vnc: 0.534
virtual: 0.489
VMM: 0.479
arm: 0.466
risc-v: 0.436
boot: 0.401
TCG: 0.397
assembly: 0.344
KVM: 0.335
--------------------
x86: 0.971
virtual: 0.462
debug: 0.164
TCG: 0.101
files: 0.094
hypervisor: 0.068
assembly: 0.020
register: 0.017
user-level: 0.012
boot: 0.008
performance: 0.007
device: 0.007
VMM: 0.004
network: 0.004
kernel: 0.003
PID: 0.003
architecture: 0.003
semantic: 0.002
socket: 0.001
graphic: 0.001
risc-v: 0.001
i386: 0.000
vnc: 0.000
permissions: 0.000
ppc: 0.000
peripherals: 0.000
mistranslation: 0.000
KVM: 0.000
arm: 0.000

No BIOS MPFP structure with smp=92 and more

qemu 0.12.2, SeaBios 0.5.1, running qemu-system-x86_64.exe with option -smp.
If smp>=92 then no MP floating point structure present in 1 Mb. This may be verified by pmemsave 0 0x100000 in debugger and search for _MP_ signature in file.

qemu 0.10.5 (bios build 05/08/09) can smp=128 (and even 255 if not hangs :).

Host win 7 x64 RTM 7600.

QEMU 0.12 is quite outdated nowadays ... can you still reproduce this issue with the latest version of QEMU (currently version 2.8)?

Man, really? xD
6 years have passed...
Close the ticket please, I don't have this code anymore.
...
still laughing... sorry

Better late than never ;-)