diff options
Diffstat (limited to '')
| -rw-r--r-- | results/classifier/gemma3:12b/files/117 | 2 | ||||
| -rw-r--r-- | results/classifier/gemma3:12b/files/1175 | 9 | ||||
| -rw-r--r-- | results/classifier/gemma3:12b/files/1176 | 8 | ||||
| -rw-r--r-- | results/classifier/gemma3:12b/files/1179 | 66 |
4 files changed, 85 insertions, 0 deletions
diff --git a/results/classifier/gemma3:12b/files/117 b/results/classifier/gemma3:12b/files/117 new file mode 100644 index 000000000..5b94a19c6 --- /dev/null +++ b/results/classifier/gemma3:12b/files/117 @@ -0,0 +1,2 @@ + +nested 9p filesystem with security_model=mapped-xattr diff --git a/results/classifier/gemma3:12b/files/1175 b/results/classifier/gemma3:12b/files/1175 new file mode 100644 index 000000000..f3c73441f --- /dev/null +++ b/results/classifier/gemma3:12b/files/1175 @@ -0,0 +1,9 @@ + +Crash / Assert in VVFAT.c while installaling WinXP from QEMU 7.0 running in Raspberry OS +Description of problem: +- Windows XP installation crashes QEMU with : +qemu-system-i386: ../block/vvfat.c:103: array_get: Assertion `index < array->next' failed. +Steps to reproduce: +Use command line above and run WindowsXP installation +Additional information: +Execution also leads to many "Invalid file name" being reported by QEMU diff --git a/results/classifier/gemma3:12b/files/1176 b/results/classifier/gemma3:12b/files/1176 new file mode 100644 index 000000000..749fb33ec --- /dev/null +++ b/results/classifier/gemma3:12b/files/1176 @@ -0,0 +1,8 @@ + +VVFAT :rw writes from guest (ReactOS, windowsXP) not visible by host +Description of problem: +As described in https://jira.reactos.org/browse/CORE-18327 +While ./LMS is mounted as a :rw VVFAT drive, guest OS (ReactOS) is able to read files BUT when files are "written" from the guest, they are not visible on host side. +QEMU execution is also massively polluted by "invalid file name" messages coming from https://git.qemu.org/?p=qemu.git;a=blob_plain;f=block/vvfat.c;hb=HEAD (but this is not specific to the use with ReactOS, as this is also observed with other guest : WXP, ...) + +See attached screenshot showing WXPSP3 as guest with file created in VVFAT drive while guest misses the newly created file. diff --git a/results/classifier/gemma3:12b/files/1179 b/results/classifier/gemma3:12b/files/1179 new file mode 100644 index 000000000..7702ed671 --- /dev/null +++ b/results/classifier/gemma3:12b/files/1179 @@ -0,0 +1,66 @@ + +qemu-img snapshot would break win8.1's system disk data +Description of problem: +`qemu-img snapshot` will cause a damage on windows 8.1 virtual machine +Steps to reproduce: +1.shutdown the virtual machine + +2.exec command +``` +$ qemu-img snapshot -d standard /media/user/SSD_VM/disk/win8_1.qcow2 +... +ERROR cluster 554329 refcount=0 reference=1 +ERROR cluster 554330 refcount=0 reference=1 +ERROR cluster 554331 refcount=0 reference=1 +ERROR cluster 554332 refcount=0 reference=1 +ERROR cluster 554333 refcount=0 reference=1 +ERROR cluster 554334 refcount=0 reference=1 +ERROR cluster 554335 refcount=0 reference=1 +Leaked cluster 557183 refcount=2 reference=1 +Leaked cluster 557472 refcount=2 reference=1 +Leaked cluster 564785 refcount=2 reference=1 +... +Leaked cluster 580393 refcount=2 reference=1 +Leaked cluster 580434 refcount=2 reference=1 +Leaked cluster 580713 refcount=2 reference=1 +Leaked cluster 580718 refcount=2 reference=1 +Leaked cluster 580726 refcount=2 reference=1 +Leaked cluster 580965 refcount=2 reference=1 +Leaked cluster 581268 refcount=2 reference=1 +Leaked cluster 581280 refcount=2 reference=1 +Leaked cluster 581367 refcount=2 reference=1 +Leaked cluster 582743 refcount=2 reference=1 +Leaked cluster 582938 refcount=2 reference=1 +Leaked cluster 583026 refcount=2 reference=1 +Leaked cluster 583027 refcount=2 reference=1 +Leaked cluster 583028 refcount=2 reference=1 +Leaked cluster 583029 refcount=2 reference=1 +Rebuilding refcount structure +Repairing cluster 547917 refcount=1 reference=0 +Repairing cluster 547936 refcount=1 reference=0 +Repairing cluster 547955 refcount=1 reference=0 +Repairing cluster 548069 refcount=1 reference=0 +Repairing cluster 548092 refcount=1 reference=0 +Repairing cluster 548115 refcount=1 reference=0 +Repairing cluster 548125 refcount=1 reference=0 +Repairing cluster 548128 refcount=1 reference=0 +Repairing cluster 548130 refcount=1 reference=0 +Repairing cluster 548144 refcount=1 reference=0 +Repairing cluster 548146 refcount=1 reference=0 +Repairing cluster 548150 refcount=1 reference=0 +Repairing cluster 548199 refcount=1 reference=0 +Repairing cluster 548201 refcount=1 reference=0 +Repairing cluster 548226 refcount=1 reference=0 +Repairing cluster 548234 refcount=1 reference=0 +Repairing cluster 548236 refcount=1 reference=0 +Repairing cluster 557073 refcount=1 reference=0 +Repairing cluster 557074 refcount=1 reference=0 +... + +``` + +3.start the virtual machine , it shows blue screen error: +`UNEXPECTED_STORE_EXCPETION` + +Additional information: +the windows virtual machine will automatically fix the damage that qemu-img caused on next restart . |