New issue
Advanced search Search tips

Issue 918979 link

Starred by 2 users

Issue metadata

Status: Unconfirmed
Owner: ----
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Crostini failing to start on Chromium OS with AMD A6-3420M APU

Reported by lukeblev...@gmail.com, Jan 3

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36
Platform: 70.4.39 (Developer Build - neverware) developer-build chromeover64

Steps to reproduce the problem:
1. Navigate to chrome://settings on an AMD device
2. Enable Linux (crostini)
3. Observe the setup process fail with "unable to start VM"

What is the expected behavior?
The setup process should complete successfully and add a Terminal icon in the app drawer that launches a Linux terminal when executed.

What went wrong?
The setup process fails with something along the lines of "unable to mount Linux files" or "unable to start VM", despite multiple tries and reboots. Furthermore, the app icon displays a spinning circle above the Terminal icon placed on the taskbar when executed. This CPU has AMD's virtualization technology supported. Hence, the "svm" cpuinfo flag.

Did this work before? No 

Chrome version: 70.0.3538.124  Channel: stable
OS Version: 70.4.39
Flash Version: 20181205.1.999.999

Although there are not currently any Chromebooks with AMD processors, these new Chromium OS developments should be ported to AMD-based hosts as well as Intel.
 
Requesting for someone to classify this bug as affecting the OS>Systems>Containers component
For clarification purposes, the CPU that is failing to run Crostini for me is the AMD A6-3420M APU.
Components: OS>Systems>Containers
Labels: -Pri-2 Pri-3
Summary: Crostini failing to start on Chromium OS with AMD A6-3420M APU (was: Properly support AMD hosts using Crostini in Chromium OS)
we already have crostini running on grunt which is AMD based, so we know it works

if you're running Chromium OS on an unofficial device, you'll prob need to debug it yourself

Sign in to add a comment