diff options
Diffstat (limited to '')
| -rw-r--r-- | results/classifier/gemma3:12b/files/1599 | 10 | ||||
| -rw-r--r-- | results/classifier/gemma3:12b/files/1599539 | 8 |
2 files changed, 18 insertions, 0 deletions
diff --git a/results/classifier/gemma3:12b/files/1599 b/results/classifier/gemma3:12b/files/1599 new file mode 100644 index 00000000..29e61373 --- /dev/null +++ b/results/classifier/gemma3:12b/files/1599 @@ -0,0 +1,10 @@ + +7.2.1 - Windows installer +Description of problem: +Please release windows installer for new stable version 7.2.1 in + +https://www.qemu.org/download/ +Steps to reproduce: + +Additional information: + diff --git a/results/classifier/gemma3:12b/files/1599539 b/results/classifier/gemma3:12b/files/1599539 new file mode 100644 index 00000000..de0ef055 --- /dev/null +++ b/results/classifier/gemma3:12b/files/1599539 @@ -0,0 +1,8 @@ + +2.6.0: vvfat driver generates bad FAT entries + +The vvfat driver sometimes generates entries about which file system checking utilities generate complaints. + +For example, dosfsck will complain that the volume label entry has non-zero size. ScanDisk from Windows 9x complains about invalid dot (".") and dot-dot ("..") entries in directories and also about invalid long file name entries. MS-DOS ScanDisk also often manages to find "lost clusters" on the drive. + +Tangentially: qemu-img convert fat:test test.img doesn't seem to work -- it generates an 504MiB of zero bytes and hangs. qemu-img map fat:test generates an assertion failure. Having qemu-img working might have helped with debugging the above issue. \ No newline at end of file |