VirtualBox: The value of the Base Memory field on the System page is not complete

[Cy Schubert]

In message <CAGK=9AGuTQC+Cdxjym5JSkYEJ19KpetxJgJ=4pHmYyb5ggf6Eg at mail.gmail.c
om>
, Mikhail Tsatsenko writes:
> 2013/6/25 kron <kron24 at gmail.com>:
> > On 2013/06/25 09:16, Mikhail Tsatsenko wrote:
> >> 2013/6/25 kron <kron24 at gmail.com>:
> >>> Greetings,
> >>>
> >>> I'm running virtualbox-ose-4.2.14 on FreeBSD 9.1-STABLE r252094M
> >>> amd64. The GUI of VirtualBox cannot create/update virtual box
> >>> definitions (the *.vbox) files. The scrollbar and the form field
> >>> for "Base Memory" are broken and the following error message
> >>> is displayed:
> >>>
> >>> "The value of the Base Memory field on the System page is not
> >>> complete."
> >>>
> >>> I guess it comes from the base memory upper bound preset to zero
> >>> but I have no clue what's the source for the zero value.
> >>>
> >>> The problem is just in the GUI:
> >>> - I can create or update VMs using the CLI
> >>> - the VMs created in older VirtualBox versions run fine
> >>>
> >>> I anyone facing the same problem?
> >> I confirm the problem. Apparently this is a regression in the latest versi
> on.
> >>
> >> Currently I'm looking at full diff between  VirtualBox 4.2.12 and
> >> 4.2.14, but still can't  find a change which could cause the issue.
> >
> > At a first glance, RTSystemQueryAvailableRam? I see some
> > new occurrences in the diff. Unfortunately, it's one of
> > the OS dependent functions. However, I don't speak C++,
> > so I'm just guessing...
> Thanks for suggestion.
> Perhaps you are right, furthermore I can not see FreeBSD version of
> that function, so currently we have at least two different approaches:
> - Rollback to an old version of system memory calculation method
> (which was a dirty hack,according to code comments)
> - Or just implement such function and send it upstream.
> The second way seems to me more preferable. It takes me a few days,
> until that you have to use cli tools or previous VirtualBox port
> revision from svn.

Here's a partial patch. The patch relies on devel/sysinfo. All you need to 
do is find a way to link libsysinfo.so and libkvm.so in. I simply hacked it 
for now just to prove it can be done. A native solution would be better 
though.

--- src/VBox/Runtime/Makefile.kmk.orig	2013-06-21 05:27:18.000000000 -0700
+++ src/VBox/Runtime/Makefile.kmk	2013-06-25 13:52:25.971618756 -0700
@@ -73,7 +73,7 @@
  include $(PATH_SUB_CURRENT)/tools/Makefile.kmk
 
  BLDPROGS += uniread
- LIBRARIES += RuntimeR3 RuntimeBldProg RuntimeR0 RuntimeEFCPP 
RuntimeR3NoCRTGCC
+ LIBRARIES += RuntimeR3 RuntimeBldProg RuntimeR0 RuntimeEFCPP 
RuntimeR3NoCRTGCC -lsysinfo -lkvm
  LIBRARIES.solaris += RuntimeR0Stub
  LIBRARIES.win += RuntimeR0Stub
  ifdef VBOX_WITH_RAW_MODE
@@ -837,6 +837,7 @@
 	generic/RTProcDaemonize-generic.cpp \
 	generic/RTProcIsRunningByName-generic.cpp \
 	generic/RTThreadGetNativeState-generic.cpp \
+	r3/linux/systemmem-linux.cpp \
 	r3/freebsd/mp-freebsd.cpp \
 	r3/freebsd/rtProcInitExePath-freebsd.cpp \
 	r3/posix/RTFileQueryFsSizes-posix.cpp \
@@ -844,7 +845,6 @@
 	r3/posix/RTMemProtect-posix.cpp \
 	r3/posix/RTPathUserHome-posix.cpp \
 	r3/posix/RTSystemQueryOSInfo-posix.cpp \
-	r3/posix/RTSystemQueryTotalRam-posix.cpp \
 	r3/posix/RTTimeNow-posix.cpp \
 	r3/posix/RTTimeSet-posix.cpp \
 	r3/posix/dir-posix.cpp \



-- 
Cheers,
Cy Schubert <Cy.Schubert at komquats.com>
FreeBSD UNIX:  <cy at FreeBSD.org>   Web:  http://www.FreeBSD.org