Description of problem: Environment HP Proliant DL380 G6 local (direct attached) 68GB drive and 144GB of RAM By default the installer tries to create a very large swap partition of 88992 MB. When completing the setup *with default options*, the setup fails with: Exception: runtime error ('failed to partition/format',) At this point the only option given is to "reboot" -- there is no option to go back and edit the partitions. Rebooting, running the RHEV-H setup again, modifying the swap partition, and decreasing it to 50,992 MB (for example) completes fine. Version-Release number of selected component (if applicable): RHEV Hypervisor - 6.5 - 20140520.0.el6ev and 20140603 How reproducible: 100% Steps to Reproduce: 1. Attempt to install to a host with a large amount of RAM (works as expected with 8 GB) using the default partitioning layout for swap. Actual results: Installation fails Expected results: The default partitioning scheme in RHEV-H setup should work without intervention. Additional info: Reducing the RAM to 8GB, I could not reproduce the issue. This it can only be reproduced when the RAM on the box is fairly high, e.g. 144GB in this case.
Ryan, can you please check if this is possibly also addressed with this patch: u/s Change-Id: I70277cfebbed9646022d2055c9302dbf8fccdf4d Bug-Url: https://bugzilla.redhat.com/show_bug.cgi?id=1087341
It does appear to be a duplicate. I don't think I have any systems with enough memory to reproduce (the biggest I've got here is 48GB), but it does appear to be a duplicate of: https://bugzilla.redhat.com/show_bug.cgi?id=1087324 (looks like I used the wrong bug in the patch) I'll see about reproducing
Hey Robert, it looks this bug seems to be caused by the combination of a large amount of RAM and a small disk. Normally RHEV-H treis to create a swap partition on disk, which is larger than the RAM size. As Ryan says, bug 1087324 is likely a duplicate of this bug, and the fix for it will land at latest in 3.5. For now the customer can try to workaround this issue by setting the SWAP size to a reasonable default during the installation. Please let me know if that workaround works.
*** This bug has been marked as a duplicate of bug 1099384 ***