RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2002458 - There Is ' VFIO_MAP_DMA failed' Info in HMP When Rebooting Guest After Installation
Summary: There Is ' VFIO_MAP_DMA failed' Info in HMP When Rebooting Guest After Instal...
Keywords:
Status: CLOSED DUPLICATE of bug 1998027
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: qemu-kvm
Version: 9.0
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Philippe Mathieu-Daudé
QA Contact: CongLi
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-09-08 21:07 UTC by John Ferlan
Modified: 2021-12-07 22:40 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1996530
Environment:
Last Closed: 2021-09-18 11:08:02 UTC
Type: ---
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-96602 0 None None None 2021-09-08 21:09:10 UTC

Description John Ferlan 2021-09-08 21:07:23 UTC 
+++ This bug was initially created as a clone of Bug #1996530 +++

Description of problem:
As subject, there is the hint info in HMP but the guest is still running well.


Version-Release number of selected component (if applicable):
qemu-kvm-6.0.0-28.module+el8.5.0+12271+fffa967b
kernel-4.18.0-330.el8.x86_64


How reproducible:
4/4


Steps to Reproduce:
Setup NVMe disk:
1. Unbind the host NVMe controller from host
# echo 0000:bc:00.0 > /sys/bus/pci/devices/0000\:bc\:00.0/driver/unbind

2.Bind the host NVMe controller to the host vfio-pci driver
# echo 144d a822 > /sys/bus/pci/drivers/vfio-pci/new_id

Installing guest on the NVMe disk:
1. Create the NVMe disk with qcow2+20G.
# qemu-img create -f qcow2 nvme://0000:bc:00.0/1 20G
# qemu-img info nvme://0000:bc:00.0/1
image: nvme://0000:bc:00.0/1
file format: qcow2
virtual size: 20 GiB (21474836480 bytes)
disk size: unavailable
cluster_size: 65536
Format specific information:
    compat: 1.1
    compression type: zlib
    lazy refcounts: false
    refcount bits: 16
    corrupt: false
    extended l2: false

2. Install guest on the disk
/usr/libexec/qemu-kvm \
    -S  \
    -name 'avocado-vt-vm1'  \
    -sandbox on  \
    -machine q35 \
    -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 VGA,bus=pcie.0,addr=0x2 \
    -m 15360  \
    -smp 16,maxcpus=16,cores=8,threads=1,dies=1,sockets=2  \
    -cpu 'Haswell-noTSX',+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 \
    -object iothread,id=iothread0 \
    -object iothread,id=iothread1 \
    -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:1c:0c:0d:e3:4c,id=idjmZXQS,netdev=idEFQ4i1,bus=pcie-root-port-3,addr=0x0  \
    -netdev tap,id=idEFQ4i1,vhost=on  \
    -vnc :0  \
    -rtc base=utc,clock=host,driftfix=slew  \
    -boot menu=off,order=cdn,once=c,strict=off \
    -enable-kvm \
    -monitor stdio \
    -chardev socket,server=on,path=/var/tmp/monitor-qmpmonitor1-20210721-024113-AsZ7KYro,id=qmp_id_qmpmonitor1,wait=off  \
    -mon chardev=qmp_id_qmpmonitor1,mode=control \
    -device pcie-root-port,id=pcie-root-port-5,port=0x5,addr=0x1.0x5,bus=pcie.0,chassis=5 \
    -device virtio-scsi-pci,id=virtio_scsi_pci1,bus=pcie-root-port-5,addr=0x0,iothread=iothread1 \
    -blockdev node-name=nvme_image1,driver=nvme,device=0000:bc:00.0,namespace=1,auto-read-only=on,discard=unmap \
    -blockdev node-name=drive_nvme1,driver=qcow2,file=nvme_image1,read-only=off,discard=unmap \
    -device scsi-hd,id=nvme1,drive=drive_nvme1 \
    -device pcie-root-port,id=pcie-root-port-6,port=0x6,addr=0x1.0x6,bus=pcie.0,chassis=6 \
    -device virtio-scsi-pci,id=virtio_scsi_pci2,bus=pcie-root-port-6,addr=0x0 \
    -blockdev node-name=file_cd1,driver=file,auto-read-only=on,discard=unmap,aio=threads,filename=/home/kvm_autotest_root/iso/linux/RHEL-8.5.0-20210714.n.0-x86_64-dvd1.iso,cache.direct=on,cache.no-flush=off \
    -blockdev node-name=drive_cd1,driver=raw,read-only=on,cache.direct=on,cache.no-flush=off,file=file_cd1 \
    -device scsi-cd,id=cd1,drive=drive_cd1,write-cache=on \


