[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1851664
Title:
After increasing dma_entry_limit limit no issue observed.
But ideal senario device is getting hung and recovery happening only
with host hard rebooting.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Presumably w-bits (aw-bits?) implies using intel-iommu, there's a
opportunity for the vfio iommu backend to return -ENOSPC (-28) if we
exceed the default number of in-flight DMA mappings per container. The
default limit is 65535. You can try increasing this by changing the
dma_entry_limit module
qemu-system-x86_64 -name guest=fedora24 -machine
q35,accel=kvm,kernel-irqchip=split \
-enable-kvm \
-m 4G \
-smp 8,sockets=1,cores=8,threads=1 \
-device intel-iommu,intremap=on,caching-mode=on,aw-bits=48 \
-drive file=,format=raw \
-device
Please find the above qemu command to lunch guest machine
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1851664
Title:
qemu-system-x86_64: "VFIO_MAP_DMA : -28" error when we attache 6 VF's
to
Please provide information how you started QEMU, and some information
about your PCI device (e.g. the output of lspci).
** Information type changed from Private Security to Public
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a
