2 files changed, 38 insertions, 0 deletions
diff --git a/results/classifier/accel-gemma3:12b/kvm/1749 b/results/classifier/accel-gemma3:12b/kvm/1749
new file mode 100644
index 000000000..70904da02
--- /dev/null
+++ b/results/classifier/accel-gemma3:12b/kvm/1749
@@ -0,0 +1,21 @@
+
+[Riscv-fu540] UEFI cannot be started with gdb on sifive fu540 platform？
+Description of problem:
+Using qemu start UEFI on sifive fu540 platform with option： -S -s.
+```
+qemu-system-riscv64                                            \
+                -cpu sifive-u54 -machine sifive_u               \
+                -bios U540.fd                                   \
+                -m 2048 -nographic -smp cpus=2,maxcpus=2        \
+                -S -s
+```
+UEFI url is： https://github.com/tianocore/edk2.git
+Steps to reproduce:
+1. start qemu with -S -s param in one terminal
+2. riscv64-unknown-linux-gnu-gdb in other terminal
+3. in gdb terminal:
+```
+       target remove :1234
+       c
+```
+4. in qemu terminal, there has no any output ?
diff --git a/results/classifier/accel-gemma3:12b/kvm/1749223 b/results/classifier/accel-gemma3:12b/kvm/1749223
new file mode 100644
index 000000000..d852bc28a
--- /dev/null
+++ b/results/classifier/accel-gemma3:12b/kvm/1749223
@@ -0,0 +1,17 @@
+
+mouse offset or invisible wall 2.11.0-3 
+
+(There was another post, I'm not sure if it is related though. Also not sure if it's Arch related, I wouldn't be surprised as I normally use Gentoo and have less problems with Gentoo.)
+
+
+qemu-system-x86_64 -enable-kvm -M q35 -cpu host -m 8192 -vga vmware -smp 4,sockets=1,cores=4,threads=1 -drive file=/path/to/my.img,if=virtio -soundhw ac97 -usb -monitor unix:/tmp/qemu-mon,server,nowait -usb --usbdevice host:0000:ffff -device vfio-pci,host=00:00.0 -alt-grab &
+
+
+
+When I grab the mouse in/out of the VM I tend to get an "invisible wall" half of the time.
+I can push past if I fling the mouse through it but not if I slowly keep moving down.
+
+The direction always seems to be down when I hit a wall (so a Y offset? maybe?)
+This has been happening since at least version 2.10.
+
+Not sure if "-alt-grab" has anything to do with it, that'd be my first guess.
\ No newline at end of file