diff options
| author | Christian Krinitsin <mail@krinitsin.com> | 2025-07-03 07:27:52 +0000 |
|---|---|---|
| committer | Christian Krinitsin <mail@krinitsin.com> | 2025-07-03 07:27:52 +0000 |
| commit | d0c85e36e4de67af628d54e9ab577cc3fad7796a (patch) | |
| tree | f8f784b0f04343b90516a338d6df81df3a85dfa2 /results/classifier/deepseek-2/reasoning/hypervisor/447 | |
| parent | 7f4364274750eb8cb39a3e7493132fca1c01232e (diff) | |
| download | qemu-analysis-d0c85e36e4de67af628d54e9ab577cc3fad7796a.tar.gz qemu-analysis-d0c85e36e4de67af628d54e9ab577cc3fad7796a.zip | |
add deepseek and gemma results
Diffstat (limited to 'results/classifier/deepseek-2/reasoning/hypervisor/447')
| -rw-r--r-- | results/classifier/deepseek-2/reasoning/hypervisor/447 | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/results/classifier/deepseek-2/reasoning/hypervisor/447 b/results/classifier/deepseek-2/reasoning/hypervisor/447 new file mode 100644 index 000000000..b9e64bd26 --- /dev/null +++ b/results/classifier/deepseek-2/reasoning/hypervisor/447 @@ -0,0 +1,9 @@ +<think> +Okay, I need to classify this bug report about QEMU. The user provided a list of categories: mistranslation, assembly, other, device, graphic, socket, network, KVM, boot, vnc, debug, files, permissions, performance, kernel, peripherals, hypervisor. + +The error message says "qemu-arm: Unable to reserve 0xffff0000 bytes... for use as guest address space." It mentions virtual memory settings and suggests using the -R option to reserve less. + +This seems related to how QEMU allocates memory for the guest OS. Since it's about reserving address space, which is part of the hypervisor's responsibilities, I think this falls under the 'hypervisor' category. +</think> + +hypervisor \ No newline at end of file |