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

PXE Boot: Invalid or corrupt kernel image #2300

Closed
b1zzu opened this Issue Dec 21, 2017 · 6 comments

Comments

Projects
None yet
3 participants
@b1zzu

b1zzu commented Dec 21, 2017

I followed the tutorial at: https://coreos.com/os/docs/latest/booting-with-pxe.html
but when i start the installation I get this error:

 Invalid or corrupt kernel image

I have download the coreos_production_pxe.vmlinuz image from here: https://stable.release.core-os.net/amd64-usr/current/coreos_production_pxe.vmlinuz where the last current version is 1576.4.0

The machine is a VM on VmWare vShpere with BIOS

@dm0-

This comment has been minimized.

Show comment
Hide comment
@dm0-

dm0- Dec 21, 2017

Member

Your link is to the PGP signature. Try https://stable.release.core-os.net/amd64-usr/current/coreos_production_pxe.vmlinuz; it's working for me.

Member

dm0- commented Dec 21, 2017

Your link is to the PGP signature. Try https://stable.release.core-os.net/amd64-usr/current/coreos_production_pxe.vmlinuz; it's working for me.

@dm0- dm0- closed this Dec 21, 2017

@b1zzu

This comment has been minimized.

Show comment
Hide comment
@b1zzu

b1zzu Dec 21, 2017

I have copied the wrong link inside the ticket I used coreos_production_pxe.vmlinuz file and to be sure I test it again but i receive the same error

Invalid or corrupt kernel image

I have even tried to download the iso, extract the vmlinuz from there but nothing changed.

b1zzu commented Dec 21, 2017

I have copied the wrong link inside the ticket I used coreos_production_pxe.vmlinuz file and to be sure I test it again but i receive the same error

Invalid or corrupt kernel image

I have even tried to download the iso, extract the vmlinuz from there but nothing changed.

@dm0-

This comment has been minimized.

Show comment
Hide comment
@dm0-

dm0- Dec 21, 2017

Member

Okay, then can you verify the signature to make sure your download wasn't corrupted. The kernel image has no problem booting for me, but I don't have vmware available to try it right now.

Member

dm0- commented Dec 21, 2017

Okay, then can you verify the signature to make sure your download wasn't corrupted. The kernel image has no problem booting for me, but I don't have vmware available to try it right now.

@dm0- dm0- reopened this Dec 21, 2017

@b1zzu

This comment has been minimized.

Show comment
Hide comment
@b1zzu

b1zzu Dec 21, 2017

I used this command:

gpg --verify coreos_production_pxe.vmlinuz.sig

and the signature is right

b1zzu commented Dec 21, 2017

I used this command:

gpg --verify coreos_production_pxe.vmlinuz.sig

and the signature is right

@lucab

This comment has been minimized.

Show comment
Hide comment
@lucab

lucab Jan 17, 2018

Member

@davbizz if this is still an issue, can you please attach your PXE entry config? Can you also check/attach logs from your PXE/TFTP server to make sure that the VM is using the proper server and hitting the correct endpoint?

Member

lucab commented Jan 17, 2018

@davbizz if this is still an issue, can you please attach your PXE entry config? Can you also check/attach logs from your PXE/TFTP server to make sure that the VM is using the proper server and hitting the correct endpoint?

@lucab

This comment has been minimized.

Show comment
Hide comment
@lucab

lucab Apr 11, 2018

Member

Lacking any further feedback and any reproducer, I'm going to close this ticket. If anybody is hitting this, please open a new bug and attach the full PXE configuration and relevant logs from the server.

Member

lucab commented Apr 11, 2018

Lacking any further feedback and any reproducer, I'm going to close this ticket. If anybody is hitting this, please open a new bug and attach the full PXE configuration and relevant logs from the server.

@lucab lucab closed this Apr 11, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment