From: Stefan Hajnoczi <stefanha@gmail.com>
To: Bug 1673722 <1673722@bugs.launchpad.net>
Cc: qemu-devel@nongnu.org, Jason Wang <jasowang@redhat.com>,
Dmitry Fleytman <dmitry.fleytman@ravellosystems.com>,
Leonid Bloch <leonid.bloch@ravellosystems.com>
Subject: Re: [Qemu-devel] [Bug 1673722] [NEW] Reading register at offset. It is not fully implemented warning make VM impossible to use
Date: Mon, 20 Mar 2017 14:20:57 +0000 [thread overview]
Message-ID: <20170320142057.GZ17887@stefanha-x1.localdomain> (raw)
In-Reply-To: <20170317094714.32220.9387.malonedeb@chaenomeles.canonical.com>
[-- Attachment #1: Type: text/plain, Size: 807 bytes --]
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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
next prev parent reply other threads:[~2017-03-20 14:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-17 9:47 [Qemu-devel] [Bug 1673722] [NEW] Reading register at offset. It is not fully implemented warning make VM impossible to use Julien Duponchelle
2017-03-20 14:20 ` Stefan Hajnoczi [this message]
2017-03-20 14:58 ` Peter Maydell
2017-03-21 5:18 ` Jason Wang
2017-05-05 13:08 ` [Qemu-devel] [Bug 1673722] " Julien Duponchelle
2020-11-08 9:21 ` Thomas Huth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170320142057.GZ17887@stefanha-x1.localdomain \
--to=stefanha@gmail.com \
--cc=1673722@bugs.launchpad.net \
--cc=dmitry.fleytman@ravellosystems.com \
--cc=jasowang@redhat.com \
--cc=leonid.bloch@ravellosystems.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).