Bug 1845758 - qemu core dumped: qemu-kvm: /builddir/build/BUILD/qemu-4.2.0/memory.c:1928: memory_region_notify_one: Assertion `entry->iova >= notifier->start && entry_end <= notifier->end' failed.
Summary: qemu core dumped: qemu-kvm: /builddir/build/BUILD/qemu-4.2.0/memory.c:1928: m...
Alias: None
Product: Red Hat Enterprise Linux Advanced Virtualization
Classification: Red Hat
Component: qemu-kvm
Version: 8.3
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: 8.3
Assignee: Eugenio Pérez Martín
QA Contact: Lei Yang
Depends On: 1843852
Blocks: 1897025
TreeView+ depends on / blocked
Reported: 2020-06-10 01:59 UTC by Lei Yang
Modified: 2021-05-25 06:42 UTC (History)
10 users (show)

Fixed In Version: qemu-kvm-5.2.0-3.module+el8.4.0+9499+42e58f08
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1843852
Last Closed: 2021-05-25 06:42:15 UTC
Type: Bug
Target Upstream Version:

Attachments (Terms of Use)

Comment 13 Lei Yang 2021-01-20 04:55:45 UTC
==Verified with qemu-kvm-5.2.0-3.module+el8.4.0+9499+42e58f08.x86_64

Test Version:

1. Boot guest with iommu-enabled virtio-net-pci device
/usr/libexec/qemu-kvm \
-name 'avocado-vt-vm1'  \
-sandbox on  \
-machine q35,kernel-irqchip=split \
-device pcie-root-port,id=pcie-root-port-0,multifunction=on,bus=pcie.0,addr=0x1,chassis=1 \
-device pcie-pci-bridge,id=pcie-pci-bridge-0,addr=0x0,bus=pcie-root-port-0  \
-nodefaults \
-device intel-iommu,intremap=on,device-iotlb=on \
-device VGA,bus=pcie.0,addr=0x2 \
-m 26624  \
-smp 12,maxcpus=12,cores=6,threads=1,dies=1,sockets=2  \
-cpu 'Skylake-Server',+kvm_pv_unhalt \
-device pcie-root-port,id=pcie-root-port-1,port=0x1,addr=0x1.0x1,bus=pcie.0,chassis=2 \
-device qemu-xhci,id=usb1,bus=pcie-root-port-1,addr=0x0 \
-device usb-tablet,id=usb-tablet1,bus=usb1.0,port=1 \
-device pcie-root-port,id=pcie-root-port-2,port=0x2,addr=0x1.0x2,bus=pcie.0,chassis=3 \
-device virtio-scsi-pci,id=virtio_scsi_pci0,bus=pcie-root-port-2,addr=0x0,disable-legacy=on,disable-modern=off,iommu_platform=on,ats=on \
-blockdev node-name=file_image1,driver=file,auto-read-only=on,discard=unmap,aio=threads,filename=/home/kvm_autotest_root/images/rhel79-64-virtio-scsi.qcow2,cache.direct=on,cache.no-flush=off \
-blockdev node-name=drive_image1,driver=qcow2,read-only=off,cache.direct=on,cache.no-flush=off,file=file_image1 \
-device scsi-hd,id=image1,drive=drive_image1,write-cache=on \
-device pcie-root-port,id=pcie-root-port-3,port=0x3,addr=0x1.0x3,bus=pcie.0,chassis=4 \
-device virtio-net-pci,mac=9a:76:08:ad:07:7a,id=id46sgOh,netdev=idUpTZ4r,bus=pcie-root-port-3,addr=0x0,disable-legacy=on,disable-modern=off,iommu_platform=on,ats=on  \
-netdev tap,id=idUpTZ4r,vhost=on,vhostforce=on  \
-vnc :0  \
-rtc base=utc,clock=host,driftfix=slew  \
-boot menu=off,order=cdn,once=c,strict=off \
-enable-kvm \
-device pcie-root-port,id=pcie_extra_root_port_0,multifunction=on,bus=pcie.0,addr=0x3,chassis=5 \
-monitor stdio \

2.Add intel_iommu=on in guest kernel line. Then reboot guest.
# grubby --update-kernel=`grubby --default-kernel` --args="intel_iommu=on"
# shudown -r now

3.Guest reboot successfully, ping out from guest.
# ping  -c 10
PING ( 56(84) bytes of data.
64 bytes from icmp_seq=1 ttl=64 time=0.340 ms
64 bytes from icmp_seq=2 ttl=64 time=0.465 ms
64 bytes from icmp_seq=3 ttl=64 time=0.489 ms
64 bytes from icmp_seq=4 ttl=64 time=0.437 ms
64 bytes from icmp_seq=5 ttl=64 time=0.514 ms
64 bytes from icmp_seq=6 ttl=64 time=0.614 ms
64 bytes from icmp_seq=7 ttl=64 time=0.612 ms
64 bytes from icmp_seq=8 ttl=64 time=0.488 ms
64 bytes from icmp_seq=9 ttl=64 time=0.483 ms
64 bytes from icmp_seq=10 ttl=64 time=0.614 ms

--- ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9239ms
rtt min/avg/max/mdev = 0.340/0.505/0.614/0.087 ms

So this bug has been fixed very well. Move to 'VERIFIED'.

Comment 15 errata-xmlrpc 2021-05-25 06:42:15 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (virt:av bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.