Bug 219889 - Update to 'kernel-lt.x86_64-6.1.130-1.el9.elrepo' causes start failure in the VM with vfio passthrough
Summary: Update to 'kernel-lt.x86_64-6.1.130-1.el9.elrepo' causes start failure in the...
Status: NEW
Alias: None
Product: Linux
Classification: Unclassified
Component: Kernel (show other bugs)
Hardware: Intel Linux
: P3 high
Assignee: Virtual assignee for kernel bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-03-17 04:47 UTC by bugzilla.kernel.org
Modified: 2025-03-30 17:12 UTC (History)
2 users (show)

See Also:
Kernel Version:
Subsystem:
Regression: No
Bisected commit-id:


Attachments
grub.cfg (3.34 KB, text/plain)
2025-03-17 04:49 UTC, bugzilla.kernel.org
Details
VM config (3.78 KB, text/xml)
2025-03-17 04:49 UTC, bugzilla.kernel.org
Details
Successful start on 6.1.129 (3.60 KB, text/plain)
2025-03-17 04:50 UTC, bugzilla.kernel.org
Details
Error on 6.1.130 (6.22 KB, text/plain)
2025-03-17 04:51 UTC, bugzilla.kernel.org
Details
Error on 6.1.131 (6.12 KB, text/plain)
2025-03-17 04:51 UTC, bugzilla.kernel.org
Details
Ok in 6.13.6 (3.60 KB, text/plain)
2025-03-17 04:51 UTC, bugzilla.kernel.org
Details
Ok in 6.13.7 (3.39 KB, text/plain)
2025-03-17 04:52 UTC, bugzilla.kernel.org
Details
6.1.132 (6.12 KB, text/plain)
2025-03-29 04:10 UTC, bugzilla.kernel.org
Details
6.14.0 (3.39 KB, text/plain)
2025-03-29 04:11 UTC, bugzilla.kernel.org
Details

Description bugzilla.kernel.org 2025-03-17 04:47:49 UTC
There is an issue in the kernels 6.1.130 & 6.1.131, while in 6.13.6 & 6.13.7 it works ok.

Cannot start VM with error

2025-03-08T14:53:10.620302Z qemu-kvm: VFIO_MAP_DMA failed: Cannot allocate memory
2025-03-08T14:53:10.620323Z qemu-kvm: vfio_container_dma_map(0x5621ca6e5400, 0xc0000, 0x20000, 0x7fd550600000) = -12 (Cannot allocate memory)
qemu: hardware error: vfio: DMA mapping failed, unable to continue


Config & logs are in the attachment.
Comment 1 bugzilla.kernel.org 2025-03-17 04:49:23 UTC
Created attachment 307842 [details]
grub.cfg
Comment 2 bugzilla.kernel.org 2025-03-17 04:49:43 UTC
Created attachment 307843 [details]
VM config
Comment 3 bugzilla.kernel.org 2025-03-17 04:50:36 UTC
Created attachment 307844 [details]
Successful start on 6.1.129
Comment 4 bugzilla.kernel.org 2025-03-17 04:51:12 UTC
Created attachment 307845 [details]
Error on 6.1.130
Comment 5 bugzilla.kernel.org 2025-03-17 04:51:29 UTC
Created attachment 307846 [details]
Error on 6.1.131
Comment 6 bugzilla.kernel.org 2025-03-17 04:51:56 UTC
Created attachment 307847 [details]
Ok in 6.13.6
Comment 7 bugzilla.kernel.org 2025-03-17 04:52:11 UTC
Created attachment 307848 [details]
Ok in 6.13.7
Comment 8 bugzilla.kernel.org 2025-03-29 04:10:00 UTC
There is the same bug in 6.1.132 and it's ok in 6.14.0.
Comment 9 bugzilla.kernel.org 2025-03-29 04:10:48 UTC
Created attachment 307905 [details]
6.1.132
Comment 10 bugzilla.kernel.org 2025-03-29 04:11:09 UTC
Created attachment 307906 [details]
6.14.0
Comment 11 Akemi Yagi 2025-03-30 17:12:56 UTC
Just wanted to add a note that elrepo does not make modifications to the source code from kernel.org. Chances are this is a bug in linux-6.1.130. 

The mainline kernels do not show any problem. Assuming that some backport caused the issue, there might be additional patches that should have been applied together.

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