summary refs log tree commit diff stats
path: root/gitlab/issues/target_i386/host_missing/accel_KVM/2361.toml
diff options
context:
space:
mode:
Diffstat (limited to 'gitlab/issues/target_i386/host_missing/accel_KVM/2361.toml')
-rw-r--r--gitlab/issues/target_i386/host_missing/accel_KVM/2361.toml21
1 files changed, 21 insertions, 0 deletions
diff --git a/gitlab/issues/target_i386/host_missing/accel_KVM/2361.toml b/gitlab/issues/target_i386/host_missing/accel_KVM/2361.toml
new file mode 100644
index 000000000..2a27badd1
--- /dev/null
+++ b/gitlab/issues/target_i386/host_missing/accel_KVM/2361.toml
@@ -0,0 +1,21 @@
+id = 2361
+title = "-cpu host or -cpu max breaks GRUB on AMD"
+state = "closed"
+created_at = "2024-05-24T19:09:49.397Z"
+closed_at = "2024-05-31T20:20:05.384Z"
+labels = ["accel: KVM", "target: i386"]
+url = "https://gitlab.com/qemu-project/qemu/-/issues/2361"
+host-os = "Debian Bookworm"
+host-arch = "x86"
+qemu-version = "7.2"
+guest-os = "Debian Bookworm"
+guest-arch = "x86"
+description = """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."""
+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 = """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."""