blob: 4f4c402a9c9ac16e4bcee39676589c6d20f64091 (
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
|
graphic: 0.725
device: 0.648
PID: 0.550
network: 0.541
architecture: 0.449
semantic: 0.443
socket: 0.364
mistranslation: 0.360
performance: 0.345
ppc: 0.337
kernel: 0.287
vnc: 0.277
register: 0.242
risc-v: 0.234
debug: 0.214
boot: 0.210
TCG: 0.167
VMM: 0.145
user-level: 0.138
arm: 0.133
files: 0.123
i386: 0.123
hypervisor: 0.113
x86: 0.112
peripherals: 0.099
permissions: 0.081
assembly: 0.072
virtual: 0.066
KVM: 0.041
qga fail to start when pidfile path is missing
The qga main program has two parameters: "--logfile" and "--pidfile" which specifies the paths to the logfile and pidfile. It assumes that the paths exit in the running OS but if not, the qga will fail to start.I think qga should create the missing paths.
I found this bug exits in several Linux distributions including Ubuntu 14, Cent-OS 6 and 7 when the original and the latest master qga applies. I have a patch which can fix it. Should I patch it to the QEMU master branch?
Patches should be sent to the qemu-devel mailing list for discussion and inclusion. Did you ever send your patch to the list?
[Expired for QEMU because there has been no activity for 60 days.]
|
