Reducing the time for buildworld

Antonio Huete Jimenez ahuete.devel at
Sun Mar 6 13:14:50 PST 2011

Hi Shivanth,

What are the hardware specs for the host VirtualBox is running on?
Does your processor have virtualization capabilities? If not that's
the first reason the build is taking so much time.

I've successfully done a buildworld in a VM with 256MB RAM running
i386 UP in approximately 2 hours. The processor is a Core2Duo T5500.
The virtualization solution is VMWare Workstation 7.

All the files for the buildworld/buildkernel can normally be found
under /usr/obj.

By the way, have you checked build(7) manpage?

Antonio Huete

2011/3/6 shivanth <fordearlinux at>:
> On 3/6/2011 4:05 PM, Alex Hornung wrote:
>> Hi Shivanth,
>> your email provides little to no information so right now, nobody can help
>> you.
>> What system do you have? What DragonFly version are you running? Is it
>> SMP or UP?
>> What's the "crash" (I assume panic?) about? Can you get a core dump or
>> at least a backtrace? You could do so by typing "trace" at the db>
>> prompt. For the former, you'd type "call dumpsys".
>> Regards,
>> Alex Hornung
>> On 6 March 2011 07:05, shivanth<fordearlinux at>  wrote:
>>> --
>>> My system has been running 'make -j3 Buildword ' for an eternity now .
>>> Worst -the make buildword causes the kernel to crash after 3-4 hours .
>>> And it seems the make command does not continue from where it stopped
>>> the last time instead it rebuilds the entire tree . Am i doing something
>>> wrong .Is there a config file for buildwprld where i can change this
>>> Thank you
>>> Shivanth
> Well i got it right now . I's running it on a VBox(UP) and it had too little
> memory i guess . And sorry for using the term crash there , the make process
> was actually stopped because it ran out of memory and swap . There's a shell
> after i pressed the Ctrl-c . So the problem was not with the kernel . Then i
> increased the memory  to 512M and the process was completed in 9 hours .

More information about the Kernel mailing list