1
2
3
4
5
6
7
8
9
10
11
12
13
|
<think>
Okay, so I need to classify this bug report into one of the given categories. Let me read through the problem carefully.
The user is running a custom-built Android-x86_64 guest on an Arch Linux host with kernel version 4.12.10. After upgrading QEMU to 2.10.0-1, they're encountering an error: "Could not disable RealTimeClock events (20160831/evxfevnt-267)". This causes the UI to become sluggish, and ACPI functions stop working. When they revert to QEMU 2.9.0-3, everything works fine again.
Looking at the categories provided: mistranslation, assembly, other, device, graphic, socket, network, KVM, boot, vnc, debug, files, permissions, performance, kernel, peripherals, hypervisor.
The main issues here are related to QEMU's behavior after an upgrade. The error message mentions RealTimeClock events and ACPI not working. Since QEMU is a hypervisor, and the problem occurs when using it with KVM (as indicated by the mention of libvirt's Shutdown button which relates to ACPI control), I think this falls under the hypervisor category.
The symptoms include UI slowness and ACPI issues, which might be due to changes in how QEMU interacts with the virtualization environment. Since downgrading fixes it, there's likely a regression in QEMU 2.10.0 related to KVM or hypervisor functions.
</think>
hypervisor
|