Bug 836392
Summary: | kexec'ing F15 installer works, but fails with F17 | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | joshua |
Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> |
Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 17 | CC: | anaconda-maint-list, dcantrell, g.kaviyarasu, jonathan, vanmeeuwen+fedora |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-10-23 17:51:42 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
joshua
2012-06-28 22:08:24 UTC
We've never made any promises about anaconda working with kexec. However there is a whole lot that can go wrong that results in that error message. I can't tell without seeing your logs though. Understood, my point here is that it works nicely in Fedora 15, and dies early before even attempting stage two in Fedora 17. Where does dracut keeps its logs and record kernel-command line inputs? If you boot with rd.debug you'll find the logs in /run/initramfs/init.log The kernel command line inputs can be found in /proc/cmdline Wow, there is a lot there. Any ideas on where I should start looking, or what I should be looking for? Honestly I don't know. kexec isn't a thing we support. I'd suggest working with the kexec folks to see what looks "normal" and what looks broken. Is there an easy way to get the logs off such that I could post them here? I don't seem to have an IP stack inside of dracut debug If you exit the debug shell and get into the anaconda shell you should be able to find the logs in /run/initramfs/init.log and should have enough bits to get IP working. I give up. It is a mess, and I don't understand dracut's init.log entries enough to identify the problem. It looks like a udev settling issue, but I can't be sure. I figured it out. It has nothing to do with dracut at all... it is that between F15 and F17, anaconda got much pickier about BOOTIF=MAC That MAC must now have a "01-" prepended to the beginning ... just like SYSLINUX/PXELINUX does. Anaconda would take the real MAC with the "01-" in Fedora 15. Just posting in case this matters to anyone else. |