restructure results

1 files changed, 37 insertions, 0 deletions

diff --git a/results/classifier/zero-shot/118/files/1176 b/results/classifier/zero-shot/118/files/1176
new file mode 100644
index 00000000..365c9703
--- /dev/null
+++ b/results/classifier/zero-shot/118/files/1176
@@ -0,0 +1,37 @@
+files: 0.911
+graphic: 0.863
+device: 0.839
+network: 0.690
+vnc: 0.674
+architecture: 0.619
+ppc: 0.561
+socket: 0.494
+performance: 0.482
+risc-v: 0.442
+semantic: 0.403
+mistranslation: 0.362
+register: 0.346
+debug: 0.342
+VMM: 0.309
+boot: 0.293
+PID: 0.287
+virtual: 0.236
+hypervisor: 0.229
+arm: 0.214
+permissions: 0.202
+x86: 0.199
+TCG: 0.189
+peripherals: 0.189
+i386: 0.178
+kernel: 0.126
+user-level: 0.106
+assembly: 0.069
+KVM: 0.004
+
+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.