Created attachment 365056 [details] what I see in console 3 during initial phases of rescue installation Description of problem: I have qemu/kvm with host based on f11 x86_64 and rawvirt repo as of 16th Ocgtober. I have a guest that is a rawhide pre beta x86_64. This guest has some problem in root fs and I want to use f12 beta rc2 to rescue it. I start guest from cd that actually is the iso downloaded (sha256sum is ok) and select "rescue installed system" option from menu. In installation window I get the choose language, choose keyboard and then, strange, the select partition window .... it seems it is searching the installation image for fedora as when you install from hard disk????? I get the attached screen shot in console 3 if it may be useful. If instead I do the same but in first screen I select "install or upgrade system" it works ok, in the sense that I arrive up to the window when it asks if I want to reinstall or upgrade; then I power off. Version-Release number of selected component (if applicable): anaconda as in dvd x86_64 F12 beta rc2 How reproducible: always Steps to Reproduce: 1. power on x86_64 dvd iso as cdrom in guest 2. select rescue installed system 3. go through choose language and choose keyboard windows Actual results: window asking to selecgt partition for install image Expected results: usual message that now anaconda is going to mount installed os filesystems and that I can do a chroot environment.... Additional info:
Any chance you can also grab all the logs from this system when you encounter the strange behavior? Change to tty2 and grab /tmp/*log*. You can activate networking from tty2 and scp them to another system as well. Please attach those files to this report.
If you let the system sit at the 'waiting for hardware' screen long enough, rescue proceeds.
answer to comment #1: unfortunately it seems that the installation aborts at a stage where in tty2 I don't have a shell yet... on monday I'll try. Or during week end if possible I'm going to reproduce @home.... (actually I doubt it:too many birthdays this weekend: father and wife ;-)
I've seen that issue before with my XO, with 256 megs of ram. Think what is happening is that there is not enough memory to hold the install.img in ram. Note the amount of memory found, and the (null) by the mount command, this was the driving force in my patches for the mounting of hdinstalls' without copying to /tmp like booting the CDROM does.
You could try appending text to the boot line, that should skip the copying install.img to ram.
*** Bug 531304 has been marked as a duplicate of this bug. ***
This is fixed by this patch: https://www.redhat.com/archives/anaconda-devel-list/2009-November/msg00096.html Which I've added to my local tree, which will get pushed to master as soon as a few other patches are reviewed. anaconda-13.8 should have this fix included.
Pushed to master: http://git.fedorahosted.org/git/?p=anaconda.git;a=commitdiff;h=a9e2e9a40532120ad9545cf677a65d6727b21c10