From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 209025] New: The "VFIO_MAP_DMA failed: Cannot allocate memory" bug is back
Date: Mon, 24 Aug 2020 16:35:06 +0000 [thread overview]
Message-ID: <bug-209025-28872@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=209025
Bug ID: 209025
Summary: The "VFIO_MAP_DMA failed: Cannot allocate memory" bug
is back
Product: Virtualization
Version: unspecified
Kernel Version: 5.9 rc1 and rc2
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: kvm
Assignee: virtualization_kvm@kernel-bugs.osdl.org
Reporter: rmuncrief@humanavance.com
Regression: No
Created attachment 292143
--> https://bugzilla.kernel.org/attachment.cgi?id=292143&action=edit
VM Fail Log
My primary Windows 10 VM uses GPU/SATA/USB passthrough and it appears a
regression has been introduced in kernel 5.9. The VM will not start with both
rc1 and rc2 because of the "VFIO_MAP_DMA failed: Cannot allocate memory" error
on all passthrough devices.
I'm running an R7 3700X CPU, ASUS TUF Gaming X570-Plus MB, 16GB PC3200 DDR4,
and two RX 580 GPUs (one dedicated to the VM passthrough). I've attached the
relevant log excerpt to this report.
By the way, the log only shows one device failing because QEMU/KVM exits on the
first error. But I switched around all VM devices so they were the first
encountered and each one failed in the same way, so it's not device related.
The VM works fantastically with kernels 5.8.3 and 5.4.60.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2020-08-24 17:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-24 16:35 bugzilla-daemon [this message]
2020-08-24 20:43 ` [Bug 209025] The "VFIO_MAP_DMA failed: Cannot allocate memory" bug is back bugzilla-daemon
2020-08-24 20:57 ` bugzilla-daemon
2020-08-25 0:53 ` bugzilla-daemon
2020-08-25 3:14 ` bugzilla-daemon
2020-08-25 7:26 ` bugzilla-daemon
2020-08-25 14:32 ` bugzilla-daemon
2020-08-25 14:32 ` bugzilla-daemon
2020-08-25 16:31 ` bugzilla-daemon
2020-08-25 17:09 ` bugzilla-daemon
2020-08-25 17:13 ` bugzilla-daemon
2020-08-25 17:47 ` bugzilla-daemon
2020-08-25 17:55 ` bugzilla-daemon
2020-08-25 18:06 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-209025-28872@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=kvm@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox