------- Comment From [email protected] 2018-07-23 16:30 EDT------- I think the key patch (from LP 1632045) was pulled in as of 4.4.0-51.72. As far as I can tell, the CMA debugging is not in ubuntu (actually, I'm not positive it was even pulled in upstream, but that's less immediately important). I will continue to poke, but I don't think there's a good way even to determine, without a kdump, where that memory is in use. I think the only thing to do is try to work around the problem by devoting more memory to the CMA by specifying a boot parameter like cma=50g for example. That would at least greatly alleviate the problem, though not fix it. To fix it, I think we will need to arrange for a kdump from a failing system and then see exactly where the memory is in use.
I will keep asking my colleagues; however, that's where I am for now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1781038 Title: KVM guest hash page table failed to allocate contiguous memory (CMA) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1781038/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
