diff options
| author | Christian Borntraeger <borntraeger@de.ibm.com> | 2017-12-11 13:21:46 +0100 |
|---|---|---|
| committer | Cornelia Huck <cohuck@redhat.com> | 2017-12-15 11:54:52 +0100 |
| commit | bb223055b9b327ec66e1f6d2fbaebaee0b8f3dbe (patch) | |
| tree | 0d7d91f7f1b108911abea548c1b4c67e798f5e83 /trace | |
| parent | 35b4df6417fc3cd9d0150590f770fdd404dfbee7 (diff) | |
| download | qemu-bb223055b9b327ec66e1f6d2fbaebaee0b8f3dbe.zip qemu-bb223055b9b327ec66e1f6d2fbaebaee0b8f3dbe.tar.gz qemu-bb223055b9b327ec66e1f6d2fbaebaee0b8f3dbe.tar.bz2 | |
s390-ccw-virtio: allow for systems larger that 7.999TB
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 24TB guest on a 1TB system.
Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
Message-Id: <20171211122146.162430-1-borntraeger@de.ibm.com>
Reviewed-by: David Hildenbrand <david@redhat.com>
[CH: 1UL -> 1ULL in KVM_MEM_MAX_NR_PAGES; build fix on 32 bit hosts]
Signed-off-by: Cornelia Huck <cohuck@redhat.com>
Diffstat (limited to 'trace')
0 files changed, 0 insertions, 0 deletions