VirtualBox 4.2.14 unusable

[Bernhard Fröhlich]

On Mon, Jul 8, 2013 at 11:03 PM, Jimmy Kelley <ljboiler at gmail.com> wrote:
> On Mon, Jul 08, 2013 at 10:14:44PM +0400, Mikhail Tsatsenko wrote:
>> 2013/7/8 Jimmy Kelley <ljboiler at gmail.com>:
>> > On Mon, Jul 08, 2013 at 12:40:16PM -0300, Sergio de Almeida Lenzi wrote:
>> >> Yes it is broken,
>> >>
>> >> the logic that finds how much real memory is there in the FreeBSD
>> >> is broken, reports ZERO..
>> >>
>> >> There is a Problem Report and a person that
>> >> says will fix it, 2 weeks ago...
>> >>
>> >> I am using the last version 4.2.12 that works
>> >>
>> >> I am still waiting for the fix...
>> >>
>> >>
>> >> Sergio
>> >>
>> >
>> > I did a search on the Freebsd PRs (http://www.freebsd.org/cgi/query-pr-summary.cgi) and
>> > cannot find anything that seems to reference this problem.  Would you know the PR number?
>> > Or was this just some discussion on the mailing list?
>> >
>> > I'll file an offical PR if there isn't one.
>> >
>> > Jimmy
>> There is no PR for this problem.
>> As far as I understand memory calculation is still broken on CURRENT.
>> And I suspect it is a build-time  not runtime bug.
>> Can anybody who is facing the problem send me a full build log of the
>> virtualbox-ose port from affected machine for investigation please.
>>
>> _______________________________________________
>> > freebsd-ports at freebsd.org mailing list
>> > http://lists.freebsd.org/mailman/listinfo/freebsd-ports
>> > To unsubscribe, send any mail to "freebsd-ports-unsubscribe at freebsd.org"
>>
>>
>>
>> --
>> Mikhail
>
> Attached is my build log; I'm running 10-CURRENT i386.  I see the patch files commited for this
> problem with VBox 4.2.14 (PR #180086) on my machine, but I have upgraded my ports tree since
> and have the newer 4.2.16 version that I'm building.

Please try the patch from that mail and see if it helps. From the
reports it looks reasonable to say
that the currently committed patch works only on amd64. So far the
reports where it doesn't work
are all on i386 and this matches with the description of the fix in the mail.

http://lists.freebsd.org/pipermail/svn-ports-all/2013-July/024215.html

--
Bernhard Froehlich
http://www.bluelife.at/