running Ubuntu on bare metal but that obviously makes it harder to move VMs around.Then the only change we made to that box was an in-place upgrade to Win10 and, lo and behold, the builds are now also taking 3.5 hours each.Ī little research shows that there are a few people having issues with VirtualBox/Win10 as both host and guest but the advice given (video memory increase, re-balancing of CPUs/memory between host and guest, enabling/disabling video acceleration, etc) doesn't seem to fix anything. The Win7 box running the VM did each build in about 1.5 hours.
Even moving the VM disk across to an SSD on my box gave little relief, meaning it's almost certainly CPU bound. The machine was also very similarly specced out (same CPU, disks, etc).Īs an aside, I was originally running VirtualBox 5.x while the Win7 box had 6.0.12 but I don't think that's the issue since an upgrade to 6.0.14 on my box made no change. The VM was totally unchanged in terms of its setup, what type of disks it ran on, and so on. A VM running on my Win10 box (the guest is Ubuntu 16.04) was copied over to a Win7 box. We think we've finally established where the issue lies. We have a build system which, until a few weeks ago, was taking about 1.5 hours for a full build of each target device.Īt some point, that's been bumped up to about 3.5 hours which, because we build for about nine different targets, has increased our build time from fourteen hours to about thirty-two.
0 kommentar(er)
