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-tmp/reasoning/KVM/1806040 | |
| parent | 7f4364274750eb8cb39a3e7493132fca1c01232e (diff) | |
| download | emulator-bug-study-d0c85e36e4de67af628d54e9ab577cc3fad7796a.tar.gz emulator-bug-study-d0c85e36e4de67af628d54e9ab577cc3fad7796a.zip | |
add deepseek and gemma results
Diffstat (limited to 'results/classifier/deepseek-2-tmp/reasoning/KVM/1806040')
| -rw-r--r-- | results/classifier/deepseek-2-tmp/reasoning/KVM/1806040 | 11 |
1 files changed, 0 insertions, 11 deletions
diff --git a/results/classifier/deepseek-2-tmp/reasoning/KVM/1806040 b/results/classifier/deepseek-2-tmp/reasoning/KVM/1806040 deleted file mode 100644 index cb481f4f..00000000 --- a/results/classifier/deepseek-2-tmp/reasoning/KVM/1806040 +++ /dev/null @@ -1,11 +0,0 @@ -<think> -Alright, let's try to figure out how to classify this bug report. The user is experiencing an issue with QEMU related to Nested VMX virtualization and live migration not being supported. They mentioned that after updating QEMU from Git, they can't create snapshots due to this error. - -Looking at the provided categories: device, graphic, socket, network, KVM, etc., I need to determine which one fits best. The error is about Nested VMX virtualization, which is a feature related to KVM hypervisor support in QEMU. KVM allows for full hardware-assisted virtualization and nested virtualization would be an extension of that. - -The user's setup uses the '-hypervisor' parameter with 'kvm=off', but they're still encountering issues. They found that a specific commit caused the problem, which likely modified how Nested VMX is handled in KVM. The error message directly points to a limitation in QEMU regarding live migration with nested VMX. - -So, considering all this, the most appropriate category here would be 'KVM' because it's related to the hypervisor functionality and virtualization features within that context. -</think> - -KVM
\ No newline at end of file |