diff options
| author | Christian Krinitsin <mail@krinitsin.com> | 2025-06-30 12:34:26 +0000 |
|---|---|---|
| committer | Christian Krinitsin <mail@krinitsin.com> | 2025-06-30 12:35:44 +0000 |
| commit | 25f8033d556aa17afaea4a5196ea7a69fe248320 (patch) | |
| tree | 0f056db167683be54ea1e5e72d29d6069af55e7d /results/classifier/deepseek-2-tmp/output/hypervisor/1180923 | |
| parent | 8e6da29e4ee5fc14bc1cc816a24f21271f14090d (diff) | |
| download | qemu-analysis-25f8033d556aa17afaea4a5196ea7a69fe248320.tar.gz qemu-analysis-25f8033d556aa17afaea4a5196ea7a69fe248320.zip | |
add new temporary deepseek-r1:14b results
Diffstat (limited to 'results/classifier/deepseek-2-tmp/output/hypervisor/1180923')
| -rw-r--r-- | results/classifier/deepseek-2-tmp/output/hypervisor/1180923 | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/results/classifier/deepseek-2-tmp/output/hypervisor/1180923 b/results/classifier/deepseek-2-tmp/output/hypervisor/1180923 new file mode 100644 index 000000000..79988ef61 --- /dev/null +++ b/results/classifier/deepseek-2-tmp/output/hypervisor/1180923 @@ -0,0 +1,4 @@ + +unused memory filled with 0x00 instead of 0xFF + +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? \ No newline at end of file |