blob: acee045c8a8412b00db282fdd66aaef0af92b893 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
|
<think>
Okay, I'm looking at this bug report where an app runs fine in KVM mode but fails in TCG mode starting from QEMU 6.2. The user mentioned that it worked up until version 6.0, so the problem likely stems from a recent change.
The possible categories include things like mistranslation, assembly issues, device-related problems, etc. Since the issue is specific to TCG versus KVM, I need to determine which category fits best.
TCG stands for Translation-Cache Guest, part of QEMU's user-mode emulation. If there's a problem when using TCG but not with KVM, it suggests an issue in how QEMU translates code or interacts with the hypervisor differently between these modes.
Looking at the categories, "hypervisor" relates to issues involving KVM, which is a hypervisor. Since the problem occurs when switching from TCG (which emulates without a hypervisor) to using KVM (a hypervisor-based solution), it's likely tied to how QEMU interacts with or manages the hypervisor environment.
Therefore, the bug report falls under the "hypervisor" category because it pertains to differences in behavior between TCG and KVM modes, which are managed by different virtualization approaches.
</think>
hypervisor
|