qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [Bug 818673] Re: virtio: trying to map MMIO memory


From: Rick Vernam
Subject: Re: [Qemu-devel] [Bug 818673] Re: virtio: trying to map MMIO memory
Date: Thu, 15 Sep 2011 19:37:36 -0000

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=/home/rick/qemu/hds/wxp.raw,if=virtio,aio=native -m 1536 -name WinXP
> -net nic,model=virtio -net user -localtime -usb -vga qxl -spice
> port=1234,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 statement 
"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=/home/rick/qemu/hds/wxp.raw,if=virtio -m 768 -name WinXP -net 
nic,model=virtio -net user -localtime -usb -vga qxl -device virtio-serial 
-chardev spicevmc,name=vdagent,id=vdagent -device 
virtserialport,chardev=vdagent,name=com.redhat.spice.0 -spice 
port=1234,disable-ticketing -daemonize -monitor 
telnet:localhost:12341,server,nowait
  The WXP guest has virtio 1.1.16 drivers for net and scsi, and the most 
current spice binaries from spice-space.org.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/818673/+subscriptions



reply via email to

[Prev in Thread] Current Thread [Next in Thread]