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/files/2405 | |
| parent | 7f4364274750eb8cb39a3e7493132fca1c01232e (diff) | |
| download | qemu-analysis-d0c85e36e4de67af628d54e9ab577cc3fad7796a.tar.gz qemu-analysis-d0c85e36e4de67af628d54e9ab577cc3fad7796a.zip | |
add deepseek and gemma results
Diffstat (limited to 'results/classifier/gemma3:12b/files/2405')
| -rw-r--r-- | results/classifier/gemma3:12b/files/2405 | 17 |
1 files changed, 17 insertions, 0 deletions
diff --git a/results/classifier/gemma3:12b/files/2405 b/results/classifier/gemma3:12b/files/2405 new file mode 100644 index 000000000..30fa9ec0f --- /dev/null +++ b/results/classifier/gemma3:12b/files/2405 @@ -0,0 +1,17 @@ + +Qemu on Windows fails to parse absolute file path in -acpitable switch +Description of problem: +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. +Steps to 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. |