1 files changed, 76 insertions, 0 deletions
diff --git a/results/classifier/zero-shot/108/other/1906184 b/results/classifier/zero-shot/108/other/1906184
new file mode 100644
index 000000000..d06e04493
--- /dev/null
+++ b/results/classifier/zero-shot/108/other/1906184
@@ -0,0 +1,76 @@
+graphic: 0.897
+other: 0.869
+socket: 0.853
+KVM: 0.851
+network: 0.831
+device: 0.821
+PID: 0.793
+boot: 0.774
+vnc: 0.759
+performance: 0.747
+permissions: 0.740
+files: 0.713
+semantic: 0.700
+debug: 0.689
+
+Lots of stuttering/crackling in guest sound
+
+When listening to music (e.g. with VLC) or watching Youtube on the guest, there's lots of stuttering and crackling in the sound.
+
+
+Tested with the following QEMU start commands:
+
+qemu-system-x86_64 -enable-kvm -m 6G -cpu host -smp 3 -cdrom ./linux/kubuntu-20.04-desktop-amd64.iso -boot d -vga virtio -soundhw hda -display sdl,gl=on
+
+qemu-system-x86_64 -enable-kvm -m 6G -cpu host -smp 3 -cdrom ./linux/kubuntu-20.04-desktop-amd64.iso -boot d -vga qxl -soundhw hda -display sdl
+
+qemu-system-x86_64 -enable-kvm -m 6G -cpu host -smp 3 -cdrom ./linux/kubuntu-20.04-desktop-amd64.iso -boot d -vga qxl -soundhw hda -display gtk
+
+
+If I use the following command (QXL graphics, "remote" access via SPICE over unix socket), stuttering is not completely gone but MUCH less annoying:
+
+qemu-system-x86_64 -enable-kvm -m 6G -cpu host -smp 3 -cdrom ./linux/kubuntu-20.04-desktop-amd64.iso -boot d -soundhw hda -vga qxl -device virtio-serial-pci -device virtserialport,chardev=spicechannel0,name=com.redhat.spice.0 -chardev spicevmc,id=spicechannel0,name=vdagent -spice unix,addr=/tmp/vm_spice.socket,disable-ticketing
+
+and this command for accessing the VM:
+remote-viewer spice+unix:///tmp/vm_spice.socket 
+
+
+
+Guest: Kubuntu 20.04 64-bit (live), but occurs with many other as well
+Host: Arch Linux, with KDE desktop
+CPU: Intel Xeon E3-1230v2 (4 cores + hyperthreading)
+RAM: 16 GB
+GPU: Nvidia GTX 980 Ti
+
+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.]
+