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.

Sign up for GitHub

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

Jump to bottom

Debian unstable with HostonlyInitrd enabled fails to boot in QEMU #562

Closed
DaanDeMeyer opened this issue Dec 10, 2020 · 0 comments · Fixed by #636
Closed

Debian unstable with HostonlyInitrd enabled fails to boot in QEMU #562

DaanDeMeyer opened this issue Dec 10, 2020 · 0 comments · Fixed by #636
Labels
bug

Comments

@DaanDeMeyer
Copy link
Contributor

Error: [FAILED] Failed to start Switch Root.

Suspicious logs:

Dec 10 18:44:52 localhost systemd-gpt-auto-generator[213]: EFI loader partition unknown, exiting.
Dec 10 18:44:52 localhost systemd-gpt-auto-generator[213]: (The boot loader did not set EFI variable LoaderDevicePartUUID.)

Config to reproduce:

[Distribution]
Distribution=debian
Release=unstable

[Output]
Bootable=yes
HostonlyInitrd=yes

[Host]
QemuHeadless=yes
@DaanDeMeyer DaanDeMeyer mentioned this issue Dec 10, 2020
Merged
@DaanDeMeyer DaanDeMeyer changed the title Debian unstable with HostonlyInitrd enables fails to boot in QEMU Debian unstable with HostonlyInitrd enabled fails to boot in QEMU Dec 21, 2020
bluca added a commit to bluca/mkosi that referenced this issue Dec 23, 2020
@bluca
Debian: ensure efivars.ko is installed if uefi is used
e59b4e0 
When --hostonly is used, efivars.ko is missing and thus the bootloader
cannot get the UUID of the EFI partition and fails to pivot root.
Specify it manually with add_drivers+=efivarfs if building for Debian
with EFI.

Fixes systemd#562
Werkov added a commit to Werkov/mkosi that referenced this issue Jan 21, 2021
@Werkov
UEFI boot: make sure efivarfs loaded in initrd
7b9eff8 
The efivarfs is needed in order to GPT root partition discovery work.
Without efivarfs initrd won't be able to switch to the real root.
(Make module inclusion distro specific in case it's included by other
reasons.)

Fixes systemd#562
@Werkov Werkov mentioned this issue Jan 21, 2021
Merged
Werkov added a commit to Werkov/mkosi that referenced this issue Jan 22, 2021
@Werkov
UEFI boot: make sure efivarfs loaded in initrd
b3c3927 
The efivarfs is needed in order to GPT root partition discovery work.
Without efivarfs initrd won't be able to switch to the real root.

Add the module regardless of hostonly or distro configuration because
dracut takes into account info from the build host and not the target
distro. Adding a module that's already included in dracut's list makes
no harm.

Fixes systemd#562
DaanDeMeyer pushed a commit that referenced this issue Jan 22, 2021
@Werkov @DaanDeMeyer
UEFI boot: make sure efivarfs loaded in initrd
092b12d 
The efivarfs is needed in order to GPT root partition discovery work.
Without efivarfs initrd won't be able to switch to the real root.

Add the module regardless of hostonly or distro configuration because
dracut takes into account info from the build host and not the target
distro. Adding a module that's already included in dracut's list makes
no harm.

Fixes #562
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

RFC UEFI boot: make sure efivarfs loaded in initrd Werkov/mkosi
1 participant
@DaanDeMeyer