blob: bbe5d65f165ea982497d6eeb3a5271ea28eb469b (
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
|
files: 0.912
x86: 0.895
graphic: 0.881
network: 0.859
performance: 0.856
semantic: 0.850
device: 0.840
ppc: 0.829
debug: 0.790
architecture: 0.782
hypervisor: 0.752
kernel: 0.732
socket: 0.720
user-level: 0.706
vnc: 0.706
PID: 0.667
register: 0.656
permissions: 0.611
i386: 0.599
peripherals: 0.598
assembly: 0.589
VMM: 0.540
arm: 0.536
risc-v: 0.493
mistranslation: 0.452
TCG: 0.437
KVM: 0.378
boot: 0.332
virtual: 0.283
qemu doesn't process -object secret when read from a config file
Description of problem:
Qemu doesn't process -object secret lines when read from a config file. This results in the new spice password-secret option failing with error: No secret with id '\<theid\>'
Steps to reproduce:
1. Create a password file
```
printf "password" > passfile.pw
```
2. Start qemu with command line options and also write to a config file
```
qemu-system-x86_64 \
-object secret,id=spicepwd,format=raw,file=passfile.pw \
-spice port=5901,password-secret=spicepwd \
-writeconfig qemu.cfg
```
3. Optional: Connect using spice client and password: "password"
4. Exit qemu and cat qemu.cfg and verify it looks okay with equivalent options to what was specified on the command line
5. Now attempt to start qemu and read the options using the config file
```
qemu-system-x86_64 -readconfig qemu.cfg
```
6. This fails with an error:
```
qemu-system-x86_64: No secret with id 'spicepwd'
```
|