Description of problem: [anaconda] The installation halted when clicking 'Skip' button (Virtual machine, Network Install, select 'Skip entering Installation Number') Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1.Install OS via http://download.englab.nay.redhat.com/pub/rhel/rel-eng/RHEL5.8-Client-20120105.0/5/x86_64/os/ or Snapshot-3.0 build ttp://download.devel.redhat.com/rel-eng/RHEL-5.8-Server-Snapshot-3.0/5/x86_64/os/ 2.Select "Skip entering Installation Number". 3.Click "Skip" Actual results: The installation halted when clicking 'Skip' button Expected results: The anaconda installation should work as normally. Additional info: anyway, enter the installation number and click OK, had the same issue for snapshot-3 build.
Created attachment 551526 [details] cannot install rhel5.8 snapshot3 build
There is not enough information in this bug report to determine what the problem is. When you skip the installation number entry, can you switch to tty2 and grab /tmp/syslog and /tmp/anaconda.log and attach them to this bug report?
(In reply to comment #3) > There is not enough information in this bug report to determine what the > problem is. When you skip the installation number entry, can you switch to > tty2 and grab /tmp/syslog and /tmp/anaconda.log and attach them to this bug > report? Select 'Skip entering Installation Number' and click OK, switch to tty2(if click 'Skip' button in the 'Skip' dialog, it's halted and cannot switch to tty2 in virtural machine.), please refer to the attached log files.
Created attachment 551746 [details] anaconda.log
Created attachment 551747 [details] syslog
while i386 arch installed properly, I am getting problem with x86_64 only with: anaconda-11.1.2.250-1.x86_64.rpm
not only network, I can reproduce it with cdrom, so remove network install from summary.
Was able to reproduce the problem using the latest 5.8 Server nightly on download.devel.redhat.com. It's a kernel panic. Attaching a PNG which captures what I can from the virt-manager window. After you click Skip on the dialog box, anaconda moves on to storage device detection, if that helps at all.
Created attachment 552187 [details] panic.png
There are no details to this bug! Even its not mentioned the kvm is used (I detected it from the logs). What is the host its running on? rhel5 or rhel6? What's the guest xml or qemu command line? I see some scsi issues and we do not support scsi (not sure the issues are related). KVM barely changed in 5.8 so I doubt its a virt issue. Is this a regression (yes..)? and if it is, what's the last known version it worked?
Yes, definitely a dup. Leaving open as TestOnly just to be sure.
Verified that the bug has been fixed now on x86_64 Client. Steps can be seen at comment 0. Move to verified.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2012-0150.html