You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 9, 2018. It is now read-only.
I'm opening this issue in order to document the solution to a common problem encountered by persons trying to set up their dev environment. I am sorry if this is not the right place for this... (maybe cozy-docs?)
If your VM does not start (timeout at cozy-dev vm:start) it may be because virtualization is not activated on your machine.
This is easy to spot, start virtualbox and look at the general settings of the machine.
Go to settings->General->Basic->Version
If only 32bits versions are available, then virtualization is not activated on your CPU. The cozy virtual image requires 64bit
Thanks for reporting @Klodd, we should add a warning into the doc.
Are you aware of any easy way to test if virtualization is activated ? Is there an error message we could display to the user?
I'm opening this issue in order to document the solution to a common problem encountered by persons trying to set up their dev environment. I am sorry if this is not the right place for this... (maybe cozy-docs?)
If your VM does not start (timeout at cozy-dev vm:start) it may be because virtualization is not activated on your machine.
This is easy to spot, start virtualbox and look at the general settings of the machine.
Go to settings->General->Basic->Version
If only 32bits versions are available, then virtualization is not activated on your CPU.
The cozy virtual image requires 64bit
To activate it, the first answer of this post is very clear:
http://askubuntu.com/questions/256792/how-do-i-enable-hardware-virtualization-technology-vt-x-for-use-in-virtualbox
The text was updated successfully, but these errors were encountered: