vmc: command not found
Marshall126 opened this issue · 10 comments
I'm in dev channel version 67 and crostini is enabled in chrome://flags
The command is seen by the OS, but not allowed, which according this page means the Crostini feature isn't enabled. Any way to enable it other than the flag?
use the vmc command from the crosh> prompt, not after typing shell
Been doing that.
ERROR: command 'vmc' is not available.
This is different from the usual "Command not found," meaning that I simply do not have permissions to access the command. Currently on latest dev build, 67.0.3383.0
I'm experiencing the same thing. Dev channel:
Version 67.0.3383.0 (Official Build) dev (64-bit) HP Chromebook 14 G4
I've enabled both flags for Container Support and Crostini support, but that didn't change anything.
Is this restricted to certain devices?
AFAIK this is pixelbook only
I'm 99% sure this will currently only work on pixelbooks.
Any word on when this will be opened up to the rest of the Intel Chromebooks that support hardware virtualization?
Not working on Samsung Chromebook 3 either (dev mode + dev channel + --enable-features=Crostini,CrOSContainer,ExperimentalCrostiniUI). No vsh from shell (and missing /dev/kvm), or vmc in crosh, though shell (as root) allows run_oci. Based on the ChromeOS commits referenced above, and from this Reddit thread, looks like it's coming soon, but currently restricted to PixelBooks for dogfooding. Rumor has it the wider roll out will be tied to Google IO announcement in early May.
Toshiba CB 2, likewise give message command not available, which is unique compared the the usual "unknown command" response.
Good news is it looks like there has been active development this year to enable crosvm on non-Pixelbooks, including lower end x64 Intel CPUs (like the 4-core Celeron N3150 Braswell, used on some Asus, Acer, and Lenovo Chromebooks): https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/936323