[Kernel-packages] [Bug 1781038] Comment bridged from LTC Bugzilla

2018-07-31 Thread bugproxy
--- Comment From s...@us.ibm.com 2018-07-31 08:56 EDT--- I believe the customer has asked to close this bug. Canonical, please confirm. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1781038] Comment bridged from LTC Bugzilla

2018-07-23 Thread bugproxy
--- Comment From p...@au1.ibm.com 2018-07-24 00:03 EDT--- There are a couple of points about the CMA and HPT allocations: 1. The HPT is probably getting sized according to the maximum memory of the guest, not the initial amount of memory. Since we haven't been given any specifics about

[Kernel-packages] [Bug 1781038] Comment bridged from LTC Bugzilla

2018-07-23 Thread bugproxy
--- Comment From s...@us.ibm.com 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).

[Kernel-packages] [Bug 1781038] Comment bridged from LTC Bugzilla

2018-07-23 Thread bugproxy
--- Comment From s...@us.ibm.com 2018-07-23 15:10 EDT--- I'm still looking. I'm confident that daniel has correctly identified and explained the failure mode (i.e. out of enough CMA to create guests). I also don't *think* we have enough information at the moment to say for sure why this

[Kernel-packages] [Bug 1781038] Comment bridged from LTC Bugzilla

2018-07-20 Thread bugproxy
--- Comment From s...@us.ibm.com 2018-07-20 19:03 EDT--- Looking though the qemu logs, I'm not seeing anything obvious, though I will have a colleague look at them also on Monday. I see that even "some time later" we have a system with 512gb of RAM, the usual default 5% in CMA (25gb) and

Re: [Kernel-packages] [Bug 1781038] Comment bridged from LTC Bugzilla

2018-07-18 Thread Daniel Axtens
Hi, I am told that this is the same machine but not while it was currently showing symptoms - due to the intermittent nature of the problem it was taken some time later. This matches what I see in the logs so I have no reason to doubt it. Regards, Daniel -- You received this bug notification

[Kernel-packages] [Bug 1781038] Comment bridged from LTC Bugzilla

2018-07-18 Thread bugproxy
--- Comment From s...@us.ibm.com 2018-07-18 08:38 EDT--- Thanks, Daniel. Are you confident that the provided logs, etc. are taken from a machine that is currently actually showing the symptoms? The customer does tend to take the view that all machines are the same at all times. I don't

[Kernel-packages] [Bug 1781038] Comment bridged from LTC Bugzilla

2018-07-12 Thread bugproxy
--- Comment From s...@us.ibm.com 2018-07-12 10:00 EDT--- Clearly, the general problem of running out of CMA allocatable space is not soluble in the current architecture, anyway. However, this is exactly why we need to know the particular situation at hand to understand this particular