Edited by mattrix at Tue Nov 25, 2014 14:23 |
dlanor replied at Tue Nov 25, 2014 00:47
@ChrisP & mattrix, re: multicore use of VMware VS VirtualBox
We're talking about different things h ...
We need the complete source in a GIT repo.
The benefits of having it in a repo is huge and shouldn't need explaining.
Transferring 3GB files around the internet is not good for anyone.
Hosting just the changes as well is not ideal.
The repo will simply be a stock standard STABLE base for android images.
From this base, Stable android images can be built.
As for the VM, I can easily simulate more cores than my host PC has in VirtualBox.
With Vagrant it as simple as setting
This is just telling virtualbox how many cores and memory to simulate. Copy the Code
- config.vm.provider "virtualbox" do |v|
- v.memory = 1024
- v.cpus = 6
See here: https://www.virtualbox.org/manual/ch03.html
Section 3.4.2. "rocessor" tab
"On the "rocessor" tab, you can set how many virtual CPU cores the guest operating systems should see. Starting with version 3.0, VirtualBox supports symmetrical multiprocessing (SMP) and can present up to 32 virtual CPU cores to each virtual machine."
It goes on to say
"You should not, however, configure virtual machines to use more CPU cores than you have available physically (real cores, no hyperthreads)."
Which should be true to whatever VM you use.
If you look in the build script for the Kernel, it's actually using -J* anyway