News for hackers. Stuff that matters.
Re:I replaced grub with systemd-boot by rfoo on Friday February 17, 2023 @12:18AM (#34831074)
> 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.

Re:I replaced grub with systemd-boot by alias_neo on Friday February 17, 2023 @04:14AM (#34832568)
That's pretty impressive, can you share some information about what you're using to achieve that?
Re:I replaced grub with systemd-boot by rfoo on Friday February 17, 2023 @08:26AM (#34834370)
My 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).

Re:I replaced grub with systemd-boot by alias_neo on Sunday February 19, 2023 @03:53PM (#34861757)
Amazing, 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?

Re:I replaced grub with systemd-boot by bityard on Tuesday February 21, 2023 @02:11PM (#34885489)
rfoo is saying that their VMs boot in under 2 seconds, not the hypervisor host.
Re:I replaced grub with systemd-boot by alias_neo on Wednesday February 22, 2023 @05:41AM (#34893910)
I 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.