diff options
| author | Christian Krinitsin <mail@krinitsin.com> | 2025-07-03 07:27:52 +0000 |
|---|---|---|
| committer | Christian Krinitsin <mail@krinitsin.com> | 2025-07-03 07:27:52 +0000 |
| commit | d0c85e36e4de67af628d54e9ab577cc3fad7796a (patch) | |
| tree | f8f784b0f04343b90516a338d6df81df3a85dfa2 /results/classifier/gemma3:12b/boot/2361 | |
| parent | 7f4364274750eb8cb39a3e7493132fca1c01232e (diff) | |
| download | emulator-bug-study-d0c85e36e4de67af628d54e9ab577cc3fad7796a.tar.gz emulator-bug-study-d0c85e36e4de67af628d54e9ab577cc3fad7796a.zip | |
add deepseek and gemma results
Diffstat (limited to 'results/classifier/gemma3:12b/boot/2361')
| -rw-r--r-- | results/classifier/gemma3:12b/boot/2361 | 14 |
1 files changed, 14 insertions, 0 deletions
diff --git a/results/classifier/gemma3:12b/boot/2361 b/results/classifier/gemma3:12b/boot/2361 new file mode 100644 index 00000000..dcbcd043 --- /dev/null +++ b/results/classifier/gemma3:12b/boot/2361 @@ -0,0 +1,14 @@ + +-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. |