Guest log:
2019-12-04T12:26:47.336084Z qemu-system-x86_64: VFIO_MAP_DMA: -12
2019-12-04T12:26:47.336130Z qemu-system-x86_64: vfio_dma_map(0x56054be32010,
0x100000, 0x7ff00000, 0x7f38ebf00000) = -12 (Cannot allocate memory)
qemu: hardware error: vfio: DMA mapping failed, unable to continue
Which matches the dmesg message you had:
[ 7599.866275] vfio_pin_pages_remote: RLIMIT_MEMLOCK (5368709120) exceeded
Did you check your full dmesg if you ever had a apparmor DENY for setrlimit?
Like in bug 1679704.
In any case you can increase the initial limits that are applied with a guest
config snippet like:
<memtune>
<hard_limit unit='GiB'>32</hard_limit>
<soft_limit unit='GiB'>32</soft_limit>
</memtune>
See also https://libvirt.org/formatdomain.html#elementsMemoryTuning
Also still waiting on:
- Ubuntu release
- kernel version
- exact type of VF device (XML + lspci)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1854952
Title:
VM is getting crashed/shutdown when we attach VF's on demand
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1854952/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
