add deepseek and gemma results

1 files changed, 20 insertions, 0 deletions

diff --git a/results/classifier/gemma3:12b/socket/2292 b/results/classifier/gemma3:12b/socket/2292
new file mode 100644
index 00000000..2cbd890b
--- /dev/null
+++ b/results/classifier/gemma3:12b/socket/2292
@@ -0,0 +1,20 @@
+
+UNIX socket path is too long
+Description of problem:
+At [Unikraft](https://unikraft.org) we facilitate the construction and also runtime lifecycle management of ultra-lightweight virtual machine unikernels.  We have developed [`kraft`](https://github.com/unikraft/kraftkit), an open-source tool which facilitates this across a number of different virtual machine monitors, [including QEMU](https://github.com/unikraft/kraftkit/tree/staging/machine/qemu).
+
+We are receiving increased reports of the following error from our users:
+
+```
+could not start and wait for QEMU process: qemu-system-x86_64: -qmp unix:/Users/__USERNAME__/.local/share/kraftkit/runtime/37a7691a-d402-4760-b493-692bb8d0460a/qemu_control.sock,server,nowait: UNIX socket path '/Users/__USERNAME__/.local/share/kraftkit/runtime/37a7691a-d402-4760-b493-692bb8d0460a/qemu_control.sock' is too long
+```
+
+We systematically build the relevant QEMU process command line and arguments with flags [via our Go SDK](https://github.com/unikraft/kraftkit/blob/staging/machine/qemu/v1alpha1.go#L180-L229) and include what has become an erroneously long UNIX path for the QAPI control socket which we use to manage instantiated VM instances.
+
+This issue tracks the increasing of maximum path length for the `-qmp` (and maybe other) flags which accept paths.
+Steps to reproduce:
+1. Install [`kraft`](https://github.com/unikraft/kraftkit), [Unikraft](https://unikraft.org)'s companion command-line client;
+2. Update KraftKit's config file to include an arbitrarily long path for `runtime_dir` by editing `~/.config/kraftkit/config.yaml`;
+3. Start a QEMU unikernel instance with `kraft run --arch x86_64 --plat qemu unikraft.org/helloworld:latest`
+Additional information:
+