{"id":49070,"date":"2025-04-10T12:17:02","date_gmt":"2025-04-10T12:17:02","guid":{"rendered":"https:\/\/www.devopsschool.com\/blog\/?p=49070"},"modified":"2025-07-12T05:56:24","modified_gmt":"2025-07-12T05:56:24","slug":"openshift-local-crc-troubleshooting-guide","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/openshift-local-crc-troubleshooting-guide\/","title":{"rendered":"Openshift Local: crc troubleshooting guide"},"content":{"rendered":"\n

If crc<\/code> is not creating a VM even after setup, and you’re using Windows 11 with Hyper-V, here’s how you can check the logs<\/strong> and troubleshoot the issue<\/strong>:<\/p>\n\n\n\n

\n\n\n\n

\u2705 1. View Detailed Logs from CRC<\/strong><\/h3>\n\n\n\n

Run this command to get verbose debug logs:<\/p>\n\n\n

crc start -l debug\n<\/code><\/span><\/pre>\n\n\n
or for even more detailed logging:<\/p>\n\n\n
crc start --log-level debug\n<\/code><\/span><\/pre>\n\n\n
This will print detailed steps of what crc<\/code> is doing, where it’s failing, and may show VM or Hyper-V issues.<\/p>\n\n\n\n
\n\n\n\n
\u2705 2. Check Log Files Manually<\/strong><\/h3>\n\n\n\n
CRC stores logs in this location on Windows:<\/p>\n\n\n
C:\\Users\\<your-username<\/span>><\/span>\\.crc\\logs\n<\/code><\/span>Code language:<\/span> HTML, XML<\/span> (<\/span>xml<\/span>)<\/span><\/small><\/pre>\n\n\n
Check the latest folder in that directory for a file like:<\/p>\n\n\n
crc<\/span>.log<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
You can open it in Notepad or any text editor to see detailed setup\/start information.<\/p>\n\n\n\n
\n\n\n\n
\u2705 3. Confirm Prerequisites<\/strong><\/h3>\n\n\n\n
Let\u2019s double-check a few required things:<\/p>\n\n\n\n
Item<\/th>Check<\/th><\/tr><\/thead>
\u2705 Hyper-V installed<\/strong><\/td>Run Get-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-All<\/code> in PowerShell<\/td><\/tr>
\u2705 User is in Hyper-V Administrators Group<\/strong><\/td>Run net localgroup \"Hyper-V Administrators\"<\/code><\/td><\/tr>
\u2705 Virtualization Enabled in BIOS<\/strong><\/td>Check from Task Manager \u2192 Performance \u2192 CPU<\/td><\/tr>
\u2705 Installed CRC with Installer<\/strong><\/td>Make sure you used the .msi<\/code> installer, not just a ZIP<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
If any of these aren’t properly configured, CRC won’t be able to start the VM.<\/p>\n\n\n\n
\n\n\n\n
\u2705 4. Manually Check Hyper-V VM<\/strong><\/h3>\n\n\n\n
Check if a CRC VM was created but failed to start:<\/p>\n\n\n
Get-VM\n<\/code><\/span><\/pre>\n\n\n
You may see something like crc<\/code> listed. If it’s there but “Off” or in a failed state, try:<\/p>\n\n\n
Start-VM -Name crc\n<\/code><\/span><\/pre>\n\n\n
And if that fails, get the error:<\/p>\n\n\n
Get-VM -Name crc | Get-VMIntegrationService\n<\/code><\/span><\/pre>\n\n\n
\n\n\n\n
\u2705 5. Clean Up and Retry (if needed)<\/strong><\/h3>\n\n\n\n
If everything fails, you can try resetting and starting fresh:<\/p>\n\n\n
crc cleanup\ncrc setup\ncrc start --log-level debug\n<\/code><\/span><\/pre>\n\n\n
\n\n\n\n
Here is a Complete OpenShift Local (CRC) Troubleshooting Guide<\/strong> tailored for Windows (especially Windows 11), covering installation, VM, daemon, logs, and networking issues \u2014 all in one place:<\/p>\n\n\n\n
\n\n\n\n
\u2705 Complete OpenShift Local (CRC) Troubleshooting Guide for Windows<\/strong><\/h1>\n\n\n\n
\n\n\n\n
\ud83e\uddf0 1. Basic CRC Setup Checklist (Before Troubleshooting)<\/strong><\/h2>\n\n\n\n
Requirement<\/th>Notes<\/th><\/tr><\/thead>
OS<\/strong><\/td>Windows 10\/11 Pro, Enterprise, or Education (Hyper-V required)<\/td><\/tr>
RAM<\/strong><\/td>Minimum 9 GB free (16 GB total preferred)<\/td><\/tr>
Disk Space<\/strong><\/td>At least 35 GB free<\/td><\/tr>
Virtualization<\/strong><\/td>Must be enabled<\/strong> in BIOS<\/td><\/tr>
Hyper-V Installed<\/strong><\/td>Required \u2013 CRC won’t work with VirtualBox<\/td><\/tr>
Admin Rights<\/strong><\/td>Must run CRC setup and start as Administrator<\/td><\/tr>
CRC Installed via MSI<\/strong><\/td>Always use the official Windows .msi<\/code> installer<\/td><\/tr>
Reboot Performed<\/strong><\/td>After install \u2013 mandatory<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
\n\n\n\n
\ud83d\udee0\ufe0f 2. Installation & Setup<\/strong><\/h2>\n\n\n\n
\u2705 Correct Installation Steps:<\/h3>\n\n\n
crc cleanup\ncrc setup\n<\/code><\/span><\/pre>\n\n\n
\n
Always reboot after installation.<\/p>\n<\/blockquote>\n\n\n\n
\n\n\n\n
\ud83e\uddea 3. Common Issues and Fixes<\/strong><\/h2>\n\n\n\n
\u274c Issue 1: CRC Daemon Not Running<\/strong><\/h3>\n\n\n\n
Error:<\/strong><\/p>\n\n\n
Is 'crc daemon'<\/span> running? Cannot reach daemon API\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
Fix:<\/strong><\/p>\n\n\n
# Open PowerShell as Admin<\/span>\ncrc daemon\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
\n
Keep this terminal open while you run crc start<\/code> in another one.<\/p>\n<\/blockquote>\n\n\n\n
\n\n\n\n
\u274c Issue 2: No VM is created<\/strong><\/h3>\n\n\n\n
Fix:<\/strong><\/p>\n\n\n\n