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
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
|
peripherals: 0.801
hypervisor: 0.795
user-level: 0.748
permissions: 0.737
risc-v: 0.694
KVM: 0.682
graphic: 0.672
mistranslation: 0.669
network: 0.666
vnc: 0.624
VMM: 0.623
architecture: 0.617
arm: 0.612
device: 0.604
performance: 0.602
assembly: 0.601
boot: 0.584
files: 0.578
register: 0.571
ppc: 0.568
kernel: 0.563
socket: 0.560
virtual: 0.554
semantic: 0.550
x86: 0.540
PID: 0.533
TCG: 0.529
debug: 0.516
i386: 0.346
Reading register at offset. It is not fully implemented warning make VM impossible to use
Hi,
Since this commit:
https://github.com/qemu/qemu/commit/bc0f0674f037a01f2ce0870ad6270a356a7a8347
We can no longer use the IOSvL2 image from Cisco. The problem is we got a lot of warning message saying:
e1000: Reading register at offset: 0x00002410. It is not fully implemented.
User got so much of this warning that they can't use the VM.
Thanks for the help
On Fri, Mar 17, 2017 at 09:47:14AM -0000, Julien Duponchelle wrote:
> Hi,
>
> Since this commit:
> https://github.com/qemu/qemu/commit/bc0f0674f037a01f2ce0870ad6270a356a7a8347
>
> We can no longer use the IOSvL2 image from Cisco. The problem is we got a lot of warning message saying:
> e1000: Reading register at offset: 0x00002410. It is not fully implemented.
>
> User got so much of this warning that they can't use the VM.
CCing the author and maintainers.
DBGOUT() is compiled in by default. Warnings that can be triggered at a
high rate by the guest should be off by default or use a
printf_once()-style macro so they are only printed once and not again.
Leonid: do you want to adjust e1000 DBGOUT() usage to avoid printing
guest-triggerable messages by default?
Stefan
On 20 March 2017 at 14:20, Stefan Hajnoczi <email address hidden> wrote:
> On Fri, Mar 17, 2017 at 09:47:14AM -0000, Julien Duponchelle wrote:
>> Hi,
>>
>> Since this commit:
>> https://github.com/qemu/qemu/commit/bc0f0674f037a01f2ce0870ad6270a356a7a8347
>>
>> We can no longer use the IOSvL2 image from Cisco. The problem is we got a lot of warning message saying:
>> e1000: Reading register at offset: 0x00002410. It is not fully implemented.
>>
>> User got so much of this warning that they can't use the VM.
>
> CCing the author and maintainers.
>
> DBGOUT() is compiled in by default. Warnings that can be triggered at a
> high rate by the guest should be off by default or use a
> printf_once()-style macro so they are only printed once and not again.
>
> Leonid: do you want to adjust e1000 DBGOUT() usage to avoid printing
> guest-triggerable messages by default?
If we want to report "whoops, we don't implement this yet" messages then
the recommended way to do that is
qemu_log_mask(LOG_UNIMP, "....");
(these are not reported by default but only if the user asks for them.)
thanks
-- PMM
On 2017年03月20日 22:58, Peter Maydell wrote:
> On 20 March 2017 at 14:20, Stefan Hajnoczi <email address hidden> wrote:
>> On Fri, Mar 17, 2017 at 09:47:14AM -0000, Julien Duponchelle wrote:
>>> Hi,
>>>
>>> Since this commit:
>>> https://github.com/qemu/qemu/commit/bc0f0674f037a01f2ce0870ad6270a356a7a8347
>>>
>>> We can no longer use the IOSvL2 image from Cisco. The problem is we got a lot of warning message saying:
>>> e1000: Reading register at offset: 0x00002410. It is not fully implemented.
>>>
>>> User got so much of this warning that they can't use the VM.
>> CCing the author and maintainers.
>>
>> DBGOUT() is compiled in by default. Warnings that can be triggered at a
>> high rate by the guest should be off by default or use a
>> printf_once()-style macro so they are only printed once and not again.
>>
>> Leonid: do you want to adjust e1000 DBGOUT() usage to avoid printing
>> guest-triggerable messages by default?
> If we want to report "whoops, we don't implement this yet" messages then
> the recommended way to do that is
> qemu_log_mask(LOG_UNIMP, "....");
>
> (these are not reported by default but only if the user asks for them.)
>
> thanks
> -- PMM
>
I don't see a reason that enabling E1000E_DEBUG by default. How about
just disable it by default?
Thanks
I sent a patch to the mailing list:
http://lists.nongnu.org/archive/html/qemu-devel/2017-05/msg01294.html
I think this has been fixed by:
https://git.qemu.org/?p=qemu.git;a=commitdiff;h=b4053c64833
|