On Tue, Sep 22, 2026, Ritesh Harjani (IBM) wrote: > hardware_disable_test forks several VMs (NR_IERATIONS=512). This patch > limits that number to 4 when we know that we are running in constraint > host environment. The number 4 is just a safe minimum when > kvm_arch_vm_create_may_enomem() can be true.
Please actually explain *why* this is necessary, and where the magic '4' comes. I assume there's some system-wide resource at play?
