Bug 715572

Summary:	RFE: check for minimum RAM available
Product:	[Fedora] Fedora	Reporter:	Karel Volný <kvolny>
Component:	anaconda	Assignee:	Will Woods <wwoods>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	15	CC:	amit.shah, berrange, dwmw2, ehabkost, gcosta, itamar, jaswinder, jforbes, jonathan, knoel, markmc, ondrejj, scottt.tw, vanmeeuwen+fedora, virt-maint
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-06-23 14:10:27 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Karel Volný 2011-06-23 11:50:45 UTC

Description of problem:
can't install Fedora 15 in qemu

Version-Release number of selected component (if applicable):
qemu-0.14.0-7.fc15.x86_64

How reproducible:
always

Steps to Reproduce:
0. sha256sum -c Fedora-15-x86_64-CHECKSUM
1. qemu-img create -f qcow2 F15.qcow2 10G
2. qemu-kvm -m 512 -cdrom Fedora-15-x86_64-DVD.iso F15.qcow2
3. choose "Install a new system or upgrade an existing sytem"
  
Actual results:
the installation freezes, qemu eats 100% cpu
the last message is:

[    0.135858] Trying to unpack rootfs image as initramfs...

Expected results:
the system installs without any problem

Additional info:
installation of Fedora 14 goes just fine ...

Comment 1 Karel Volný 2011-06-23 12:26:21 UTC

shame on me, I've missed that I need 640 MiB RAM (oh my ...)

http://docs.fedoraproject.org/en-US/Fedora/15/html/Release_Notes/sect-Release_Notes-Welcome_to_Fedora_15.html#sect-Release_Notes-Hardware_Overview

anyway, hard freeze instead of properly reported error is bad behaviour so turning this into RFE

Comment 2 Chris Lumens 2011-06-23 12:36:18 UTC

This is way too early for anaconda to do any sort of check - it's still the kernel setting the environment up.  We are, however, working on making things fit into memory better.

Comment 3 Karel Volný 2011-06-23 13:09:22 UTC

(In reply to comment #2)
> This is way too early for anaconda to do any sort of check - it's still the
> kernel setting the environment up.

then let's pass this to kernel ... it should report some sort of "out of memory" message instead of just hanging (or what does it do?)

Comment 4 Will Woods 2011-06-23 14:10:27 UTC

It panics, with a trace that starts:
[    2.546782] Call Trace:
[    2.547107]  [<ffffffff81467a3a>] ? panic+0x91/0x19c
[    2.547674]  [<ffffffff810daf85>] ? out_of_memory+0x2e2/0x378

Which seems pretty clear to me, but there's some proposed patches to make this clearer in bug 680542.

*** This bug has been marked as a duplicate of bug 680542 ***

Comment 5 Karel Volný 2011-06-23 20:57:54 UTC

(In reply to comment #4)
> It panics, with a trace that starts:
> [    2.546782] Call Trace:
> [    2.547107]  [<ffffffff81467a3a>] ? panic+0x91/0x19c
> [    2.547674]  [<ffffffff810daf85>] ? out_of_memory+0x2e2/0x378

hm, this hasn't happened on my system - at least not within reasonable timeframe (i.e. tenths of minutes)