blob: d1afc690dd49858a75f5bda87794ea8cf1da95cd (
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
70
|
vnc: 0.974
instruction: 0.937
network: 0.915
mistranslation: 0.912
semantic: 0.911
device: 0.902
other: 0.900
graphic: 0.831
socket: 0.805
assembly: 0.794
KVM: 0.762
boot: 0.675
Unnecessary events option of the trace argument with UST backend
When running configure with the --enable-trace-backends=ust option the user should not have to specify a the "events" and "file" options because they are not used with that tracing framework.
Right now, in order the use this option the need to specify a dummy events file.
This fails:
$> qemu-system-x86_64 -hda debian_wheezy_amd64_standard.qcow2 -trace -m 512
qemu-system-x86_64: -trace -m: Invalid parameter '-m'
This works:
$> qemu-system-x86_64 -hda debian_wheezy_amd64_standard.qcow2 -trace events=dummy-events.txt -m 512
VNC server running on `127.0.0.1:5900'
I am using version:
$> qemu-system-x86_64 --version
QEMU emulator version 2.1.90, Copyright (c) 2003-2008 Fabrice Bellard
On Wed, Nov 12, 2014 at 04:01:38PM -0000, Francis Deslauriers wrote:
> When running configure with the --enable-trace-backends=ust option and compiling.
> The user should not have to specify a the "events" and "file" options because they are not used with that tracing framework.
>
> Right now, in order the use this option the need to specify a dummy
> events file.
>
> This fails:
> $> qemu-system-x86_64 -hda debian_wheezy_amd64_standard.qcow2 -trace -m 512
> qemu-system-x86_64: -trace -m: Invalid parameter '-m'
>
> This works:
> $> qemu-system-x86_64 -hda debian_wheezy_amd64_standard.qcow2 -trace events=dummy-events.txt -m 512
> VNC server running on `127.0.0.1:5900'
>
> I am using version:
> $> qemu-system-x86_64 --version
> QEMU emulator version 2.1.90, Copyright (c) 2003-2008 Fabrice Bellard
What happens when you pass no -trace option?
Stefan
It works without the -trace option.
Want I meant with this post is that the "events" argument of the "-trace" option has no effect in the case of using LTTng UST as the tracing backend because the events are enabled from the LTTng tracer itself.
Is there some way I can make an argument optional or conditional to a tracing framework?
Thanks,
Francis
The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to "Incomplete" now.
If you still think this bug report here is valid, then please switch the state back to "New" within the next 60 days, otherwise this report will be marked as "Expired". Or mark it as "Fix Released" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience.
[Expired for QEMU because there has been no activity for 60 days.]
|