From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:59542) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1R3vUF-0000hS-9T for qemu-devel@nongnu.org; Wed, 14 Sep 2011 15:51:16 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1R3vUA-0006Nk-2A for qemu-devel@nongnu.org; Wed, 14 Sep 2011 15:51:11 -0400 Received: from indium.canonical.com ([91.189.90.7]:53790) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1R3vU9-0006NO-UJ for qemu-devel@nongnu.org; Wed, 14 Sep 2011 15:51:06 -0400 Received: from loganberry.canonical.com ([91.189.90.37]) by indium.canonical.com with esmtp (Exim 4.71 #1 (Debian)) id 1R3vU9-0006Pp-8P for ; Wed, 14 Sep 2011 19:51:05 +0000 Received: from loganberry.canonical.com (localhost [127.0.0.1]) by loganberry.canonical.com (Postfix) with ESMTP id 3EADF2E81AE for ; Wed, 14 Sep 2011 19:51:05 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Date: Wed, 14 Sep 2011 19:42:09 -0000 From: vrozenfe <818673@bugs.launchpad.net> Sender: bounces@canonical.com References: <20110730230157.13425.3564.malonedeb@chaenomeles.canonical.com> Message-Id: <20110914194209.31176.83747.malone@soybean.canonical.com> Errors-To: bounces@canonical.com Subject: [Qemu-devel] [Bug 818673] Re: virtio: trying to map MMIO memory Reply-To: Bug 818673 <818673@bugs.launchpad.net> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Thank you, Rick. Could you help me to narrow this problem down? As I see, you have three virtio drivers installed on your system - block, n= et, and virtio serial. Technically, anyone of them can create "trying to map MMIO memory" problem. = The best way to find a buggy driver ( or drivers) will be to isolate one fr= om the other. If you can, please try running only one virtio device every time to see whi= ch driver sends incorrect scatter/gather list element to QEMU. Another question. You said, the problem happens after every second or third= restart. Do you shutdown your VM, or just restart it? How does it work after going = through several hibernate/resume, and/or suspend/resume cycles. Best regards, Vadim. -- = You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/818673 Title: virtio: trying to map MMIO memory Status in QEMU: New Bug description: Qemu host is Core i7, running Linux. Guest is Windows XP sp3. Often, qemu will crash shortly after starting (1-5 minutes) with a statem= ent "qemu-system-x86_64: virtio: trying to map MMIO memory" This has occured with qemu-kvm 0.14, qemu-kvm 0.14.1, qemu-0.15.0-rc0 and= qemu 0.15.0-rc1. Qemu is started as such: qemu-system-x86_64 -cpu host -enable-kvm -pidfile /home/rick/qemu/hds/wxp= .pid -drive file=3D/home/rick/qemu/hds/wxp.raw,if=3Dvirtio -m 768 -name Win= XP -net nic,model=3Dvirtio -net user -localtime -usb -vga qxl -device virti= o-serial -chardev spicevmc,name=3Dvdagent,id=3Dvdagent -device virtserialpo= rt,chardev=3Dvdagent,name=3Dcom.redhat.spice.0 -spice port=3D1234,disable-t= icketing -daemonize -monitor telnet:localhost:12341,server,nowait The WXP guest has virtio 1.1.16 drivers for net and scsi, and the most cu= rrent spice binaries from spice-space.org. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/818673/+subscriptions