Red Hat Bugzilla – Bug 825735
RFE: Provide tui screen to set partition sizes
Last modified: 2016-04-26 09:25:00 EDT
Created attachment 587201 [details]
Description of problem:
on a big memory machine, during install will report "not enough space for installation". It should be the swap_size is too big.
The current method to allocate the swap_size is:
SWAP_SIZE = int(BASE_SWAP_SIZE) + int(OVERCOMMIT_SWAP_SIZE)
if MEM_SIZE_GB < 4:
elif MEM_SIZE_GB < 16:
elif MEM_SIZE_GB < 64:
OVERCOMMIT_SWAP_SIZE = int(MEM_SIZE_MB) * self.overcommit * 10 / 10
On a machine with 256 GB mem, the SWAP_SIZE will large than 100GB.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. tui install rhevh on a big memory machine, such as have 256GB mem.
during install will report "not enough space for installation".
install can continue.
This is really NOTABUG, but I'll defer it to 6.4 as an RFE to add a partition size configuration screen.
In the above case, if you provide a disk large enough, the installation will be successful. If you want to customize the swap size, you can specify it in the storage_vol kernel command line parameter.
another option is to allow the user to set the overcommit value (which defaults to 0.5).
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development. This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.
upstream patch: http://gerrit.ovirt.org/#/c/8520/
oVirt Node Hypervisor 2.5.999-999.201210101948.fc17
│ Please enter the sizes for the following partitions in MB │
│ UEFI/Bios: 256_______ │
│ Root & RootBackup: 256_______ (2 partitions at 256MB each) │
│ Swap: 39________ │
│ Config: 500_______ │
│ Logging: 2048______ │
│ Data: 100_______ │
│ <Quit> <Back> <Continue> │
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.