add new temporary deepseek-r1:14b results

1 files changed, 13 insertions, 0 deletions

diff --git a/results/classifier/deepseek-2-tmp/reasoning/performance/1775702 b/results/classifier/deepseek-2-tmp/reasoning/performance/1775702
new file mode 100644
index 000000000..393944b23
--- /dev/null
+++ b/results/classifier/deepseek-2-tmp/reasoning/performance/1775702
@@ -0,0 +1,13 @@
+<think>
+Okay, so I need to classify this bug report into one of the given categories for QEMU. Let me read through the bug report carefully.
+
+The user mentions that after upgrading their Windows 10 guest OS to version 1803, the VM is running slower and causing high host CPU load even when the guest is almost idle. They didn't experience this issue with versions up to 1709. They provided links to other reports as well.
+
+Looking at the possible categories: mistranslation, assembly, other, device, graphic, socket, network, KVM, boot, vnc, debug, files, permissions, performance, kernel, peripherals, hypervisor.
+
+The issue here is about high CPU usage and slower VM performance after an OS upgrade. Since this affects overall system performance without specific symptoms pointing to a particular component like graphics or networking, it's likely related to how the host's CPU resources are being managed by QEMU for the guest.
+
+Considering the categories, "performance" seems appropriate because the problem is about resource usage and efficiency between the host and guest OS. The high CPU load suggests that the hypervisor (QEMU/KVM) might not be handling the virtualization efficiently after the guest upgrade. However, since it's more about performance metrics rather than a specific component like KVM itself or the hypervisor's functionality per se, "performance" is a suitable category.
+</think>
+
+performance
\ No newline at end of file