Hi John, your system has (at the time of the logs) ~2.5G free and ~1.5G that it could free up. There is no swap set up. That is very likely to fail to be spawned and qemu is just telling you so. There is nothing that qemu does "wrong" if it just can't get as much memory as it needs.
I have read quickly into [1] where this maas tunable is defined. And setting 10 only allows you to try to define guests up to such size. But you need sooner or later some space those can live in. Overcommit is only good until used and sizing of a machine should always have at least the required amount as swap or - even if you are lucky and can start things - you might later on crash hard on an OOM which is even worse. @Maas team - do you ensure that (memory*ratio)+baseConsumption (e.g. 15%) is <= memory+swap of the system (as an upper limit)? If not such issues as seen here will happen and I don't yet see any component doing wrong. [1]: https://docs.maas.io/2.4/en/nodes-comp-hw#configuration ** Changed in: maas Status: Incomplete => New ** Changed in: qemu (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831134 Title: Pods Cannot allocate memory, even with memory_over_commit_ratio set 10.0 To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1831134/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
