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

[Arequipeno <818673@bugs.launchpad.net>]

I've been dealing with this bug for some time on Fedora.  Until
recently, I was using the VirtIO drivers from RHEV 2.2, which don't
suffer from this problem.  As of Fedora 16, however, that isn't an
option, because they cause the guest to blue-screen early in the boot
process.

So ... I've been doing some more testing with the following setup:

  Host:
    Intel DQ67SW motherboard with Q67 chipset (including IOMMU)
    BIOS version SWQ6710H.86A.0050.2011.0401.1409 (release date 04/01/2011)
    Intel Core i7 2600, 4-cores, 8 threads, 3.4 GHz
    16GB memory
    Fedora 15 64-bit, fully updated including updates-testing repo
      qemu-kvm-0.14.0-8.fc15.x86_64
      libvirt-0.8.8-7.fc15.x86_64
      kernel-2.6.41.6-1.fc15.x86_64

  Guest:
    Windows 7 Professional 32-bit, fully updated
    2 VCPUs
    3.5GB memory
    Red Hat VirtIO Ethernet Adapter driver version 6.0.209.605 (9/20/2010)
    Red Hat VirtIO SCSI Controller driver version 6.0.0.10 (9/20/2010)
    (No VirtIO serial ports or channels defined)

(The VirtIO drivers are from http://alt.fedoraproject.org/pub/alt
/virtio-win/latest/images/.)

I have determined that disabling the Intel IOMMU has no effect; the
problem still occurs.

Perhaps more interestingly, it seems that the problem only occurs when I
am using the VirtIO SCSI *and* the VirtIO Ethernet drivers.  It seems
that the problem does not occur if I only use one of the drivers; an IDE
disk with a VirtIO NIC seems to be stable, as does a VirtIO disk with an
e1000 NIC.

Now to the big question ... what the heck can be done to get this problem fixed?  I hope that everyone agrees that it's totally unacceptable for a problem like this to sit unfixed for so long.  I am more than willing to test any patches, enable
debugging, etc.; just tell me what to do.

Thanks!

-- 
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