Bug 947395 - Unable to perform graphical network installation in virt-manager on VM guest with 1GB memory
Summary: Unable to perform graphical network installation in virt-manager on VM guest ...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 19
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: fedora19rtt
TreeView+ depends on / blocked
 
Reported: 2013-04-02 10:21 UTC by Ľuboš Kardoš
Modified: 2017-12-11 15:17 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-04-04 15:27:27 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Output of top command executed in anaconda environment (7.04 KB, text/plain)
2013-04-02 10:22 UTC, Ľuboš Kardoš
no flags Details
anaconda.log (710 bytes, text/x-log)
2013-04-02 10:23 UTC, Ľuboš Kardoš
no flags Details
program.log (902 bytes, text/x-log)
2013-04-02 10:23 UTC, Ľuboš Kardoš
no flags Details
X.log (17.78 KB, text/x-log)
2013-04-02 10:24 UTC, Ľuboš Kardoš
no flags Details

Description Ľuboš Kardoš 2013-04-02 10:21:52 UTC
Description of problem: 
When I start graphical network installation in virt-manager on VM guest with 1GB memory, last thing I see is a message: "Starting installer, one moment..." then I can see only black screen.


Version-Release number of selected component (if applicable):
F19-Alpha-TC3
anaconda-19.14

How reproducible:
always

Steps to Reproduce:
1. Create new VM guest in virt-manager and select "Network install".
2. Provide fedora 19 TC3 install URL.
3. Select 1024MB for guest memory.
4. Finish creating of guest and start installation.
  
Actual results:
After printing some messages, last one is "Starting installer, one moment...", black screen is showed.

Expected results:
Graphical installation should be showed instead of black screen.

Additional info:

Comment 1 Ľuboš Kardoš 2013-04-02 10:22:51 UTC
Created attachment 730673 [details]
Output of top command executed in anaconda environment

Comment 2 Ľuboš Kardoš 2013-04-02 10:23:15 UTC
Created attachment 730674 [details]
anaconda.log

Comment 3 Ľuboš Kardoš 2013-04-02 10:23:41 UTC
Created attachment 730675 [details]
program.log

Comment 4 Ľuboš Kardoš 2013-04-02 10:24:04 UTC
Created attachment 730676 [details]
X.log

Comment 5 Chris Lumens 2013-04-04 14:06:50 UTC
What happens if you boot with slub_debug=- ?

Comment 6 Ľuboš Kardoš 2013-04-04 14:44:01 UTC
Booting with slub_debug=- solves this problem.

Comment 7 Chris Lumens 2013-04-04 15:27:27 UTC
Okay, great.  We've got other bugs tracking OOM conditions in anaconda in general, so I'm going to close this one.

Comment 8 Jan Stodola 2013-04-26 11:28:05 UTC
Chris, what bugs are tracking those OOM conditions, please? Unfortunately, I wasn't able to find them in bugzilla.

https://fedoraproject.org/wiki/Common_F19_bugs also doesn't say anything about this issue.


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