Date: Mon, 26 Jun 2023 08:06:27 -0400 From: Aryeh Friedman <aryeh.friedman@gmail.com> To: Vitaliy Gusev <gusev.vitaliy@gmail.com> Cc: FreeBSD virtualization <freebsd-virtualization@freebsd.org>, FreeBSD Mailing List <freebsd-questions@freebsd.org> Subject: Re: bhyve: how to keep the host from starving the guest Message-ID: <CAGBxaXkY70PSC1qb1VsJUq_3UG0K5M2HruBoC40c66wun%2BcseA@mail.gmail.com> In-Reply-To: <48D9FE17-B885-40AC-8958-EA90EEB9D8B6@gmail.com> References: <CAGBxaXkcBuu70SjjW4ci-6Lhv24gqowf6T2Rj4Aig4sZLt-Tvg@mail.gmail.com> <48D9FE17-B885-40AC-8958-EA90EEB9D8B6@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jun 26, 2023 at 7:50=E2=80=AFAM Vitaliy Gusev <gusev.vitaliy@gmail.= com> wrote: > > Hi Aryeh, > > Have you wired a guest memory with bhyve's -S option? > > -S Wire guest memory > > > Anyway, OS does not have another choice than kill a process to free some = memory > when RAM+swap is fully used (assume kernel already scanned Inactive memor= y). > > As recommendation: > > Look at an another memory consumers like ZFS, another processes > Increase swap > Tune vm.overcommit sysctl. See tuning(7) for details. > > > So in short, there is no good way to run applications that fully use 10 G= B > memory on a systems with just 1 GB RAM + 1 GB swap. You should have > enough resources to do that. You completely mischaracterize the situation I want to reserve 16GB or 24GB for the VM and the other 8 are for the host (and the host alone).. I have already used the -S flag since it is required by passthru Also the memory is successfully reserved accoring to top(1) but yet it still runs out (i.e. it shows 19GB are wired). -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAGBxaXkY70PSC1qb1VsJUq_3UG0K5M2HruBoC40c66wun%2BcseA>