Description of problem: If I boot anaconda using vmlinuz+initrd with this argument: inst.repo=nfs:nfs.englab.brq.redhat.com:/pub/fedora/fedora-alt/stage/18-Alpha-TC5/Fedora/x86_64/os/ I see this message: dracut-initqueue[290]: mount.nfs: Protocol not supported dracut-initqueue[290]: Warning: Couldn't mount nfs:,nfsvers=3:nfs.englab.brq.redhat.com:/pub/fedora/fedora-alt/stage/18-Alpha-TC5/Fedora/x86_64/os/ dracut-initqueue[290]: Warning: no suitable images dracut-initqueue[290]: Warning: Could not boot. The NFS directory can be mounted on an ordinary machine, but dracut doesn't seem to support it. Version-Release number of selected component (if applicable): F18 Alpha TC5 How reproducible: always
Proposing as Beta blocker: " 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). This must work if the remote source is not a complete repository but contains only the files necessary for the installer itself to run. " https://fedoraproject.org/wiki/Fedora_18_Beta_Release_Criteria
dracut works very well with nfs3 and nfs4. It's probably anaconda which has faulty scripts here.
I have a similar problem but don't know enough about anaconda and so forth to know if is exactly the same one as you had: https://bugzilla.redhat.com/show_bug.cgi?id=853508
*** This bug has been marked as a duplicate of bug 855170 ***