I already had the patch complete and was writing the changelog, but
while doing that and the dep8 header I realized that this really isn't
something we want to do.
Effectively that would "invite" latter and worse issues - in this case for
example you don't want qemu to map against the 1G pages in
/dev/hugepages-1048576.
You really might want to uncomment the hugetlbfs_mount in
/etc/libvirt/qemu.conf to disable the guesswork libvirt is doing.
If you would really want it to map against that you'd still want to set
hugetlbfs_mount to have it reliably pick up the right path and in case of a non
standard path you'd then want to extend the apparmor profile as Seth suggested.
I still want to continue discussing this and it would be great Thiago,
if you could provide the files I asked for of your case. Also I might
overlook something, so discussion is certainly worth it.
I'll however make a comment entry in the DPDK config file about the issue.
Adding a tracker now.
** Also affects: dpdk (Ubuntu)
Importance: Undecided
Status: New
** Changed in: dpdk (Ubuntu)
Status: New => Triaged
** Changed in: dpdk (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1680956
Title:
Fail to launch an OpenStack Instance with hugepages on top of OVS+DPDK
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1680956/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
