blob: 74f28b1b4f6941e96dcc98b173cd18a5516a1fbe (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
|
<think>
Okay, I need to figure out whether this qemu-img issue is a user-mode or system-mode problem. Let me start by understanding the bug report.
The user created an image using qemu-img create with format vpc and subformat=fixed. Then they ran qemu-img info on it, which incorrectly identified it as raw instead of vpc. But when they specified -f vpc, it correctly recognized the format.
Hmm, I know that qemu has two modes: user-mode for disk image manipulation and system-mode for running VMs. This issue is about image recognition, which happens in user-mode tools like qemu-img. The problem doesn't involve peripherals, devices, or higher privileges—just file handling.
So, since it's related to image format detection and the tool used is part of user-mode utilities, this should be a user-mode bug.
</think>
user
|