diff options
| author | Christian Krinitsin <mail@krinitsin.com> | 2025-07-03 19:39:53 +0200 |
|---|---|---|
| committer | Christian Krinitsin <mail@krinitsin.com> | 2025-07-03 19:39:53 +0200 |
| commit | dee4dcba78baf712cab403d47d9db319ab7f95d6 (patch) | |
| tree | 418478faf06786701a56268672f73d6b0b4eb239 /results/classifier/deepseek-r1:14b/output/hypervisor/1133 | |
| parent | 4d9e26c0333abd39bdbd039dcdb30ed429c475ba (diff) | |
| download | emulator-bug-study-dee4dcba78baf712cab403d47d9db319ab7f95d6.tar.gz emulator-bug-study-dee4dcba78baf712cab403d47d9db319ab7f95d6.zip | |
restructure results
Diffstat (limited to 'results/classifier/deepseek-r1:14b/output/hypervisor/1133')
| -rw-r--r-- | results/classifier/deepseek-r1:14b/output/hypervisor/1133 | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/results/classifier/deepseek-r1:14b/output/hypervisor/1133 b/results/classifier/deepseek-r1:14b/output/hypervisor/1133 new file mode 100644 index 00000000..b1738e93 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/hypervisor/1133 @@ -0,0 +1,11 @@ + +unused memory filled with 0x00 instead of 0xFF +Description of problem: +Qemu, ever since it was made (so, since 2003), has this problem in DOS (either PC-DOS or MS-DOS and partly Windows 9x) not recognizing the memory available when the memory is filled with 0x00 but when it is filled with 0xFF it gets recognized properly, where should I patch qemu to solve this memory problem? + +Refer to +https://bugs.launchpad.net/qemu/+bug/1180923 +Steps to reproduce: +1. +2. +3. |