Skip to content
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] - cannot get crc to start on windows, system-tray app will not stay running for more than 3 seconds #2666

Closed
robstryker opened this issue Aug 23, 2021 · 3 comments · Fixed by #2680
Labels
kind/bug Something isn't working os/windows

Comments

@robstryker
Copy link

General information

  • OS: Windows 10 Home, 21H1
  • Hypervisor: I assume hyper-v? I wasn't asked to install a hypervisor. Installation unpacked a hyper-v. I know I had virtualbox installed on the machine at one point.
  • Did you run crc setup before starting it (Yes/No)? Yes
  • Running CRC on: Laptop / Baremetal-Server / VM Laptop

CRC version

CodeReady Containers version: 1.31.2+19538dab
OpenShift version: 4.8.4 (not embedded in executable)

CRC status

DEBU CodeReady Containers version: 1.31.2+19538dab
DEBU OpenShift version: 4.8.4 (not embedded in executable)
DEBU Running 'crc status'
DEBU Checking file: C:\Users\rob\.crc\machines\crc\.crc-exist
DEBU Running '(Get-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion" -Name ReleaseId).ReleaseId'
DEBU Running '(Get-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion").EditionID'
Machine does not exist. Use 'crc start' to create it

CRC config

- consent-telementry      : yes

Host Operating System

Host Name:                 DESKTOP-LET5SIJ
OS Name:                   Microsoft Windows 10 Home
OS Version:                10.0.19043 N/A Build 19043
OS Manufacturer:           Microsoft Corporation
OS Configuration:          Standalone Workstation
OS Build Type:             Multiprocessor Free
Registered Owner:          [sic]
Registered Organization:
Product ID:                00326-10861-73294-AA479
Original Install Date:     7/28/2020, 12:42:34 AM
System Boot Time:          8/23/2021, 1:44:38 PM
System Manufacturer:       Gigabyte Technology Co., Ltd.
System Model:              AB350M-Gaming 3
System Type:               x64-based PC
Processor(s):              1 Processor(s) Installed.
                           [01]: AMD64 Family 23 Model 8 Stepping 2 AuthenticAMD ~3600 Mhz
BIOS Version:              American Megatrends Inc. F22, 3/15/2018
Windows Directory:         C:\WINDOWS
System Directory:          C:\WINDOWS\system32
Boot Device:               \Device\HarddiskVolume2
System Locale:             en-us;English (United States)
Input Locale:              en-us;English (United States)
Time Zone:                 (UTC-05:00) Eastern Time (US & Canada)
Total Physical Memory:     32,719 MB
Available Physical Memory: 29,200 MB
Virtual Memory: Max Size:  37,583 MB
Virtual Memory: Available: 33,428 MB
Virtual Memory: In Use:    4,155 MB
Page File Location(s):     C:\pagefile.sys
Domain:                    WORKGROUP
Logon Server:              \\DESKTOP-LET5SIJ
Hotfix(s):                 12 Hotfix(s) Installed.
                           [01]: KB5004331
                           [02]: KB4561600
                           [03]: KB4566785
                           [04]: KB4570334
                           [05]: KB4577266
                           [06]: KB4580325
                           [07]: KB4586864
                           [08]: KB4593175
                           [09]: KB4598481
                           [10]: KB5000736
                           [11]: KB5005033
                           [12]: KB5005260
Network Card(s):           1 NIC(s) Installed.
                           [01]: Realtek PCIe GbE Family Controller
                                 Connection Name: Ethernet 2
                                 DHCP Enabled:    Yes
                                 DHCP Server:     192.168.1.1
                                 IP address(es)
                                 [01]: 192.168.1.194
                                 [02]: fe80::70b2:b750:a222:d58f
                                 [03]: 2605:a601:a610:5c00:891b:fbf3:bdab:5a87
                                 [04]: 2605:a601:a610:5c00:70b2:b750:a222:d58f
Hyper-V Requirements:      VM Monitor Mode Extensions: Yes
                           Virtualization Enabled In Firmware: Yes
                           Second Level Address Translation: Yes
                           Data Execution Prevention Available: Yes

Steps to reproduce

  1. run crc delete
  2. run crc cleanup
  3. run crc setup --check-only
  4. run crc setup --log-level debug
  5. run crc start --log-level debug
  6. crc fails to start, indicating the tray application is not running.
  7. Try to run the tray application

Expected

I expect the tray application (and then later, the crc) to start.

Actual

The CRC does not start. The important part of the log below is that the system-tray app is not running. When running the system-tray command, the openshift logo appears in the tray for 3 seconds before disappearing. No indication anywhere as to why it was terminated.

Logs

Before gather the logs try following if that fix your issue

$ crc delete -f
$ crc cleanup
$ crc setup
$ crc start --log-level debug

https://gist.github.com/robstryker/4f817cb778d7b20f81f26d9c5477d50f

@robstryker robstryker added kind/bug Something isn't working status/need triage labels Aug 23, 2021
@robstryker robstryker changed the title [BUG] [BUG] - cannot get crc to start on windows, system-tray app will not stay running for more than 3 seconds Aug 23, 2021
@praveenkumar
Copy link
Member

@robstryker OS: Windows 10 Home, 21H1 https://crc.dev/crc/#_microsoft_windows we don't support windows home and in the tray there is check which prevent it to run on windows home addition.

@jeffmaury
Copy link

The remaining question is why this invalid configuration hasn't been detected earlier (by crc setup --check-only for example) ?

@anjannath
Copy link
Member

We have a bug in our windows edition detection, we are using the EditionID to detect if the version of windows is Home, but in fact the name of the edition is "Core"
image

The tray failing to start will be because of other checks in the chain, Like hyper-v not available, since on windows home it is not available by default

anjannath added a commit to anjannath/crc that referenced this issue Aug 30, 2021
The name of the edition for windows 10 Home edition is "Core"
and not "Home"

```
PS > (Get-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion").EditionID
Core
```
anjannath added a commit to anjannath/crc that referenced this issue Aug 30, 2021
The name of the edition for windows 10 Home edition is "Core"
and not "Home"

```
PS > (Get-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion").EditionID
Core
```
anjannath added a commit that referenced this issue Aug 30, 2021
The name of the edition for windows 10 Home edition is "Core"
and not "Home"

```
PS > (Get-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion").EditionID
Core
```
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working os/windows
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants