New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Hard to understand failure when running in a VM without nested virtualization #4080
Comments
I do not believe it was easy to detect this from a regular user. Please, prove me wrong. |
Not planning to dig a lot here, as running crc in VMs is not something we support. However, this particular bug would be similar to running crc on physical hardware without virtualization support (ie lack of the |
Right, but this needs (needed?) Administrator privileges. That is not something we want to be asked for during a pre-flight. Note: this might have changed, and would like this to be investigated. Though that was the reason this was not done before. |
looked at this a bit today, seems there's no way to find detailed processor capabilities like on linux. and the generic cpu info provided by using powershell cmdlet |
This does not have to be a processor flag check, this could also be available at a higher level, for example hyper-v saying if hardware virtualization is supported or not. |
General information
crc setup
before starting it ? yesCRC version
I installed crc with the MSI installer, then ran
crc setup
, andcrc start
fails withFailed to start the virtual machine 'crc' because one of the Hyper-V components is not running.
I'm running this Windows in a VM on a linux host (libvirt/qemu/rhel9), and after investigating, I realized I forgot to enable nested virt for this VM. While nested virtualization is unsupported, I'd still expect that some preflight check would catch that this host is not virtualization-capable, and that hyper-v is not fully running.
The text was updated successfully, but these errors were encountered: