blob: 1680311d67aea742fdda39f1ea06fd67687d10aa (
plain) (
blame)
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
27
28
29
|
<think>
Alright, I need to classify this bug report into one of the given categories. The issue is about UEFI firmware not being able to write to a "fake" FAT hard disk in QEMU.
First, let's understand what each category means:
- **mistranslation**: This would involve incorrect mapping from source architecture to IR or target, likely in user-mode.
- **assembly**: Related to assembly lowering issues.
- **other**: For anything that doesn't fit the other categories.
- **device**: Issues with hardware devices emulation.
- **graphic**: Problems related to graphical output.
- **socket**: Socket-related bugs.
- **network**: Networking issues.
- **KVM**: Kernel-based Virtual Machine specific problems.
- **boot**: Booting issues.
- **vnc**: Remote desktop protocol (VNC) related.
- **debug**: Debugging tools or logs.
- **files**: File handling issues.
- **permissions**: Permission-related bugs.
- **performance**: Performance degradation.
- **kernel**: Kernel-level issues.
- **peripherals**: Problems with peripherals like disks, USB, etc.
- **hypervisor**: Issues with the hypervisor layer.
The bug report mentions that UEFI applications can't write to an emulated FAT disk. The problem occurs when using Tianocore OVMF firmware and the `-hda fat:rw:path/here` option. Files get created or written but are corrupted.
Since it's about writing to a disk image in QEMU, this relates to how the hypervisor (QEMU) emulates storage devices. The issue is with the emulation of the hard disk, specifically the FAT filesystem. Therefore, this falls under **peripherals**, as it deals with device emulation rather than other categories like boot or network.
</think>
peripherals
|