blob: 5a822b86495e978ca752570422eb95b8df5e1b7d (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
|
<think>
Okay, so I need to figure out whether this bug report is about a user-mode or system-mode issue in QEMU. Let's start by understanding what the problem is.
The documentation for QEMU's user-space emulator mentions some old "tar.gz" files that no longer exist. Specifically, they refer to qemu-XXX-i386-wine.tar.gz and qemu-runtime-i386-XXX-.tar.gz. These are binary blobs that aren't available anymore on QEMU.org. The issue is causing confusion because the docs still reference them.
The user suggests that these parts should be rephrased and maybe point to building the components, possibly referencing the LFS book with some scripts. Also, there are other instances of non-existent "tar.gz" files mentioned in different sections like Network emulation.
Looking at the previous report [2], it seems similar confusion about where those filenames came from. The user notes that these references are old and probably haven't been updated since the days of older texi documentation over a decade ago.
Now, considering QEMU's modes: user-mode is for running unprivileged processes in an emulated environment, like Wine or other userland software. System-mode deals with emulating entire systems, including peripherals and OSes.
The bug report specifically mentions the user-space emulator, which points to user-mode. The documentation issue pertains to building or referencing components that are part of the user-space setup, not system-level emulation. So the problem is within the user-mode section.
</think>
user
|