qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Bug 818673 <818673@bugs.launchpad.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Bug 818673] Re: virtio: trying to map MMIO memory
Date: Sun, 14 Aug 2011 16:00:06 +0100	[thread overview]
Message-ID: <CAJSP0QXdn0Rx==eizViRYNV_oDPXhYbCBFPrccTxUO3WtQGHtQ@mail.gmail.com> (raw)
In-Reply-To: <20110814061120.13531.37210.malone@soybean.canonical.com>

On Sun, Aug 14, 2011 at 7:11 AM, Rick Vernam <818673@bugs.launchpad.net> wrote:
> So that would point to virtio.  This appears to be the place for virtio bugs, correct?
> Should I be doing anything to help usher this along?

Either we need to help Vadim reproduce this so he can take a look.
Vadim: were you able to reproduce this?

Or someone interested in Windows driver debugging can see if they can
debug this.  The symptom is that the guest driver is placing invalid
descriptors into the vring.  QEMU tries to map the memory and finds
the address is in a memory-mapped I/O region instead of a RAM region.
Normally the vring descriptors only point into RAM, so this is a guest
driver bug where the vring is being corrupted somehow.  If anyone
wants to take a look I can try to help guide them along the
virtio-specifics.

Stefan

  reply	other threads:[~2011-08-14 15:00 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-30 23:01 [Qemu-devel] [Bug 818673] [NEW] virtio: trying to map MMIO memory Rick Vernam
2011-07-31 17:54 ` Stefan Hajnoczi
2011-07-31 18:43   ` Vadim Rozenfeld
2011-08-02 14:20 ` [Qemu-devel] [Bug 818673] " Rick Vernam
2011-08-04 21:35 ` David Rando
2011-08-05  3:10 ` Rick Vernam
2011-08-05 16:11 ` Rick Vernam
2011-08-13  4:38 ` Rick Vernam
2011-08-13 12:23 ` David Rando
2011-08-14  6:11 ` Rick Vernam
2011-08-14 15:00   ` Stefan Hajnoczi [this message]
2011-08-25 14:53 ` David Rando
2011-08-25 15:54   ` Stefan Hajnoczi
2011-08-25 19:33     ` Vadim Rozenfeld
2011-09-06 15:08 ` dx-vmonroig
2011-09-12 17:49 ` Rick Vernam
2011-09-13 16:27 ` vrozenfe
2011-09-13 23:26 ` Rick Vernam
2011-09-14 15:43 ` Rick Vernam
2011-09-14 17:52 ` Rick Vernam
2011-09-14 19:42 ` vrozenfe
2011-09-14 21:30   ` Rick Vernam
2011-09-15 16:23     ` Rick Vernam
2011-09-15 19:37       ` Rick Vernam
2011-09-16  8:52         ` hkran
2011-09-16 17:42           ` Rick Vernam
2011-09-16 19:31             ` Rick Vernam
2011-09-22 19:10             ` Rick Vernam
2011-09-23 19:07               ` Alon Levy
2011-09-23 19:49                 ` Rick Vernam
2011-09-15 19:55 ` vrozenfe
2011-09-26 16:38 ` Rick Vernam
2011-09-29  2:07 ` Rick Vernam
2011-12-29 20:52 ` Arequipeno
2011-12-30 16:00 ` Ian Pilcher
2011-12-30 16:31 ` Rick Vernam
2012-01-24 16:35 ` Vitalis
2012-01-24 16:48 ` Vitalis
2012-01-24 19:25   ` Rick Vernam
2012-02-02  9:12 ` Mike Cao
2012-02-02 17:31 ` Rick Vernam
2012-02-02 17:40 ` Rick Vernam
2012-02-08 11:18 ` Vitalis
2012-02-16 17:03 ` vrozenfe
2012-02-17  7:10 ` Vitalis
2012-02-17  7:58 ` Alon Levy
2012-02-17  9:13 ` vrozenfe
2012-02-17  9:14 ` vrozenfe
2016-10-20 21:15 ` 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='CAJSP0QXdn0Rx==eizViRYNV_oDPXhYbCBFPrccTxUO3WtQGHtQ@mail.gmail.com' \
    --to=stefanha@gmail.com \
    --cc=818673@bugs.launchpad.net \
    --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).