blob: 264ed1399c22c90271e891ffeff4d5bc36248130 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
|
<think>
Okay, so I'm trying to figure out whether this TPM2 configuration issue in QEMU is a user-mode or system-mode problem. Let me start by understanding the context.
The report mentions that swtpm provides several interfaces, including TCP, which is convenient for testing without needing root permissions. The main request is to have QEMU work with TPM devices emulated via TCP.
I know that TPM (Trusted Platform Module) is a hardware component used for secure storage of cryptographic keys and other sensitive data. Emulating it in software allows testing without physical hardware, which is great.
Now, swtpm can connect via TCP, so the emulator acts like a server over the network, perhaps on localhost. QEMU would need to connect to this TCP interface as a client. Since the user doesn't need root permissions for this setup, it's probably intended for regular users without elevated privileges.
In QEMU, when you run it as a normal user, it typically uses user-mode networking by default unless specified otherwise. The fact that the TCP connection doesn't require root suggests it's using standard ports and user-level processes.
So, if QEMU is trying to connect to a TPM emulated via TCP without needing system-level privileges, this falls under user-mode. User-mode processes run with limited permissions and don't interact directly with hardware or core OS components, which matches the scenario here.
Therefore, I think the bug report is related to user-mode.
</think>
user
|