Re: VirtualBox: Eating up 100% CPU, freezing Windows 7

From: Kevin Oberman <kob6558_at_gmail.com>
Date: Sat, 4 Aug 2012 17:56:32 -0700
On Sat, Aug 4, 2012 at 2:30 PM, Doug Barton <dougb_at_freebsd.org> wrote:
> On 08/04/2012 14:26, Garrett Cooper wrote:
>> On Sat, Aug 4, 2012 at 1:26 PM, Doug Barton <dougb_at_freebsd.org> wrote:
>>
>>> On 08/04/2012 00:40, O. Hartmann wrote:
>>>> No, also in my case. I build world and the VBox software with each
>>>> kernel - usually.
>>>
>>> You can ensure that by putting this in src.conf:
>>>
>>> PORTS_MODULES=  emulators/virtualbox-ose-kmod
>>>
>>> You can place other modules in that list as well. I use vbox so you can
>>> be pretty confident that this is going to keep working. :)
>>
>>     That doesn't work
>
> I assure you that it does. I have put a non-zero amount of work into
> fixing it, I use this method, and the resulting kernel module works just
> fine.
>
> If you actually try it and find something is not as it should be, then
> yes; please do file a PR and feel free to cc me.
>
> Doug

I am only aware of this because of your posts. No reference to it at
all in src.conf(5). It would be nice to see it there.

It is mentioned in build(7), but only as a MAKE option and a lot of
people are not going to realize it can be placed in src.conf. Also,
for those not fairly conversant in make, it is not clear whether
multiple ports should be space, comma, colon, or otherwise delimited

This is a very nice option as it is very easy to overlook rebuilding
kernel modules in ports when building the kernel. Thanks or working on
it.
-- 
R. Kevin Oberman, Network Engineer
E-mail: kob6558_at_gmail.com
Received on Sat Aug 04 2012 - 22:56:34 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:29 UTC