Bug 692247 - Fedora 15 Alpha hangs in Virtualbox 4.0.0 during kernel boot of installation dvd
Summary: Fedora 15 Alpha hangs in Virtualbox 4.0.0 during kernel boot of installation dvd
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 15
Hardware: i686
OS: Unspecified
unspecified
urgent
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-30 19:35 UTC by Penelope Fudd
Modified: 2013-01-10 06:33 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-09-26 14:22:16 UTC
Type: ---


Attachments (Terms of Use)
Screenshot of crash (186.27 KB, image/png)
2011-03-30 19:35 UTC, Penelope Fudd
no flags Details

Description Penelope Fudd 2011-03-30 19:35:01 UTC
Created attachment 488880 [details]
Screenshot of crash

Description of problem:
I want to install Fedora 15 Alpha on Virtualbox 4.0.0 r69151 on a Mac OS X Snowleopard box.  The installation DVD image Fedora-15-Alpha-x86_64-DVD.iso hangs after the initial boot menu where you select "Install a new system"; the kernel starts and then hangs partway through.

Version-Release number of selected component (if applicable):
Fedora-15-Alpha-x86_64-DVD.iso

How reproducible:
Always

Steps to Reproduce:
1. Create a virtual box
2. Attach dvd image to the virtual cdrom device
3. Boot
4. Select 'install' (default option) in boot menu
  
Actual results:
Hangs

Expected results:
...

Additional info:
See attached screen shot of hung system.

Comment 1 Chris 2011-04-20 19:06:34 UTC
I can confirm that the same problem occurs with Fedora 15 beta installing on Virtualbox v4.0.4 running on Windows 7 Home Premium.

The hang occurs whether booting normally or with 'basic video driver'.

The last line displayed on screen during the attempted normal boot is:

[   3.255596] [<c040377e>] ? kernel_thread_helper+0x6/0x10

The virtual machine was created using the default settings for Fedora Linux.

Comment 2 Chuck Ebbert 2011-04-21 04:07:26 UTC
(In reply to comment #1)
> 
> The virtual machine was created using the default settings for Fedora Linux.

And what are those settings?

Comment 3 Penelope Fudd 2011-04-21 05:41:50 UTC
It's the install disk.  You virtually insert it in the virtual cdrom drive, start the virtual machine, and press the virtual enter key.  *Those* default settings.  No command line tweaking.

Comment 4 Penelope Fudd 2011-04-21 05:49:49 UTC
Whoops, sorry, I'm tired.  I don't know about Chris's virtualbox settings, but my virtualbox settings are contained in the screenshot, along with the hung virtual console, which didn't die at the same point as Chris's did.

Comment 5 Chris 2011-04-21 08:30:58 UTC
As requested, here are the default settings for Fedora Linux in Virtualbox 4.0.4:

Base memory: 512MB
Dynamically expanding virtual hard disk
Initial hard disk size: 8GB

Comment 6 Chuck Ebbert 2011-04-22 05:27:26 UTC
(In reply to comment #5)
> As requested, here are the default settings for Fedora Linux in Virtualbox
> 4.0.4:
> 
> Base memory: 512MB
> Dynamically expanding virtual hard disk
> Initial hard disk size: 8GB

Fedora 15 Beta requires 1GB for network install. (The Alpha required 1GB for all methods.)

Comment 7 Chris 2011-04-22 11:14:49 UTC
Reconfigured the virtual machine to 1024MB of RAM and Fedora 15 Beta installed successfully. Thanks for the info, Chuck.

However, on logging in after the successful installation, Gnome 3 failed to launch but did not specify why. I increased the video memory allocation from the default (12MB) to the maximum (128MB) in the virtual machine but got the same result.

(Should this be logged as a new bug?)

Comment 8 Penelope Fudd 2011-04-25 06:27:07 UTC
Chris, I think you're right, what you've found should be logged as a new bug, so that it gets the attention it deserves.

The original bug I logged had 8GB of RAM, 17MB of video memory, and 38GB of disk.

Comment 9 Steve 2011-05-03 16:30:15 UTC
Installed Fedora 15 Beta on VirtualBox 4.0.6 on a Fedora 14 base, system hangs at some point and process on base needs to be killed.
RAM 1512 MB
Video 128 MB
disk (ext3) normal 18GB
VT-x/AMD-V, Nested Paging, PAE/NX
lucky to get 2 minutes of uptime

Comment 10 Steve 2011-05-05 08:50:26 UTC
running yum/package kit will trigger the fault is more than approximately 10 items are to be updated

Comment 11 Chuck Ebbert 2011-05-08 17:59:39 UTC
We really don't support booting on Virtualbox. Can you reproduce any of these problems on a KVM host?

Comment 12 Penelope Fudd 2011-05-08 22:13:03 UTC
I'll try; can you point me to a good KVM tutorial?

A major part of my problem is that our office is 100% mac based, and we're trying to switch over to Linux in stages.  Of the three Mac-hosted virtualization solutions (VMware, Parallels, VirtualBox) only VirtualBox is open source.  I've just seen mentions of running MacOSX under KVM, but that would still be a pretty big leap for the folks in THIS office.

I realize that the crash must be due to imperfect virtualization, and therefore VirtualBox's problem, but please realize that this is the only way to convert Mac users to Linux using only free software.  It's free advertising; it lets you try before you buy and look before you leap.  It'll make you see angels.  The first hit is free.

Unfortunately they're kinda strapped for Linux kernel developers over at VirtualBox, and could use any hints they can get.  If it helps, I can definitely confirm that Fedora 14 and 13 work perfectly; I use and have used them as my daily desktop, it's just Fedora 15 beta that fails during the install.

Thanks

Comment 13 Chuck Ebbert 2011-05-09 10:13:11 UTC
Are you trying to boot the installation disc in EFI mode? (Settings ->
System -> Enable EFI) You could try disabling that, and/or adding "noefi" to the boot options when starting the install disc.

Comment 14 Steve 2011-05-10 04:38:07 UTC
built a new VirtualBox 4.0.6 instance of Fedora 15 beta 32 bit
graphic acceleration off
EFI and IO_APIC off
PAE/NX on VT-x on, nested pages off
1 GB RAM, 64 MB video
VDI - 12GB fixed, 
   /boot - ext2, 
   / - ext3 
   otherwise default
yum-presto removed, looked like it 
   caused an OOM on initial connection
network bridged - Pro1000
otherwise default
vbox additions installed
system works rather than 90s uptime

yum-presto seems to be more trouble that benefits

Comment 15 Josh Boyer 2011-09-26 14:22:16 UTC
F15 has been released for quite a while now and we cannot update installation media.  It seems most of the issues here were cleared up one way or another, so I'm going to close this bug out (particularly given that most of them were reported using virtualbox).


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