Date: Fri, 9 Aug 2019 11:09:24 -0700 From: Kevin Oberman <rkoberman@gmail.com> To: FreeBSD Stable ML <stable@freebsd.org> Subject: Memory management changes after kernel update on 6-Aug Message-ID: <CAN6yY1uLDBJc_We4N1BHi3s9f5R0pCTvVsKV_E8oj0YnWo6pQQ@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
Since I updated my 12.0-STABLE system on 6-Aug I have been seeing issues resuming my Win7 VM on VirtualBox. My prior kernel was built on 24-Jul. If there is not sufficient memory available to reload the system (4 Meg.), the resume fails with a message that memory was exhausted. Usually I can try resuming again and it will work. Sometimes I get the error two or three times before the system resumes. Since I have not touched VirtualBox other than to rebuild the kmod after the kernel build, it looks like something in the OS triggered this. Since the system frees up some memory each time so that the VM eventually resumes, it looks like the memory request is made to the OS, but VB is not waiting or not enough memory is freed to allow the VB to complete the resume. Any clue what might have changed over those 13 days? I am running GENERIC except that I run the 4BSD scheduler. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAN6yY1uLDBJc_We4N1BHi3s9f5R0pCTvVsKV_E8oj0YnWo6pQQ>