Re: [Qemu-devel] [PATCH v3 1/1] s390-ccw-virtio: allow for systems larger that 7.999TB

2017-12-14 Thread Cornelia Huck
On Thu, 14 Dec 2017 14:26:17 +0100 David Hildenbrand wrote: > On 14.12.2017 14:21, Cornelia Huck wrote: > > On Mon, 11 Dec 2017 13:21:46 +0100 > > Christian Borntraeger wrote: > > > >> KVM does not allow memory regions > KVM_MEM_MAX_NR_PAGES,

Re: [Qemu-devel] [PATCH v3 1/1] s390-ccw-virtio: allow for systems larger that 7.999TB

2017-12-14 Thread David Hildenbrand
On 14.12.2017 14:21, Cornelia Huck wrote: > On Mon, 11 Dec 2017 13:21:46 +0100 > Christian Borntraeger wrote: > >> KVM does not allow memory regions > KVM_MEM_MAX_NR_PAGES, basically >> limiting the memory per slot to 8TB-4k. As memory slots on s390/kvm must >> be a

Re: [Qemu-devel] [PATCH v3 1/1] s390-ccw-virtio: allow for systems larger that 7.999TB

2017-12-14 Thread Cornelia Huck
On Mon, 11 Dec 2017 13:21:46 +0100 Christian Borntraeger wrote: > KVM does not allow memory regions > KVM_MEM_MAX_NR_PAGES, basically > limiting the memory per slot to 8TB-4k. As memory slots on s390/kvm must > be a multiple of 1MB we need start a new memory region if we

[Qemu-devel] [PATCH v3 1/1] s390-ccw-virtio: allow for systems larger that 7.999TB

2017-12-11 Thread Christian Borntraeger
KVM does not allow memory regions > KVM_MEM_MAX_NR_PAGES, basically limiting the memory per slot to 8TB-4k. As memory slots on s390/kvm must be a multiple of 1MB we need start a new memory region if we cross 8TB-1M. With that (and optimistic overcommitment in the kernel) I was able to start a