4 ms·
> I am curious about what scenarios would make one want to use systemd-boot (or grub) instead. I have Linux VMs which boots in ~2s (to ssh login; ~700ms to use
by rfoo 4y ago
> I am curious about what scenarios would make one want to use systemd-boot (or grub) instead.
I have Linux VMs which boots in ~2s (to ssh login; ~700ms to userspace). I use systemd-boot because it has nicer integration with my distro of choice than bare EFI stub, and it adds very minimal overhead in boot time.
- alias_neo 4y agoThat's pretty impressive, can you share some information about what you're using to achieve that?
- rfoo 4y agoMy preferred distro is Debian. Use linux-image-cloud; use a modern hypervisor with no legacy devices (only virtio etc); use tiny-initramfs; mask systemd-networkd-wait-online.service; add cryptomgr.notests noreplace-smp to kernel command line. I think that's all, and use a moderately fast CPU (i7-8700K which is already 5 years old).
- alias_neo 4y agoAmazing, thanks for the reply! Debian is my preferred base so I'll give this a try! When you say modern hypervisor, do you mean, not KVM? How do you get around the UEFI/BIOS post time which is usually a few seconds by itself?
- bityard 4y agorfoo is saying that their VMs boot in under 2 seconds, not the hypervisor host.
- alias_neo 4y agoI didn't ask about the Hypervisor host. I'm talking about the time taken by OMVF/SeaBIOS or whatever equivalent in the VM; which is why I asked about the type of VM/Hypervisor because that might not apply.