1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
|
<think>
Okay, so I need to classify this bug report for QEMU into one of the given categories. Let me read through the problem carefully.
The user is reporting an issue when using `qemu-system-aarch64` with a Raspberry Pi 3 machine type and more than 4GB RAM. Specifically, they're trying to run it with `-m 8G`, which causes an error message:
```
Unexpected error in visit_type_uintN() at /builddir/build/BUILD/qemu-3.0.0/qapi/qapi-visit-core.c:164:
qemu-system-aarch64: Parameter 'vcram-base' expects uint32_t
```
They mention that the problem is using more than 4GB RAM, which isn't supported by `raspi3`. They also note that when they tried using too many CPU cores (more than 4), QEMU gave a clear error message about the maximum CPUs allowed. So for consistency, they want a better error message in this case.
Looking at the possible categories:
- **mistranslation**: Incorrect mapping from source to target architecture. Doesn't seem related here.
- **assembly**: Assembly lowering issue. Not applicable.
- **other**, **device**, **graphic**, **socket**, **network**, **KVM**, **boot**, **vnc**, **debug**, **files**, **permissions**, **performance**, **kernel**, **peripherals**, **hypervisor**.
The bug is about a hardware configuration limit (RAM for `raspi3`). It's not related to translation issues or assembly. The issue is specific to the machine type and its constraints, which falls under device-related problems because it's about hardware emulation limits.
So the category should be **device**, as it pertains to how QEMU handles the Raspberry Pi 3 machine's limitations.
</think>
The bug report deals with a limitation in the `raspi3` machine type regarding RAM size. It's related to how QEMU handles device-specific constraints, particularly hardware configuration limits.
**device**
|