-
-
Notifications
You must be signed in to change notification settings - Fork 185
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 iso boot fails. Tested: Ubuntu and QubesOS #470
Comments
From u-root slack: Here what i've found:
|
@flammit :
|
So my bad for Debian/Ubuntu it was documented in the Wiki. Will test, but thought that it would have been fixed. From predent picture, we can see that $ISO_PATH doesn't seems to expend and is left to be
@flammit : But for QubesOS, I would have expected it to work out of the box. |
Sorry in advance for poor pictures.... Have to replace that broken lens ASAP. @flammit : To reproduce: Under Dom0: in VM terminal:
from Heads recovery shell:
Booting from USB results in a validated configuration: When attempting Install options 3 and 4: Booting option 3 or 4 results in an instant reboot. |
@tlaurion I just tested Ubuntu 16.04.3 / Ubuntu 18.04.1 / Debian Live 9.5.0 / Qubes 4 installer and they all booted fine for me from ISO. If you're using master, this should work for the plain ISO's with just a detached signature and it doesn't require the Note that in your screenshots, that blank I vaguely recall having an issue later on in the Qubes 4 install where it couldn't find packages when installing from ISO, so I had to revert to a |
@Pant1993 : This is not iso boot. Additionally, it seems to be linuxboot on top of qemu? Please open another issue with more details:
Normally, if you let it die from timeout, you should get additional details. I suppose mapped disk which was passed to kexec call cannot be found from qemu but that needs to be documented so someone playing with qemu can answer properly. |
Yes it is not an iso boot, was trying to boot from Ubuntu 18.04 bootable USB drive. I waited for long time, it doesn't timeout. |
@flammit @osresearch
I'm trying to use iso boot without success. Tried QubesOS and Ubuntu.
I never retested this code path because I knew that it was broken, the mitigation being to
dd
the iso image directly into a SD card and boot directly from it from Heads, which always worked for QubesOS without added integrity validation functionalities. That's the mitigation I used until now, but i'm running out of free SD cards and USB drives. Plus... It would make total sense to have a single USB drive/SD card for all boot needs. :)For QubesOS, the public signature being included in the rom makes the integrity validation works out of the box, but the booting of the ISO doesn't find the root of the iso filesystem:
For Ubuntu, I had to
gpg --sign --armor --detach Ubuntu.iso
from recovery console:@flammit: I remember there were some magic to be applied to the boot line. Thought it was
iso-scan/filename
but it doesn't seem to be applied to all discovered boot configurations. The result of attempting to boot any configuration is a reboot.The text was updated successfully, but these errors were encountered: