Bug 646818 - Installation of Fedora-14-Beta-x86_64-netinst.iso and Fedora-14-Beta-i386-netinst.iso hang both in KVM and VirtualBox
Summary: Installation of Fedora-14-Beta-x86_64-netinst.iso and Fedora-14-Beta-i386-net...
Keywords:
Status: CLOSED DUPLICATE of bug 621893
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 14
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-26 11:25 UTC by Andrey Panasyuk
Modified: 2010-10-26 22:17 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-10-26 22:17:26 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Andrey Panasyuk 2010-10-26 11:25:42 UTC 
Description of problem:

Installation of both i386 and x86_64 versions of Betas fail. Black screen is displayed after choosing "Skip" item on the screen of verifying media. Processor is not used, harddrive is not used too,

The situation is absolutely the same on VirtualBox and QEMU for both versions despite of the video driver settings.

Graphical install of Debian 5.05(debian-505-i386-netinst.iso) works fine everywhere.

How reproducible:
Every time.

Steps to Reproduce:
1. Create a virtual machine.
2. Attach netinst ISO.
3. Try to install the distro.
  
Actual results:
Installation hangs after pressing Skip on check media screen.

Expected results:
Installation should continue.

Additional info:
Fedora 13 with all of the latest updates. 
Kernel: 2.6.34.7-61.fc13.x86_64
Oracle VirtualBox 3.2.10. The same problems on VirtualBox-OSE.
QEMU. 0.12.5
NVidia Driver: 260.19.12

Sha256 of the installing ISO for x86_64: aa170fab83bc78a59c6c48320741da6d0d40a79e6aeb62f0b3c2dad464e3e5c7
Comment 1 Andre Robatino 2010-10-26 20:57:06 UTC 
Looks like a duplicate of bug 621893.
Comment 2 Brian Lane 2010-10-26 22:17:26 UTC 

*** This bug has been marked as a duplicate of bug 621893 ***
Note You need to log in before you can comment on or make changes to this bug.