1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
|
<think>
Okay, so I'm looking at this bug report where QEMU's qemu-img fails to create images that are 4GB or larger. The user mentioned they're on Windows XP with an NTFS drive and using either the precompiled version of QEMU 0.12.x or a locally built one. When they run 'qemu-img create foo.img 4G', it creates a zero-length file instead.
First, I need to classify this bug into one of the given categories: mistranslation, assembly, other, device, graphic, socket, network, KVM, boot, vnc, debug, files, permissions, performance, kernel, peripherals, hypervisor.
The issue is with creating images larger than 4GB. QEMU's qemu-img is supposed to handle disk image creation. The problem occurs on Windows, specifically when using NTFS. So it might be related to how QEMU interacts with the file system or handles large files.
Considering the categories: 'files' seems relevant because it's about creating a file of a certain size. Another possibility could be 'permissions', but in this case, it's more about the file size limit rather than access permissions.
Wait, but on NTFS, there might be specific handling for large files. Maybe QEMU isn't correctly setting up the sparse or dynamic allocation needed for large images. Alternatively, it could be a bug in how the image format (like raw, qcow2) is written when the size exceeds certain thresholds.
Looking at the possible categories again, 'files' directly relates to the file creation issue. It's not about translation errors, assembly code, or performance per se, but more about correctly creating a file of specified size.
</think>
The bug report describes an issue where `qemu-img create` fails to create images larger than 4GB on Windows XP with NTFS. The problem is related to the creation and handling of large files, which falls under the category of file operations.
**Answer:**
files
|