Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Mike can you confirm:
1) That it is not planned to allow changing of the partition sizes from the installer UI.
2) Whether or not granular configuration will still be supported when parsing in the storage_vol kernel parameter?
3) What the recommended total minimum storage is for rhev-hypervisor 6.1/6.2?
Thanks,
Steve
(In reply to comment #1)
> Mike can you confirm:
>
> 1) That it is not planned to allow changing of the partition sizes from the
> installer UI.
Correct, no changes in the GUI install
> 2) Whether or not granular configuration will still be supported when parsing
> in the storage_vol kernel parameter?
Yes, storage_vol is still supported for automated installations
> 3) What the recommended total minimum storage is for rhev-hypervisor 6.1/6.2?
Actual minimums
Root (x2) = 256*2=512MB
Config = 5MB
Logging = 5MB (Though i think VDSM actually increases this to 2GB)
Data = 5MB
Swap = 5MB
532 MB actual minimum
Defaults:
Root (x2) = 256*2 = 512MB
Config = 5MB
Logging = 2048MB
Swap is dependent on RAM + and overcommit ratio
RAM Swap(MB)
<4GB 2048
<16GB 4096
<64GB 8192
else 16384
overcommit defaults to 0.5 and is multiplied by the actual RAM on the machine.
I think the swap calculation is actually documented somewhere in the base RHEL guides, though I'm not sure exactly where
Data, by default takes up the entire rest of the disk. It is used for upgrades when initiated from RHEV-M, so it should probably be at least 256MB
Actual minimums ended up being 8 MB, not 5 MB, as 8 MB is the minimum size of an LV extent.
* See Section 2.1.
* See Section 4.2.3 under storage_vol parameter.
Red_Hat_Enterprise_Linux-Hypervisor_Deployment_Guide-6-web-en-US-1-17.el6eng