blob: aeae6d2f01426b6ec22f5a8112b15153d32c1dd6 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
|
<think>
Okay, I need to classify this bug report for QEMU into one of the given categories. Let me read through the details carefully.
The user is reporting a startup crash when using an EFI-enabled VM with KVM acceleration. They provided the command line they used and the error message from the log. The error points to kvm-all.c:690, specifically an assertion failure in kvm_log_clear_one_slot regarding alignment of start and size with psize.
Looking at the categories, I see options like 'device', 'graphic', 'network', 'KVM', etc. Since the issue is happening in accel/kvm/kvm-all.c and involves KVM-specific code (the error is from within the KVM module), it's clearly related to the KVM hypervisor.
I don't think this falls under 'mistranslation' or 'assembly' because those are more about code translation or assembly lowering. It's not a general bug but specific to KVM functionality. Other categories like 'device', 'graphic', etc., don't fit here since it's not hardware-related but rather a software issue in the hypervisor layer.
So, the category should be 'KVM' because the crash occurs within the KVM acceleration code.
</think>
The bug report involves an assertion failure in the KVM module (kvm-all.c), which is part of QEMU's KVM acceleration. The error specifically relates to memory alignment during logging operations within the KVM context. Since this issue arises from KVM-specific code and affects the hypervisor layer, it falls under the 'KVM' category.
**Answer:** KVM
|