3 ms·

I'm interested in knowing how GitHost are hosting GitLab CI. I'm currently using GLCI to run integration tests in Vagrant VMs, which unfortunately means most "c

by p8952 12y ago

I'm interested in knowing how GitHost are hosting GitLab CI. I'm currently using GLCI to run integration tests in Vagrant VMs, which unfortunately means most "cloud" hosting is out. joshfng (Assuming you are from GitHost). Do you know if your environment would support this?

joshfng 12y ago
All of our CI instances (coordinators and runners) are based on Ubuntu 12.04 x64 images. You are free to install any sort of software needed to run your builds on the runners.
- p8952 12y ago
  Hey joshfng. Thanks for the info, but it's more the BIOS settings I'm interested in. For example DigitalOcean's Ubuntu 12.04 x64 images work fine with Vagrant/VirtualBox, and their CPUs support VT-x. However since they do not enable VT-x in their BIOS you can only run x86 guests. If you could let me know the output of these commands in your images before I drop $10 to try it out it would be much appreciated: $ cat /proc/cpuinfo| grep 'vmx' # Checks for VT-x support on the CPU. $ rdmsr 0x3a # Checks if VT-x is enabled in the BIOS.
  - joshfng 12y ago
    VT-x is not enabled in the bios of our cloud images. Is there a specific need to run the build inside of a nested vm, as opposed to running directly in the runner itself? Feel free to email me jfrye [at] githost.io to discuss further.
  - joshfng 12y ago
    Also, forgot to mention you can try GitHost for free. There is no upfront billing.
    - p8952 12y ago
      Oh awesome, I didn't see that anywhere. I appreciate that mine is a strange edge case so thanks for all your help.