I'm running KDE Linux in a QEMU/KVM virtual machine. This is the FASTEST loading Linux distro I've ever tried! From the time I launch the VM to an active Desktop is less than 20-seconds!
-
Windows no longer obstruct my view.
Using Kubuntu Linux since March 23, 2007.
"It is a capital mistake to theorize before one has data." - Sherlock Holmes -
Nice to know
Dave Kubuntu 20.04 Registered Linux User #462608
Wireless Script: http://ubuntuforums.org/showthread.p...5#post12350385 -
I suspect some of it is that it isn't using Grub.
Comment
-
Or maybe not.
Kubuntu 24.04 on the SATA drive
This does include loading Jellyfin as well, so that probably adds some extra time. Otherwise it is a 95% stock Kubuntu, now that the old puppy has retired from daily desktop duties.Code:mini@minime:~$ systemd-analyze Startup finished in 3.580s (firmware) + 5.896s (loader) + 2.889s (kernel) + 13.065s (userspace) = 25.432s graphical.target reached after 13.051s in userspace.
KDE Linux on NVME
Code:[banana@banana:~] $ systemd-analyze Startup finished in 12.032s (firmware) + 8.739s (loader) + 1.107s (kernel) + 3.006s (initrd) + 9.809s (userspace) = 34.696s graphical.target reached after 5.366s in userspace.
But here the only real difference is the time mine spends in the firmware (aka the BIOS) before going to the bootloader.
I saw similar firmware times with other OS loading from an NVME, so it is definitely hardware/firmware related, specifically on this 2017 HP Elitedesk 800 G3 Mini. I hadn't checked boot times from a SATA drive on this machine before this past month. I beleive the m.2 slot was more intended for Optane usage, maybe.
I will wager the emulated and smaller/simpler UEFI on virtual machines also makes a bit of a difference as well.
Interesting.
Last edited by claydoh; Dec 07, 2025, 06:35 PM.Comment
-
Not totally relevant, just curious, my 22.04 on SSD:
It seems fast when I actually do it, too.Code:systemd-analyze Startup finished in 9.814s (firmware) + 7.885s (loader) + 3.789s (kernel) + 1min 1.378s (userspace) = 1min 22.868s graphical.target reached after 1min 1.357s in userspace
An intellectual says a simple thing in a hard way. An artist says a hard thing in a simple way. Charles BukowskiComment
-
Like I said, FAST!Code:systemd-analyze Startup finished in 879ms (kernel) + 1.391s (initrd) + 4.719s (userspace) = 6.990s graphical.target reached after 4.716s in userspace.
Windows no longer obstruct my view.
Using Kubuntu Linux since March 23, 2007.
"It is a capital mistake to theorize before one has data." - Sherlock HolmesComment
-
Dual booting CachyOS for testingCode:systemd-analyze Startup finished in 9.611s (firmware) + 10.308s (loader) + 5.975s (kernel) + 6.434s (userspace) = 32.329s graphical.target reached after 6.431s in userspace.
Last edited by cookiemuncher; Jan 02, 2026, 02:05 AM.Comment
-
I wonder why it skips the firmware time.Originally posted by Snowhog View Post
My PC (neon) would be blazing fast except it likes to hang around in the firmware before getting to the bootloader. I *think* I may have turned off the quick boot bios feature, maybe.
My KDE Linux install on my old Elitedesk Mini likes to hang around the boot loader (which is NOT grub btw).Code:$ systemd-analyze Startup finished in 19.456s (firmware) + 5.009s (loader) + 4.088s (kernel) + 6.600s (userspace) = 35.154s graphical.target reached after 6.577s in userspace.
My userspace is longer here as I have some things loading at login, like Jellyfin.Code:[banana@banana:~] $ systemd-analyze Startup finished in 3.562s (firmware) + 13.920s (loader) + 1.110s (kernel) + 3.509s (initrd) + 16.692s (userspace) = 38.796s graphical.target reached after 9.709s in userspace.
Last edited by claydoh; Jan 02, 2026, 02:39 AM.Comment
-
Would it be because I'm running KDE Linux in a VM?Originally posted by claydoh View PostWindows no longer obstruct my view.
Using Kubuntu Linux since March 23, 2007.
"It is a capital mistake to theorize before one has data." - Sherlock HolmesComment
Comment