blob: 1311ef8dedea09179a4735389db0b6677ff50537 (
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 SSH module bug in QEMU is a user-mode or system-mode issue. The user installed gcc-8 and libssh on Ubuntu 18.04 arm64 and tried compiling QEMU versions like 3.1.0, 4.0.0, or 4.1.0 with SSH support. When they did that, GCC threw errors about undeclared variables such as 'SSH_KNOWN_HOSTS_OTHER' and 'SSH_KNOWN_HOST_UNKNOWN'.
Hmm, let me break this down. QEMU is a machine emulator that can run in two modes: user-mode and system-mode. User-mode emulation allows running unmodified guest OSes on the same host kernel, while system-mode emulates an entire machine with its own hardware.
The error here seems to be during compilation when SSH support is enabled. The variables mentioned are part of libssh's API. Maybe they're using a version of libssh that doesn't have those constants defined? Or perhaps QEMU expects them but the installed libssh doesn't include them, leading to these errors.
If this were a system-mode issue, it might involve hardware emulation or kernel-level operations. But since it's about SSH module compilation and undeclared variables in the code, it sounds more like a software issue within the user application layer—specifically, how QEMU is using the libssh library.
User-mode issues typically relate to processes running with standard privileges and dealing with application-specific functions. Here, the problem arises when compiling QEMU with SSH support, which is part of its functionality for remote connections, probably in user-mode where it's handling SSH sessions without needing kernel-level access.
So I think this bug is related to user-mode because it's about the application (QEMU) using libraries and encountering issues during compilation. It doesn't seem to involve system-level components like hardware or kernel operations.
</think>
user
|