On 02/23/2017 08:50 AM, Michal Privoznik wrote:
On 02/23/2017 03:26 PM, Matt Fleming wrote:
On Tue, 21 Feb, at 11:23:52AM, Michal Privoznik wrote:
Jim,
what is the actual problem? I've tried to reproduce this by running vm
with 3.5G RAM backed by 1GB huge pages and the guest runs just fine.
On 02/23/2017 03:26 PM, Matt Fleming wrote:
> On Tue, 21 Feb, at 11:23:52AM, Michal Privoznik wrote:
>>
>> Jim,
>>
>> what is the actual problem? I've tried to reproduce this by running vm
>> with 3.5G RAM backed by 1GB huge pages and the guest runs just fine. I
>> mean kvm guest. This is because
On Tue, 21 Feb, at 11:23:52AM, Michal Privoznik wrote:
>
> Jim,
>
> what is the actual problem? I've tried to reproduce this by running vm
> with 3.5G RAM backed by 1GB huge pages and the guest runs just fine. I
> mean kvm guest. This is because at the cmd line level there is aligned
> value:
>
On 02/13/2017 02:52 AM, Jim Fehlig wrote:
> Hi All,
>
> Matt encountered the following issue when using 1GB huge pages with libvirt
>
>> This problem turned out to be entirely my fault because I didn't round
>> the VM's memory size to a 1G multiple, and the kernel tried to split
>> the VMA at
Hi All,
Matt encountered the following issue when using 1GB huge pages with libvirt
This problem turned out to be entirely my fault because I didn't round
the VM's memory size to a 1G multiple, and the kernel tried to split
the VMA at the end of the region, triggering this code in the kernel
