Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

KEXEC_INITRD does not follow symlinks, while KEXEC_KERNEL does #179

Open
alexbakker opened this issue May 5, 2017 · 1 comment
Open

Comments

@alexbakker
Copy link

On Debian Jessie with linux-image-amd64 installed, /initrd.img and /vmlinuz are symlinks to the latest initrd and kernel available in /boot. Setting KEXEC_INITRD to /initrd.img and KEXEC_KERNEL to /vmlinuz results in the following:

>>> kexec: kernel=/vmlinuz initrd=/initrd.img append=''
wget: bad address ''
>>> kexec: initrd not found

Changing only KEXEC_INITRD to the full path: /boot/initrd.img-3.16.0-4-amd64, seems to fix the issue. I looked at the kexec portion of the init script but I couldn't figure out why this happens.

@alexbakker
Copy link
Author

Ok, so the actual issue appears to be that /initrd.img links to "/boot/initrd.img-3.16.0-4-amd64". If I change it to "boot/initrd.img-3.16.0-4-amd64", kexec works. Notice the missing /.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant