blob: 5e1a247d9f20c7b097a049b54c929ca116b127b7 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
|
socket: 0.988
device: 0.988
permissions: 0.951
debug: 0.934
peripherals: 0.929
files: 0.908
ppc: 0.904
architecture: 0.903
graphic: 0.896
performance: 0.894
register: 0.890
boot: 0.842
user-level: 0.833
network: 0.774
kernel: 0.771
PID: 0.761
semantic: 0.700
hypervisor: 0.667
vnc: 0.649
virtual: 0.638
arm: 0.610
mistranslation: 0.539
TCG: 0.536
x86: 0.532
risc-v: 0.494
VMM: 0.431
assembly: 0.394
KVM: 0.378
i386: 0.254
qemu-system-aarch64: tpm-emulator: TPM result for CMD_INIT: 0x9 operation failed
Description of problem:
I'm using QEMU (compile from the latest source code) to simulate a tpm2 device with the above command, it just returns an error message:
```
qemu-system-aarch64: tpm-emulator: TPM result for CMD_INIT: 0x9 operation failed
```
swtpm start command:
```
TPMSOCK=/tmp/swtpm-sock$$
swtpm socket --tpm2 -t -d --tpmstate dir=$PWD/tpm --ctrl type=unixio,path=$TPMSOCK --log level=20
```
swtpm version:
```
TPM emulator version 0.7.3, Copyright (c) 2014-2021 IBM Corp.
```
Also tried the latest swtpm, encountered the same error.
swtpm log (0.7.3):
```
swtpm: Data client disconnected
swtpm: SWTPM_NVRAM_Lock_Dir: Could not open lockfile: Permission denied
swtpm: Error: Could not initialize libtpms.
swtpm: Error: Could not initialize the TPM
swtpm: Data client disconnected
```
swtpm log (0.10.0):
```
swtpm: SWTPM_NVRAM_StoreData: Error (fatal) opening tpm/TMP2-00.permall for write failed, Permission denied
swtpm: SWTPM_NVRAM_Lock_Dir: Could not open lockfile: Permission denied
swtpm: Error: Could not initialize the TPM
swtpm: Data client disconnected
```
Any clues about this error? Best regrads.
Steps to reproduce:
Refer to [Description of problem](#description-of-problem)
Additional information:
|