Bug 624414 - OOMKILL on VM with 768MB RAM and no swap
OOMKILL on VM with 768MB RAM and no swap
Status: CLOSED CANTFIX
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
14
All Linux
low Severity medium
: ---
: ---
Assigned To: Anaconda Maintenance Team
Fedora Extras Quality Assurance
:
Depends On:
Blocks: F14Blocker/F14FinalBlocker
  Show dependency treegraph
 
Reported: 2010-08-16 07:20 EDT by Kamil Páral
Modified: 2010-08-16 10:23 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-08-16 10:23:29 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
anaconda logs (290.00 KB, application/x-tar)
2010-08-16 07:20 EDT, Kamil Páral
no flags Details
kernel messages (35.04 KB, image/png)
2010-08-16 07:20 EDT, Kamil Páral
no flags Details
memory usage in the moment of OOM crash as seen by top (319.23 KB, image/png)
2010-08-16 07:21 EDT, Kamil Páral
no flags Details

  None (edit)
Description Kamil Páral 2010-08-16 07:20:04 EDT
Created attachment 438924 [details]
anaconda logs

Description of problem:
I installed Fedora 14 Alpha RC4 DVD x86_64, using DVD as a package repository. I use KVM in virt-manager. The virtual machine has 768MB RAM assigned.

The installation fails on 'Out of memory', but only if I don't have swap partition created (very weird).

I used vnc for installation (all logs are from that attempt), but later I reproduced it also when using basic graphical installation. So it is probably not related to vnc. 

The installation fails when installing selinux-policy-targeted package. It seems that package requires huge amount of memory and kernel OOMKILLs anaconda.

The weird thing is that the installation proceeds just fine if I have "use whole disk" disk layout (I use 7GB disk device in my VM). But when I create custom disk layout, create just a single 7GB large partition for / (no other partitions, no LVM, no swap, nothing), the installation fails on OOM.

Version-Release number of selected component (if applicable):
anaconda 14.15

How reproducible:
always, but correct setup is needed

Steps to Reproduce:
1. Use KVM VM in virt-manager using 768MB RAM.
2. Select custom disk layout, create a single partition (for /) over whole disk (7GB in my case), no LVM, no other partition, no swap.
3. Installation produces OOM on selinux-policy-targeted package installation.
  
Actual results:
768MB RAM is not enough for installation

Expected results:
768MB RAM is enough for installation

Additional info:
I tested the exactly same setup on VM with 1GB RAM and installation succeeds. Therefore the required amount of RAM is somewhere between 768MB and 1GB.
Comment 1 Kamil Páral 2010-08-16 07:20:23 EDT
Created attachment 438925 [details]
kernel messages
Comment 2 Kamil Páral 2010-08-16 07:21:11 EDT
Created attachment 438926 [details]
memory usage in the moment of OOM crash as seen by top
Comment 3 Kamil Páral 2010-08-16 07:24:23 EDT
Oh, I think I get it know. If I create a swap partition in the installation process, that partition is available even for anaconda, right? That would explain why default disk setup works. But if I don't create swap partition, it has no swap to use and just halts.

That would mean that this bug report should be more appropriately called "768MB RAM is not enough for installation" or something like that. 768MB should be enough. (Do we have some official guidelines on that somewhere?)
Comment 4 Chris Lumens 2010-08-16 10:23:29 EDT
It's really quite difficult to definitively say how much memory is required for installation.  It depends on your architecture, what storage selections you make (certain storage programs require more memory), your packaging selections, etc.  We have some guidelines, but we can't really say for sure whether you've got enough or not.

You're right, though - if you make a swap partition, anaconda will make use of that.

Note You need to log in before you can comment on or make changes to this bug.