1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
|
<think>
Alright, let's try to figure out the category for this bug report. The user provided a bug where KVM crashed with SIGSEGV in malloc_consolidate().
First, I see that the executable is /usr/bin/kvm and the signal is 11 (SIGSEGV), which usually indicates a segmentation fault, meaning there's an issue with memory access.
Looking at the stack trace, it mentions malloc_consolidate(), which is part of the memory management functions in the C library. This suggests that there might be a problem with how memory is being allocated or managed within KVM.
The KvmCmdLine shows some parameters including -usb and -usbdevice host:0fce:d0b5, indicating that this crash happens when Windows is installing drivers for a WDM device on USB. So the issue occurs during USB device handling.
I need to categorize this under one of the provided options: hypervisor, kernel, etc. Since KVM is a hypervisor, but the problem seems related to memory management in the host environment rather than the virtualization layer itself.
Alternatively, it could be a bug in how KVM interacts with the USB device driver or handles resources, leading to a crash in malloc. Considering that malloc_consolidate is part of the C library used by KVM, this might be a performance issue related to memory allocation during USB handling.
But since the primary application here is KVM and the error is within its execution, the category should reflect that it's specific to KVM functionality rather than a general system component. However, 'hypervisor' seems appropriate because KVM is the hypervisor in this context.
Wait, but the crash is happening in malloc, which is part of the C library used by KVM. So maybe it's not directly about the hypervisor itself but how KVM uses memory when handling USB devices. But since KVM is the main component here and the issue arises during its operation, I think 'hypervisor' is still the best fit.
Alternatively, if the problem was in device drivers or kernel modules, it might fall under 'device' or 'kernel', but given that KVM itself crashed, hypervisor seems more accurate.
</think>
hypervisor
|