Maybe because xen is a type 1 hypervisor in its original meaning and all the other ones are type 2? (yes, ESX(i) doesn't use linux but it also brings its own os on which it runs on top)
That works if there is enough memory after the "bad" process has been killed. The question is, is it necessary? Many systems can live with processes performing a little bit poorly for some minutes and I wouldn't do it.
It's fine that "many systems" can. But there is no easy way when the user or system can't. Flushing back to RAM is slow - that's not controversial. So it would help if there was a way to do this in advance of the need for the programs where that matters.
> The question is, is it necessary? Many systems can live with processes performing a little bit poorly for some minutes and I wouldn't do it.
The outage ain't resolved until things are back to operating normally.
If things aren't back to 100% healthy, could be I didn't truly find the root cause of the problem - in which case I'll probably be woken up again in 30 minutes when the problem comes back.
Imo that's a pretty complicated topic. On one side if you just build LWRs you just don't need very highly enriched uranium or plutonium so posession of those is a red flag. On the other side fast breeder reactors are the ones which are able to produce the least harmful waste. But fast breeders and closed fuel cycles produce and handle plutonium which in turn can be used for bad things.
Linux kernel image or another stage of bootloader loaded by the GPU is pretty normal in mobile SOCs like the one that is used here. At least they did not enable secure boot so that it's still possible to execute something else.
Because WinApps is just a collection of Bash scripts, and not everyone might want to work on a project of this scale using Bash. In fact, I was considering a rewrite of WinApps myself, using Rust and egui, but never got around to it...
I still remember how we installed Windows PCs at home if no media with the latest service pack was available. Install Windows, download service pack, copy it away, disconnect from internet, throw away everything and install Windows again...