From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:48052) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QiVjM-0003ao-2l for qemu-devel@nongnu.org; Sun, 17 Jul 2011 14:06:17 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QiVjK-0007Zv-OB for qemu-devel@nongnu.org; Sun, 17 Jul 2011 14:06:16 -0400 Received: from mail-wy0-f173.google.com ([74.125.82.173]:62604) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QiVjK-0007Zr-Jj for qemu-devel@nongnu.org; Sun, 17 Jul 2011 14:06:14 -0400 Received: by wyf28 with SMTP id 28so1924857wyf.4 for ; Sun, 17 Jul 2011 11:06:13 -0700 (PDT) Message-ID: <4E232493.4060500@gmail.com> Date: Sun, 17 Jul 2011 20:06:11 +0200 From: =?ISO-8859-1?Q?St=E9phanie_Ouillon?= MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="------------040706090106070802060900" Subject: [Qemu-devel] error "kvm: virtio: trying to map MMIO memory" List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org This is a multi-part message in MIME format. --------------040706090106070802060900 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Hello, I am porting virtio device drivers for DragonFly BSD for a GSoC project. [1] I have been facing a problem for 3-4 days with my virtio network device driver in qemu: when I load the driver, I get the following error: kvm: virtio: trying to map MMIO memory And then the machine crashes immediately (I started the vm in a screen to see this message). It seems to be linked with the call of a bus_space_write_2 function [2] inside a virtio_enqueue_commit function in virtio.c [3]. But without more information about this type of error message (I found some patches or bug reports on the net, but I am not sure they match in my case), I found it difficult to locate it. Would anybody have a clue about what kind of bug would provoke this error in qemu ? Thank you ! Stéphanie Ouillon [1] http://github.com/arroway/virtio_DragonFlyBSD/tree/dev-net/net [2] source code in DragonFly BSD http://fxr.watson.org/fxr/source/cpu/i386/include/bus_at386.h?v=DFBSD;im=bigexcerpts#L887 [3] at l.465: http://github.com/arroway/virtio_DragonFlyBSD/blob/dev-net/virtio.c --------------040706090106070802060900 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hello,

I am porting virtio device drivers for DragonFly BSD for a GSoC project. [1]

I have been facing a problem for 3-4 days with my virtio network device driver in qemu: when I load the driver, I get the following error:
kvm: virtio: trying to map MMIO memory

And then the machine crashes immediately (I started the vm in a screen to see this message).

It seems to be linked with the call of a bus_space_write_2 function [2] inside a virtio_enqueue_commit function in virtio.c [3]. But without more information about this type of error message (I found some patches or bug reports on the net, but I am not sure they match in my case), I found it difficult to locate it.

Would anybody have a clue about what kind of bug would provoke this error in qemu ?


Thank you !


Stéphanie Ouillon


[1] http://github.com/arroway/virtio_DragonFlyBSD/tree/dev-net/net
[2] source code in DragonFly BSD http://fxr.watson.org/fxr/source/cpu/i386/include/bus_at386.h?v=DFBSD;im=bigexcerpts#L887
[3] at l.465: http://github.com/arroway/virtio_DragonFlyBSD/blob/dev-net/virtio.c

--------------040706090106070802060900--