1 files changed, 143 insertions, 0 deletions
diff --git a/results/classifier/118/peripherals/1673722 b/results/classifier/118/peripherals/1673722
new file mode 100644
index 000000000..1da1d5b12
--- /dev/null
+++ b/results/classifier/118/peripherals/1673722
@@ -0,0 +1,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
+
+