Actual results:
Hit the error hint in HMP when rebooting the guest after installation.
# sh qemu-install.sh 
QEMU 6.0.0 monitor - type 'help' for more information
(qemu) c
(qemu) qemu-kvm: VFIO_MAP_DMA failed: No space left on device

Check the status of the guest:
(qemu) info status
VM status: running


Expected results:
There is no hint info in HMP.


Additional info:
Hit the same issue when installing guest with the NVMe disk created with luks format.

--- Additional comment from Philippe Mathieu-Daudé on 2021-08-24 07:34:05 UTC ---

Amusingly while reviewing another BZ yesterday I thought this warning would confuse end-users, and here we are. Self-assigning.

--- Additional comment from Philippe Mathieu-Daudé on 2021-08-24 14:35:33 UTC ---

Upstream series: https://lore.kernel.org/qemu-devel/20210824141142.1165291-1-philmd@redhat.com/T/#mb889c9accae815811792d339f105cd91c518d155

--- Additional comment from Philippe Mathieu-Daudé on 2021-08-26 20:09:48 UTC ---

v2: https://lore.kernel.org/qemu-devel/20210826195014.2180369-1-philmd@redhat.com/

--- Additional comment from Klaus Heinrich Kiwi on 2021-08-27 12:16:28 UTC ---

(In reply to Philippe Mathieu-Daudé from comment #1)
> Amusingly while reviewing another BZ yesterday I thought this warning would
> confuse end-users, and here we are. Self-assigning.

Thanks Phil!

--- Additional comment from Philippe Mathieu-Daudé on 2021-09-02 07:05:19 UTC ---

v3: https://lore.kernel.org/qemu-devel/20210902070025.197072-1-philmd@redhat.com/

--- Additional comment from Philippe Mathieu-Daudé on 2021-09-07 15:22:55 UTC ---

Merged upstream: https://gitlab.com/qemu-project/qemu/-/commit/f9128631fbeb40a55f7bc145397981c963d40909.

--- Additional comment from Danilo Cesar Lemes de Paula on 2021-09-07 18:33:59 UTC ---


This bug has been addressed by Philippe Mathieu-Daudé <philmd>, with the following series:
[RHEL-AV-8.5.0 qemu-kvm PATCH 00/10] block/nvme: Only report VFIO error on failed retry

http://patchwork.virt.bos.redhat.com/patch/102073

--- Additional comment from John Ferlan on 2021-09-08 21:05:29 UTC ---

Housekeeping - the referenced commit went into qemu-6.2 which is planned to be rebased some time in Nov/Dec when it's "released" upstream. It may be the case that an 6.2-rc release could be used for an early rebase, but we'll need to revisit this then.

Removed the ITM - that's something for QE to set.

Set the DTM to 14 and left in POST under the assumption this would be picked up by the rebase at that time. Comment 6 lists the upstream commit id.

I will move the bug to RHEL8 since that's where the rebase will happen and RHEL-AV will "just" be a rebuild of RHEL
Comment 1 Tingting Mao 2021-09-09 01:20:41 UTC 

*** This bug has been marked as a duplicate of bug 1998027 ***
Comment 2 John Ferlan 2021-09-17 14:00:52 UTC 
I agree in general w/ comment 1; however, the product is different - bug 1998027 is for RHEL8 and this one is for RHEL9 - validation is separate.
Comment 5 John Ferlan 2021-09-18 11:08:02 UTC 
(In reply to Tingting Mao from comment #4)
> Hi John,
> 
> I have already filed 2 bugs of this issue. BZ 1996530 is for rhel8.5. BZ
> 1998027 is for rhel9. Could you please help to check again? 
> 
> Thanks.

Ahh - now I see, there are 3 bugs... This one is a clone of the RHEL8 bug 1996530 and bug 1998027 is a copy of the RHEL8 bug.

Looking back at comment 2, I must have been looking at the cloned from RHEL8 bug and not the one you noted - my apologies, I have *way too many* tabs open while trying to move bugs from RHEL8 to RHEL9 and checking for clones. 

Anyway, when clone is used, a dependency is generated which makes it clear that two bugs are "related" - when copy is used, there's no dependency which means you have to stop a read every bug. When altering 100's of bugs, that's just not possible.

You will note that the copy is essentially unassigned (even though Klaus noted he'd assign to Phil).

Thanks for making me look again - I knew I'd make mistakes and I'm happy to resolve them!  I will reclose this one as the duplicate, but also alter the other one to note the relationship with the RHEL8 bug.

*** This bug has been marked as a duplicate of bug 1998027 ***
Note You need to log in before you can comment on or make changes to this bug.