From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([140.186.70.92]:34695)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <stefanha@gmail.com>) id 1QscAb-0002KU-3E
	for qemu-devel@nongnu.org; Sun, 14 Aug 2011 11:00:09 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <stefanha@gmail.com>) id 1QscAZ-00087o-W2
	for qemu-devel@nongnu.org; Sun, 14 Aug 2011 11:00:09 -0400
Received: from mail-yx0-f173.google.com ([209.85.213.173]:52038)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <stefanha@gmail.com>) id 1QscAZ-00087M-Sc
	for qemu-devel@nongnu.org; Sun, 14 Aug 2011 11:00:07 -0400
Received: by yxt3 with SMTP id 3so3248573yxt.4
	for <qemu-devel@nongnu.org>; Sun, 14 Aug 2011 08:00:06 -0700 (PDT)
MIME-Version: 1.0
In-Reply-To: <20110814061120.13531.37210.malone@soybean.canonical.com>
References: <20110730230157.13425.3564.malonedeb@chaenomeles.canonical.com>
	<20110814061120.13531.37210.malone@soybean.canonical.com>
Date: Sun, 14 Aug 2011 16:00:06 +0100
Message-ID: <CAJSP0QXdn0Rx==eizViRYNV_oDPXhYbCBFPrccTxUO3WtQGHtQ@mail.gmail.com>
From: Stefan Hajnoczi <stefanha@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [Qemu-devel] [Bug 818673] Re: virtio: trying to map MMIO memory
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Bug 818673 <818673@bugs.launchpad.net>
Cc: qemu-devel@nongnu.org

On Sun, Aug 14, 2011 at 7:11 AM, Rick Vernam <818673@bugs.launchpad.net> wr=
ote:
> So that would point to virtio. =A0This 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