blob: 380fbc192606ccf4874cbf5a80d4cf7e6f9a4217 (
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
|
graphic: 0.954
device: 0.808
x86: 0.733
mistranslation: 0.729
debug: 0.661
architecture: 0.643
KVM: 0.629
network: 0.605
performance: 0.522
vnc: 0.478
semantic: 0.453
i386: 0.450
ppc: 0.439
hypervisor: 0.359
PID: 0.342
kernel: 0.332
boot: 0.331
socket: 0.325
peripherals: 0.319
register: 0.285
arm: 0.196
files: 0.180
permissions: 0.151
virtual: 0.144
user-level: 0.144
assembly: 0.131
VMM: 0.129
TCG: 0.105
risc-v: 0.067
"-set device" doesn't work with device specified in json
Description of problem:
The above QEMU command line results in:
```
qemu-system-x86_64: -set device.ua-igd.x-igd-gms=1: there is no device "ua-igd" defined
```
While the following command works:
```
qemu-system-x86_64 -accel kvm -m 8192 -nodefaults -display none -net none -device vfio-pci,host=0000:00:02.0,id=ua-igd -set device.ua-igd.x-igd-gms=1
```
libvirt has moved to the json device specification, therefore I can no longer associate use a <qemu:commandline> section to set driver options for a specific device with this broken id association.
Steps to reproduce:
1. Create a device with an ID and use -set device.$ID to set a driver option for the device
2. Note failure when using json device format vs legacy device specification
3. Profit
Additional information:
|