Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 25 Jun 2013 20:23:08 +0400
From:      Mikhail Tsatsenko <m.tsatsenko@gmail.com>
To:        kron <kron24@gmail.com>
Cc:        freebsd-virtualization@freebsd.org
Subject:   Re: VirtualBox: The value of the Base Memory field on the System page is not complete
Message-ID:  <CAGK=9AGuTQC%2BCdxjym5JSkYEJ19KpetxJgJ=4pHmYyb5ggf6Eg@mail.gmail.com>
In-Reply-To: <51C96E75.2020103@gmail.com>
References:  <51C93F52.4050209@gmail.com> <CAGK=9AGujKfkzaQi1arm9xWzVvfxgzXiwFWUED1ufskGeqgYrg@mail.gmail.com> <51C96E75.2020103@gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
2013/6/25 kron <kron24@gmail.com>:
> On 2013/06/25 09:16, Mikhail Tsatsenko wrote:
>> 2013/6/25 kron <kron24@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 ver=
sion.
>>
>> 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.

>
> Oli
> _______________________________________________
> freebsd-virtualization@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
> To unsubscribe, send any mail to "freebsd-virtualization-unsubscribe@free=
bsd.org"



--
=ED=C9=C8=C1=C9=CC



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAGK=9AGuTQC%2BCdxjym5JSkYEJ19KpetxJgJ=4pHmYyb5ggf6Eg>