Bug 752315

Summary: System hangs on boot after upgrade of fc15 to fc16
Product: [Fedora] Fedora Reporter: Steve <lance.list.7>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED CANTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 16CC: dennis, frank.mehnert, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-11-09 18:15:04 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
screen shot of system
none
screen shot of system after mods none

Description Steve 2011-11-09 07:05:39 UTC
Description of problem:
System hangs on boot after upgrade

Version-Release number of selected component (if applicable):
Fedora 16

How reproducible:
every time

Steps to Reproduce:
1. boot after upgrade
  
Actual results:
system stops mid boot process

Expected results:
system should boot

Additional info:
the system is a virtual box client on a Fedora-15

Comment 1 Steve 2011-11-09 07:08:18 UTC
Created attachment 532469 [details]
screen shot of system

screen shot of system

rhgb and quiet flags removed from kernel boot parameters

Comment 2 Josh Boyer 2011-11-09 18:15:04 UTC
You probably need to rebuild something from virtualbox.  Fedora doesn't support virtualbox, so you might want to contact them about what should be done in this case.

Comment 3 Steve 2011-11-10 06:23:42 UTC
Created attachment 532730 [details]
screen shot of system after mods

system boots into rescue mode
yum remove dkms
removed vbox client via supplier procedure
still hangs as in screen shot

Comment 4 Frank Mehnert 2011-11-10 08:08:35 UTC
Steve, which version of VirtualBox are you using? Could you also attach a VBox.log file of that hanging VM session?