From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:58334) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1R4Jkz-0001Fq-HS for qemu-devel@nongnu.org; Thu, 15 Sep 2011 17:46:06 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1R4Jkx-0006SC-TO for qemu-devel@nongnu.org; Thu, 15 Sep 2011 17:46:05 -0400 Received: from indium.canonical.com ([91.189.90.7]:43437) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1R4Jkx-0006S4-PH for qemu-devel@nongnu.org; Thu, 15 Sep 2011 17:46:03 -0400 Received: from loganberry.canonical.com ([91.189.90.37]) by indium.canonical.com with esmtp (Exim 4.71 #1 (Debian)) id 1R4Jkw-00037c-R0 for ; Thu, 15 Sep 2011 21:46:02 +0000 Received: from loganberry.canonical.com (localhost [127.0.0.1]) by loganberry.canonical.com (Postfix) with ESMTP id 9B4F72E8317 for ; Thu, 15 Sep 2011 21:46:02 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Date: Thu, 15 Sep 2011 19:37:36 -0000 From: Rick Vernam <818673@bugs.launchpad.net> Sender: bounces@canonical.com References: <20110730230157.13425.3564.malonedeb@chaenomeles.canonical.com> <20110914194209.31176.83747.malone@soybean.canonical.com> <201109141630.11577.rickv@hobi.com> <201109151123.53824.rickv@hobi.com> Message-Id: <201109151437.36302.rickv@hobi.com> Errors-To: bounces@canonical.com Subject: Re: [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 On Thursday 15 September 2011 11:23:53 Rick Vernam wrote: > On Wednesday 14 September 2011 16:30:11 Rick Vernam wrote: > > On Wednesday 14 September 2011 14:42:09 vrozenfe wrote: > > > Thank you, Rick. > > > = > > > Could you help me to narrow this problem down? > > = > > Absolutely. > > = > > > As I see, you have three virtio drivers installed on your system - > > > block, net, 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 from the other. If you > > > can, please try running only one virtio device every time to see which > > > driver sends incorrect scatter/gather list element to QEMU. > > = > > Sure, no problem. I'll have that in the next few days. > = > I started qemu without any of the virt-serial stuff, specfically: > 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,aio=3Dnative -m 1536 -name= WinXP > -net nic,model=3Dvirtio -net user -localtime -usb -vga qxl -spice > port=3D1234,disable-ticketing -monitor stdio > = > It's been running for around 2 hours and no crash yet. So without virt-serial, the machine ran until I rebooted the guest OS, then = crashed with the same error message. Without virt-serial it seemed to be = stable so long as it was just left running. Now I'll run it without virt-net, and let you know how that goes. > = > Thanks, > -Rick > = > > > Another question. You said, the problem happens after every second or > > > third restart. Do you shutdown your VM, or just restart it? > > = > > Have to shut down the VM guest so that the qemu process exits. > > = > > > How does it work > > > after going through several hibernate/resume, and/or suspend/resume > > > cycles. > > = > > I often will suspend with or without pausing qemu (via monitor commands > > 'stop' and 'cont'). I have never experienced any problem with the qemu > > process that was running prior to the suspend. > > = > > > Best regards, > > > Vadim. > > = > > Thanks, > > -Rik -- = 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