| Summary: | livecd-iso-to-pxeboot produces initrd that does not find root device | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Patrick C. F. Ernzer <pcfe> | ||||||||||
| Component: | livecd-tools | Assignee: | Brian Lane <bcl> | ||||||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
| Severity: | high | Docs Contact: | |||||||||||
| Priority: | medium | ||||||||||||
| Version: | 15 | CC: | adam.stokes, bcl, bruno, dhuff, harald, Jasper.Hartline, jonathan, katzj, mammar, mmello, sukesh.nischal | ||||||||||
| Target Milestone: | --- | ||||||||||||
| Target Release: | --- | ||||||||||||
| Hardware: | Unspecified | ||||||||||||
| OS: | Linux | ||||||||||||
| Whiteboard: | |||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | Type: | --- | |||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||
| Documentation: | --- | CRM: | |||||||||||
| Verified Versions: | Category: | --- | |||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||
| Bug Depends On: | |||||||||||||
| Bug Blocks: | 494832 | ||||||||||||
| Attachments: |
|
||||||||||||
Here's the PXE config that was generated on F15 # cat pxelinux.cfg/default DEFAULT pxeboot TIMEOUT 20 PROMPT 0 LABEL pxeboot KERNEL vmlinuz0 APPEND rootflags=loop initrd=initrd0.img root=live:/Fedora-15-i686-Live-Desktop.iso rootfstype=auto ro liveimg quiet rhgb rd.luks=0 rd.md=0 rd.dm=0 ONERROR LOCALBOOT 0 And here is what I got on RHEL6 (x86_64 Live image this time) # cat default DEFAULT pxeboot TIMEOUT 20 PROMPT 0 LABEL pxeboot KERNEL vmlinuz0 APPEND rootflags=loop initrd=initrd0.img root=live:/Fedora-15-x86_64-Live-Desktop.iso rootfstype=auto ro liveimg quiet rhgb rd.luks=0 rd.md=0 rd.dm=0 ONERROR LOCALBOOT 0 Unless I typoed, all the given options should have ended up in the PXE config I use (see previous comment) I don't know how much this is useful to you guys, but following is what i had experienced. I also got this issue while PXE booting my custom Fedora 15 spin. But now my spin boot successfully. What i did is, i reduced the spin size from 480 MB to 430 MB. RAM size is 2 GB when spin size is 480 MB RAM size is 1 GB when spin size is 430 MB So the memory size is not the issue. I made PXE images using livecd-iso-to-pxeboot.sh on Fedora 14. livecd-iso-to-pxeboot.sh is same in Fedora 14 and Fedora 15. I am seeing the same problem here, it complains about not being able to mount the root device and then there is a kernel traceback. I think this is a dracut problem. It should be mounting the iso but isn't. It also isn't dropping into a shell when passing rd.shell I tried this using a Fedora 15 livecd. Created attachment 511997 [details]
Screenshot of crash
(In reply to comment #4) > Created attachment 511997 [details] > Screenshot of crash this looks like no initramfs has been loaded at all, so config error err... and where can the image find the Fedora-15-x86_64-Live-Desktop.iso ?? initrd0.img generated by livecd-iso-to-pxeboot is 573M so I expect it all inside that file. Maybe my expectation is wrong. I doubt PXE pulls that much from the server :) Is the purpose of livecd-iso-to-pxe shell script to be able to actually PXE boot the LiveCD ISO it's self, or to load an initramfs and kernel which also contains the neccessary components for making an install attempt over a PXE booted kernel and intramfs? Is this script able to do both or is it currently targeted to do one or another of these things? reassigning to livecd-tools to get more info Well, for me the issue was RAM size. I bumped the KVM up to 2048MB and I can boot the image just fine. So, I cannot reproduce this here. (In reply to comment #12) > Well, for me the issue was RAM size. I bumped the KVM up to 2048MB and I can > boot the image just fine. So, I cannot reproduce this here. Weird, I have <memory>2097152</memory> <currentMemory>2097152</currentMemory> And it fails to boot. Created attachment 515760 [details]
virsh dumpxml output of the VM I use
Brian,
any major differences from what you use for the VM?
Created attachment 515768 [details]
output of virsh dumpxml for working virt
Here's mine. I don't see anything too obvious. I don't have a seclabel set, and you don't have any drives but that really shouldn't matter.
I can confirm the comments of Muhammad Ammar. I couldnt get this to work in any way with my custom Fedora iso, which was about 890 MB. I tried this in Vmware and tried giving the VM 8GB of ram to no avail. I stripped the ISO down to about 270MB and it worked. Now im not sure if this really is down to size or not. Previously I was using fedora-livecd-lxde.ks from spin-kickstarts. I just added a few extra packages from the defaults. But it never worked, no matter what I put in my PXE Linux config. Then I tried just using fedora-live-base.ks but I removed @base-x from the kickstart and it booted ok. So this is either down to size of the iso or something in fedora-livecd-lxde.ks which cause the boot to fail. This is starting to look like size matters. I used the default fedora-live-base.ks from spin-kickstarts and the resultant iso image managed to PXE boot past the problem. I then added @lxde-desktop to the package list to produce an iso which was about 450MB. This then had then problem, and wouldnt PXE boot with the same error The RAM size of the machine didnt seem to be relevant, I tried bumping up to 8GB and this image still wouldnt PXE boot. So what gives? Why is the size of the initrd important? This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping |
Created attachment 511275 [details] full console output from F15 Live i686 boot attempt Description of problem: livecd-iso-to-pxeboot makes an initrd which is unable to find root Version-Release number of selected component (if applicable): livecd-tools-15.7-1.fc15.x86_64 and livecd-tools-13.3-1.el6.x86_64 How reproducible: always Steps to Reproduce: 1. cd /tmp/test 2. have a verified Fedora-15-i686-Live-Desktop.iso in /tmp/test 3. livecd-iso-to-pxeboot Fedora-15-i686-Live-Desktop.iso 4. copy initrd0.img and vmlinuz0 to my RHEL6 tftp server 5. add a PXE target with all the options livecd-iso-to-pxeboot generated except quiet Actual results: kernel and initrd load fine then root is not found ... [ 1.328997] VFS: Cannot open root device "live:/Fedora-15-i686-Live-Desktop.iso" or unknown-block(0,0) [ 1.331107] Please append a correct "root=" boot option; here are the available partitions: [ 1.332582] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) Expected results: livecd-iso-to-pxeboot working both in EPEL6 and F15 Additional info: the exact PXE target I use is label F15-Live-i686 MENU LABEL F15 Live i686 KERNEL images/F15-Live-i686/vmlinuz0 APPEND rootflags=loop initrd=images/F15-Live-i686/initrd0.img root=live:/Fedora-15-i686-Live-Desktop.iso rootfstype=auto ro liveimg rhgb rd.luks=0 rd.md=0 rd.dm=0 'quiet' was dropped. To retrieve the above log, I also added console=ttyS0 Result is the same whether I use livecd-iso-to-pxeboot on RHEL6 or F15, strangely the initrd they produce is not the same (sha1sum differs, but I did not look inside yet.