blob: c59949457e38b35454691e99e79ab1ffb813057d (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
|
<think>
Alright, I need to classify this bug report for QEMU. Let's see what the user provided.
The user mentioned "Crash why dragon fly 3.4.1" and provided a command line with QEMU options like -vga vmware, -net nic,model=virtio, etc. There's also an internal KVM error with suberror 1 and emulation failure.
Looking at the categories: possible ones include kernel, hypervisor, device, network, graphic, etc. The mention of "KVM internal error" is a key clue here because KVM stands for Kernel-based Virtual Machine, which is part of the hypervisor layer in QEMU. So this isn't about user-mode translation but rather the hypervisor itself.
Additionally, the detailed register dumps and code context suggest it's related to how QEMU emulates hardware or interacts with the kernel during virtualization. Since KVM is involved, the category should be 'hypervisor'.
</think>
hypervisor
|