| commit | 80df46494846e857399618c54df30ce294dc1edd | |
| author | Maxim Uvarov <maxim.uvarov@oracle.com> | |
| Fri, 14 Oct 2011 22:36:51 +0000 (14 15:36 -0700) | ||
| committer | Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> | |
| Mon, 21 Nov 2011 22:14:46 +0000 (21 17:14 -0500) | ||
| tree | 704ed580131750bf17cca19e9fe98cec418d1b5c | treesnapshot (tar.gz zip) |
| parent | 92931abf3f5bd3efe941d67d67c5f14b6c16d4f7 | commitdiff |
xen: Make XEN_MAX_DOMAIN_MEMORY have more sensible defaults
Which is that 128GB is not going to happen with 32-bit PV DomU.
Lets use something more realistic. Also update the 64-bit to 500GB
which is the max a PV guest can do.
Signed-off-by: Maxim Uvarov <maxim.uvarov@oracle.com>
[v1: Updated 128GB->500GB for 64-bit]
Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Which is that 128GB is not going to happen with 32-bit PV DomU.
Lets use something more realistic. Also update the 64-bit to 500GB
which is the max a PV guest can do.
Signed-off-by: Maxim Uvarov <maxim.uvarov@oracle.com>
[v1: Updated 128GB->500GB for 64-bit]
Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
| arch/x86/xen/Kconfig | diffblobblamehistory |