1 files changed, 73 insertions, 0 deletions
diff --git a/results/classifier/108/other/1907776 b/results/classifier/108/other/1907776
new file mode 100644
index 000000000..74fd37771
--- /dev/null
+++ b/results/classifier/108/other/1907776
@@ -0,0 +1,73 @@
+graphic: 0.878
+boot: 0.772
+other: 0.753
+vnc: 0.740
+files: 0.728
+device: 0.687
+KVM: 0.658
+permissions: 0.643
+PID: 0.638
+semantic: 0.624
+network: 0.613
+performance: 0.592
+socket: 0.521
+debug: 0.491
+
+Mounting VFat drive yields error messages.
+
+Mounting a virtual Fat drive results in error messages (see attached image). 
+
+* https://www.qemu.org/docs/master/system/images.html#virtual-fat-disk-images
+
+The "drive" is however mounted, and as a test, saving a text file to the drive is successfully stored in the directory `/tmp`, which can be read after shutdown of Qemu.
+
+    Archlinux 5.9.11-arch2-1 (64-bit)
+    qemu-headless 5.1.0-3
+  
+    qemu-system-x86_64 -boot order=d -name test \
+      -enable-kvm -m 2G -cpu host -k sv \
+      -daemonize \
+      -drive if=pflash,format=raw,readonly,file=/usr/share/edk2-ovmf/x64/OVMF_CODE.fd \
+      -drive if=pflash,format=raw,file=~/vm/OVMF_VARS.local.fd \
+      -drive if=ide,format=raw,media=disk,index=1,file=fat:rw:/tmp \
+      -vnc :1 \
+      -cdrom /obj/archlinux/release/2020.10.01-x86_64.iso \
+      -drive format=raw,index=0,media=disk,file=~/vm/qemu.raw
+
+
+
+I have just noticed that the error does not appear when mounting the VFat drive in the installed instance of Arch Linux. The reported error messages occurred when using the "LiveUSB".
+
+
+The QEMU project is currently moving its bug tracking to another system.
+For this we need to know which bugs are still valid and which could be
+closed already. Thus we are setting the bug state to "Incomplete" now.
+
+If the bug has already been fixed in the latest upstream version of QEMU,
+then please close this ticket as "Fix released".
+
+If it is not fixed yet and you think that this bug report here is still
+valid, then you have two options:
+
+1) If you already have an account on gitlab.com, please open a new ticket
+for this problem in our new tracker here:
+
+    https://gitlab.com/qemu-project/qemu/-/issues
+
+and then close this ticket here on Launchpad (or let it expire auto-
+matically after 60 days). Please mention the URL of this bug ticket on
+Launchpad in the new ticket on GitLab.
+
+2) If you don't have an account on gitlab.com and don't intend to get
+one, but still would like to keep this ticket opened, then please switch
+the state back to "New" or "Confirmed" within the next 60 days (other-
+wise it will get closed as "Expired"). We will then eventually migrate
+the ticket automatically to the new system (but you won't be the reporter
+of the bug in the new system and thus you won't get notified on changes
+anymore).
+
+Thank you and sorry for the inconvenience.
+
+
+[Expired for QEMU because there has been no activity for 60 days.]
+