blob: 7067d15d646acbb240769093727cf2243c6dda56 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
|
<think>
Okay, so I'm trying to figure out how to classify this bug report. The issue is about savevm/loadvm/migration being broken for 32-bit ARM guests that use TrustZone.
First, I'll break down the components mentioned: savevm and loadvm relate to saving and loading a virtual machine's state, which is part of migration functionality. TrustZone is a security technology used in ARM processors to create secure partitions on the hardware.
The problem occurs with 32-bit ARM guests, so it's specific to ARM architecture. The fact that TrustZone is involved suggests it's related to security or partitioning features within the virtual machine.
Looking at the categories provided: hypervisor seems relevant here because migration and save/load functions are typically managed by the hypervisor layer. However, since TrustZone is a hardware feature, maybe it interacts with how the hypervisor handles secure partitions, which could affect migration processes.
Other categories like device or kernel might be related, but I think hypervisor is more precise here because it's about managing VM states and possibly handling security features during migration.
</think>
hypervisor
|