restructure results

1 files changed, 41 insertions, 0 deletions

diff --git a/results/classifier/zero-shot/118/device/2132 b/results/classifier/zero-shot/118/device/2132
new file mode 100644
index 00000000..b9d0ec61
--- /dev/null
+++ b/results/classifier/zero-shot/118/device/2132
@@ -0,0 +1,41 @@
+device: 0.832
+graphic: 0.798
+performance: 0.761
+kernel: 0.683
+architecture: 0.678
+mistranslation: 0.653
+register: 0.644
+semantic: 0.621
+KVM: 0.605
+permissions: 0.598
+peripherals: 0.584
+debug: 0.564
+network: 0.558
+user-level: 0.523
+PID: 0.478
+VMM: 0.475
+i386: 0.448
+boot: 0.444
+socket: 0.438
+assembly: 0.433
+vnc: 0.419
+risc-v: 0.418
+arm: 0.417
+hypervisor: 0.372
+ppc: 0.357
+x86: 0.356
+files: 0.218
+TCG: 0.214
+virtual: 0.089
+
+USB Hub as USB Host Device: Child devices not recognized in Win11
+Description of problem:
+I wanted to give the Windows environment direct access to some of the physical USB ports on my pc. So I mapped a selection of ports to Windows via the associated hub. Windows correctly recognizes the hub. Also, when devices are plugged into or removed from the associated ports, Windows recognizes the connection of a new device or its removal. However, regardless of the device, Windows reports:
+"USB device not recognized.
+The last USB device you connected to this computer has malfunctioned, and Windows does not recognize it."
+Steps to reproduce:
+1. Add one of the hosts USB hubs to a Windows VM as a USB Host Device.
+2. Verify that Windows recognizes the host hub in device manager.
+3. Try plugging in a USB device into one of the corresponding physical ports.
+Additional information:
+