Description of problem: If I boot vmlinuz+initrd and provide inst.repo=http://repo argument to the kernel line, anaconda fails to boot. The problem is probably in dracut, it doesn't download the stage2 image. > dracut-initqueue[290]: Warning: Could not boot. > dracut-initqueue[290]: Warning: /dev/root does not exist > > Entering emergency mode. Exit the shell to continue. > Type "journalctl" to view system logs. > > dracut:/# Version-Release number of selected component (if applicable): F18 Alpha TC3 How reproducible: always
Created attachment 605687 [details] boot.log
Created attachment 605688 [details] boot-debug.log
I tried inst.repo=ftp://, it doesn't work either. Nominating as Alpha blocker: " The installer must be able to use at least one of the HTTP or FTP remote package source options " https://fedoraproject.org/wiki/Fedora_18_Alpha_Release_Criteria
That's a really broad criterion, though, and you should still be able to use the UI to enter an HTTP/FTP source which would therefore take care of that.
To tell the truth, I'm not sure whether that criterion refers to adding a custom repository in the UI or to the kernel boot options. PXE boot itself is listed in Beta criteria. Let's discuss at blocker bug meeting.
Discussed at 2012-08-20 QA meeting, acting as a blocker review meeting: http://meetbot.fedoraproject.org/fedora-meeting/2012-08-20/fedora-qa.2012-08-20-15.00.html . Accepted as a Beta blocker per criterion "It must be possible to install by booting the installation kernel directly, including via PXE, and correctly specifying a remote source for the installer itself, using whichever protocols are required to work for package retrieval at the current phase (Alpha, Beta, Final)..." - that's really what this bug is about, the repo is being used as a source for the installer, not just for packages. This bug does not necessarily indicate that inst.repo= doesn't work as a simple package source.
'set_neednet' was broken, so the network never came up, so nothing ever got fetched. *** This bug has been marked as a duplicate of bug 849672 ***