Error starting penguin container: 5 Launching vmshell failed: Error starting crostini for terminal: 5

Comments

10 comments

  • Michael Clarke

    Emanuel.

     

    There is already quite a long forum thread on the Crostini Error 5 topic, here: 

    https://neverware.zendesk.com/hc/en-us/community/posts/4405874706579 

    Increased security checks in ChromiumOS v91 and onward mean that if your CPU is susceptible to the Spectre and Meltdown vulnerabilities, Crostini will not run.  Latest BIOS does not guarantee your CPU is running the required Microcode.

    If you are good with linux Kernel and Grub, you might be able to insert the microcode fixes into the underlying OS, but this clearly does not fall within the normal use cases for users on this forum.

    There may be official fixes and workarounds in the future, but for now the issue is likely to affect older hardware that no longer has support from the manufacturer.  If you are reliant on Linux-based applications, you may find you need to revert to a full Linux installation until such time a universal solution is found (or you obtain hardware with the Spectre and Meltdown vulnerabilities patched).

    Neverware put a statement regarding the Crostini situation here:

    https://cloudreadykb.neverware.com/s/article/Linux-Beta-support

    1
    Comment actions Permalink
  • Emanuel.

    Is the Ryzen 5 3600 also vulnerable? I ran a quick test on Windows since CR without linux apps is not working for me and this was the result. The only thing I need is thunderbird to be able to work on my machine but it looks like it won't work with CR.

     

    0
    Comment actions Permalink
  • Michael Clarke

    Checking your CPU under Windows will not guarantee that the CPU is not vulnerable under CloudReady, since Windows may contain some microcode mitigation that the underlying Linux OS behind ChromiumOS does not.

    Run the checks under Cloud Ready as follows:

    How do I check if my device has any unmitigated CPU vulnerabilities? 

    The following steps can only be done on CloudReady Home Edition.
    To check whether you have unmitigated vulnerabilities preventing virtualization:

    1. Log in on a CloudReady Home Edition device
    2. Enter crosh by pressing Ctrl + Alt + t
    3. Enter shell by typing shell and pressing enter
    4. Type  cat /sys/devices/system/cpu/vulnerabilities/l1tf and press enter
    5. If the output doesn’t contain: VMX: cache flushes or VMX: flush not necessary  the device has unmitigated CPU vulnerabilities. Examples of bad results:  
      1. Mitigation: PTE Inversion; VMX: conditional cache flushes, SMT disabled
      • Mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable

     

    1
    Comment actions Permalink
  • Emanuel.

     

    If I understand correctly my cpu is not vulnerable, I think. Thank you very much for your help.I am testing with the live version of CR.

     

    0
    Comment actions Permalink
  • Emanuel.

    Also a while ago I already sent the bug report to CloudReady.

    0
    Comment actions Permalink
  • Emanuel.

    Any solution?? Thank you very much in advance.

    0
    Comment actions Permalink
  • Michael Clarke

    Hi Emanuel.

    In your original post you mentioned the Linux Container may not have installed correctly.  If this is the case, I think the only way to revert to stock CloudReady is to reinstall or powerwash the operating system.  I certainly haven't yet found a way to remove a broken Linux environment.

    There is another well documented bug with some ChromiumOS installations where the Linux container does not install correctly, for which a workaround was to set the Crostini-Use-DLC flag to disabled before attempting the installation of the Linux environment.

    chrome://flags/#crostini-use-dlc

    These are all just suggestions - I do not work for CloudReady, and am currently affected by the Linux issues as well, so hopefully there will be some development in the future, but for now you may need to make a decision regarding which OS suits your needs the best.  CloudReady with some unsupported elements, Full Linux, or Official Chromebook...

     

    0
    Comment actions Permalink
  • Emanuel.

    I say it was not installed correctly because the container does not start. Thank you very much for your help. Best regards.

    Forrest Smith Any solution?

    0
    Comment actions Permalink
  • Emanuel.

    Forrest Smith I was able to install with a ryzen 5 3600 and with a gtx 150 ti but I can't work with CR because of the lack of client like thunderbird. I already exposed my problem in a series of post, I also sent the bug report to CR. Could you help me to solve this? Thank you very much. Best regards. 

    0
    Comment actions Permalink
  • lojasal

    Restart your Chromebook two or three times in a row and check if the issue persists. Sometimes, simply restarting your device is enough to clear up strange glitches like this one.

    Additionally, you can also remove the battery and leave your device unplugged for one minute. Insert the battery, power up the device, and check if you can launch Linux. If you’re still getting the same error, go to the next step

    0
    Comment actions Permalink

Please sign in to leave a comment.