blob: 648c9d22419e9c6264a7f1df2baa90c28bf2a535 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
|
<think>
Okay, so I need to classify this bug report related to QEMU and KVM. Let me read through it carefully.
The user reports an issue where KVM doesn't support KVM_CAP_USER_MEMORY, suggesting they upgrade their kernel or use a newer kvm-kmod. They mention running on RHEL 5.8 with kernel 2.6.18 and encountering the same error on another machine with RHEL 5.9, despite a higher kernel version.
They're also unsure if QEMU is compatible with RHEL 5.9 64-bit and whether this issue still exists in the latest QEMU. The user notes that this problem was present only in an old qemu-kvm fork and suggests closing the ticket since it's obsolete.
Looking at the possible categories: hypervisor, kernel, other, etc. Since the issue relates to KVM capabilities and kernel versions, "hypervisor" seems appropriate because KVM is a hypervisor.
</think>
hypervisor
|