Description of problem: I have added F17 support to oz, which is an image builder for virtual machines. I installed Fedora 17 and used the generated kickstart file to seed the kickstart file for oz. I didn't modify the kickstart file created from the install at all. To try oz, pull the repo: git clone git://github.com/sdake/oz.git make rpm rpm -ivh (the rpm created by oz) Running oz creation with the kickstart file (oz/oz/auto/fedora-17-jeos.ks - attached) results in failure. Version-Release number of selected component (if applicable): Fedora 17 iso How reproducible: 100% Steps to Reproduce: Use F16 as a the base OS 1. install updated OZ from above forked repo 2. Put the iso image file in /var/lib/libvirt/images 2. run oz-install F17-x86_64-cfntools-jeos.tdl 3. open virtual machine manager and watch the install fail Actual results: booting fails with: dracut Warning: Unable to process initqueue dracut Warning: /dev/root does not exist Dropping to debug shell Expected results: oz install works properly Additional info: I used the kickstart that was created from installing a f17 using virtual machine manager. If the kickstart generated by the install isn't correct, could I get some guidance for a proper kickstart file?
Created attachment 589572 [details] oz tdl file for F17
Created attachment 589573 [details] fedora 17 kickstart file generated by installing F17 in a virtual machine
Created attachment 589581 [details] actual f17 kickstart file used in oz (last one was wrong repo)
This may be user error, but is definitely a change in functionality from F16->F17. Documenting in bugzilla so others that run into this problem understand the problem. Previously oz used the kernel command ks=cdrom:/ks.cfg. Reading the kickstart docs, the correct syntax is ks=cdrom:/dev/cdrom:/ks.cfg. Changing to the proper syntax makes the software work, although other software may depend on the previous behavior where just cdrom:/ks.cfg worked properly.
*** This bug has been marked as a duplicate of bug 828589 ***