diff options
| author | Christian Krinitsin <mail@krinitsin.com> | 2025-06-01 21:35:14 +0200 |
|---|---|---|
| committer | Christian Krinitsin <mail@krinitsin.com> | 2025-06-01 21:35:14 +0200 |
| commit | 3e4c5a6261770bced301b5e74233e7866166ea5b (patch) | |
| tree | 9379fddaba693ef8a045da06efee8529baa5f6f4 /gitlab/issues_text/target_i386/host_missing/accel_KVM/1133 | |
| parent | e5634e2806195bee44407853c4bf8776f7abfa4f (diff) | |
| download | qemu-analysis-3e4c5a6261770bced301b5e74233e7866166ea5b.tar.gz qemu-analysis-3e4c5a6261770bced301b5e74233e7866166ea5b.zip | |
clean up repository
Diffstat (limited to 'gitlab/issues_text/target_i386/host_missing/accel_KVM/1133')
| -rw-r--r-- | gitlab/issues_text/target_i386/host_missing/accel_KVM/1133 | 10 |
1 files changed, 0 insertions, 10 deletions
diff --git a/gitlab/issues_text/target_i386/host_missing/accel_KVM/1133 b/gitlab/issues_text/target_i386/host_missing/accel_KVM/1133 deleted file mode 100644 index 8fe0446b2..000000000 --- a/gitlab/issues_text/target_i386/host_missing/accel_KVM/1133 +++ /dev/null @@ -1,10 +0,0 @@ -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. |