summary refs log tree commit diff stats
path: root/gitlab/issues/target_missing/host_x86/accel_missing/2405.toml
diff options
context:
space:
mode:
Diffstat (limited to 'gitlab/issues/target_missing/host_x86/accel_missing/2405.toml')
-rw-r--r--gitlab/issues/target_missing/host_x86/accel_missing/2405.toml26
1 files changed, 26 insertions, 0 deletions
diff --git a/gitlab/issues/target_missing/host_x86/accel_missing/2405.toml b/gitlab/issues/target_missing/host_x86/accel_missing/2405.toml
new file mode 100644
index 000000000..ec8415007
--- /dev/null
+++ b/gitlab/issues/target_missing/host_x86/accel_missing/2405.toml
@@ -0,0 +1,26 @@
+id = 2405
+title = "Qemu on Windows fails to parse absolute file path in -acpitable switch"
+state = "opened"
+created_at = "2024-06-23T19:14:23.223Z"
+closed_at = "n/a"
+labels = ["ACPI", "host: x86", "hostos: Windows", "kind::Bug"]
+url = "https://gitlab.com/qemu-project/qemu/-/issues/2405"
+host-os = "Windows 11 23H2"
+host-arch = "x64"
+qemu-version = "v9.0.0-12054-g923cf646f4"
+guest-os = "no matter"
+guest-arch = "no matter"
+description = """I expect qemu-system-x86_64.exe to navigate to the path provided with -acpitable switch and to try to parse it. Instead, Qemu prints: "can't open file C: No such file or directory" if provided with absolute path. Qemu thinks "C:" itself is a file with acpi table.
+
+However, Qemu correctly processes files with relative path. If I run this command to try to parse file COPYING bundled in default qemu build:
+
+`qemu-system-x86_64.exe -acpitable "file=copying"`
+
+Qemu says: `qemu-system-x86_64.exe: -acpitable file=copying: warning: ACPI table has wrong length, header says 1313284128, actual size 17992 bytes`
+
+Then it proceeds to boot BIOS, as usual."""
+reproduce = """1. Run `qemu-system-x86_64.exe -acpitable "file=C:\\temp\\temp.txt"`
+2. Experience "can't open file C: No such file or directory" error message returning you to the command prompt. No BIOS screen.
+3. Run `qemu-system-x86_64.exe -acpitable "file=copying"` 
+4. Experience insignificant warning and then a normal BIOS screen."""
+additional = "n/a"