graphic: 0.987
architecture: 0.956
device: 0.877
boot: 0.820
debug: 0.755
performance: 0.736
semantic: 0.733
permissions: 0.583
PID: 0.558
mistranslation: 0.544
arm: 0.483
user-level: 0.473
assembly: 0.465
register: 0.451
vnc: 0.418
ppc: 0.372
risc-v: 0.279
kernel: 0.242
files: 0.217
TCG: 0.213
virtual: 0.211
VMM: 0.157
network: 0.152
hypervisor: 0.135
socket: 0.129
peripherals: 0.108
KVM: 0.030
i386: 0.026
x86: 0.018

-cpu host or -cpu max breaks GRUB on AMD
Description of problem:
I'm running the on an AMD Ryzen CPU host.  I am emulating a Debian Bookworm image stored in a raw disk.  It uses GRUB to load a large (400MB) initrd.  When ran with the flag -cpu host or -cpu max, GRUB throws an out of memory error while loading the initrd.  This doesn't occur when using -cpu kvm64 or excluding the -cpu flag.

If I direct boot the initrd and kernel via -initrd and -kernel, it works fine.  The image also works with -cpu host on an Intel CPU host machine.  The image also works with -cpu EPYC.
Steps to reproduce:
1. Create a raw disk with a large initrd and GRUB boot loader
2. Start a qemu machine on an AMD host 
3. Receive an error: out of memory
Additional information:
I could try selectively enabling CPU features, but I was wondering if the maintainers knew of any feature that might be causing this or how to list the features -cpu host enables.

I also am not 100% that this is a QEMU bug, but it seems the only way to fix it is changing the QEMU config.