that us "overselling RAM" on KVM machines and processes arbitrarily killed via OOM killer (which for some reason did not choose biggest consumer, but the literally smallest 512MB VM

I have no problems with Debian on a 512MB AlphaVPS KVM.

We are running idling Debian 13 in Limitless Hosting $3/year 512MB IPv6-only KVM.

https://support.solusvm.com/hc/en-us/articles/13268133793431-KVM-on-SolusVM-is-randomly-stopped-or-suspended-because-host-node-OOM-kills-corresponding-qemu-process

(Quote)

(Quote)

(Quote)

(Quote)

(Quote)

Yep, or a hard 512M limit for the KVM process (which includes, apart from the guest-usable memory, some overhead like Video RAM, ...).

Swap is managed by the guest kernel. For the kernel to move pages to swap, it needs to reach a memory threshold first. However, this provider's hypervisor is so aggressive that it kills the entire KVM

OVZ is different since it's a container. On KVM the guest OS handles its memory management on its own and if it is not able to use all memory that has been allocated, it will end up very bad.

This sounds weird, that's not really how KVM works. Guest can not exceed the allocated memory limit so it doesn't make sense for the host to "kill" the VM. Maybe your guest OS crashe

I ordered a 512MB RAM KVM VPS to run a minimal Debian 12 setup. As we all know, Debian 12/13 runs perfectly fine on 512MB for headless tasks. However, I encountered constant, instant shutdowns.

Maxko and PipeHost (/pfcloud) are already the go-to options in HR and SI locations respectively.

* Virtualization: KVM preferred

Platform: KVM

(Quote)

(Quote)

(Quote)