Bug 707611 - VirtualBox - can't boot Fedora
Summary: VirtualBox - can't boot Fedora
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 15
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-25 14:07 UTC by Filip Bartmann
Modified: 2011-08-23 16:08 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-08-23 16:08:23 UTC
Type: ---

Attachments (Terms of Use)
Screen capture with error messages (33.48 KB, image/png)
2011-05-25 14:07 UTC, Filip Bartmann 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Filip Bartmann 2011-05-25 14:07:55 UTC 
Created attachment 500828 [details]
Screen capture with error messages

Description of problem:
When I try to boot Fedora 15 in VirtuelBox, then boot hangs on Started udev Kernel Device Manager

How reproducible:
Try to boot Fedora 15 in VirtualBox

  
Actual results:
Boot hangs on Started udev Kernel Device Manager
Then will be only error messages, that are targets /boot, Getty on tty* aborted because failed dependencies and system is switched into maintenance mode.
Screen is captured in attached image.

Expected results:
Booted Fedora into GDM

Additional info:
Comment 1 Eugene Goryachkin 2011-08-23 03:53:07 UTC 
Good day!
I have same problem, not with VirtualBox, but with my PC. Searching the Internet no results there...
Comment 2 Eugene Goryachkin 2011-08-23 03:56:28 UTC 
Good day!
I have same problem, not with VirtualBox, but with my PC. Searching the Internet no results there...
Comment 3 Harald Hoyer 2011-08-23 06:26:39 UTC 
[] piix4_smbus: SMBus base address uninitialized - upgrade BIOS or use force_addr=0xaddr
Comment 4 Chuck Ebbert 2011-08-23 16:08:23 UTC 
Please report problems with VirtualBox to its developers.
Note You need to log in before you can comment on or make changes to this bug.