New issue
Advanced search Search tips

Issue 863818 link

Starred by 7 users

Issue metadata

Status: Fixed
Owner:
Closed: Sep 10
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug


Show other hotlists

Hotlists containing this issue:
Hotlist-1


Sign in to add a comment

sudo reboot - VM does not come online anymore

Project Member Reported by yeri@google.com, Jul 16

Issue description

Chrome version: 
Google Chrome	69.0.3473.0 (Official Build) dev (64-bit)
Revision	cd23eb9e98a965ea157e23052bb62553e5d520d5-refs/branch-heads/3473@{#1}
Platform	10820.0.0 (Official Build) dev-channel eve
OS: Chrome

Repro steps:
1. sudo reboot
2. terminal does not come back online
3. Need to reboot CrOS to make it work

Expected: have Linux come back online after a couple of minutes
Actual: opening terminal goes into endless loop

 
Summary: sudo reboot - VM does not come online anymore (was: sudo reboot)
Components: OS>Systems>Containers
Owner: dgreid@chromium.org
Status: Assigned (was: Untriaged)
We're adding an option to the Terminal's right-click menu that will let you shut down the container/vm, and clicking it will start it up again.
What is the command to manually reboot the container/vm? "vmc stop termina" followed by "vmc start termina" from crosh does not bring it back. This seems related to 864274 and 864263.
More information: If I try to restart the vm with vmc stop termina then vmc start termina it appears the container does not run.

crosh> vmc stop termina
crosh> vmc start termina
(termina) chronos@localhost ~ $ lxc exec penguin bash
Error: Container is not running.
(termina) chronos@localhost ~ $ lxc start penguin
Error: Missing source '/run/tokens/penguin_token' for disk 'container_token'
Try `lxc info --show-log penguin` for more info
(termina) chronos@localhost ~ $ lxc info --show-log penguin
Name: penguin
Remote: unix://
Architecture: x86_64
Created: 2018/07/16 14:18 UTC
Status: Stopped
Type: persistent
Profiles: default

Log:

lxc penguin 20180718141445.742 WARN     lxc_conf - conf.c:lxc_map_ids:2857 - newuidmap is lacking necessary privileges
lxc penguin 20180718141445.742 WARN     lxc_conf - conf.c:lxc_map_ids:2863 - newgidmap is lacking necessary privileges
lxc penguin 20180718141445.922 WARN     lxc_conf - conf.c:lxc_map_ids:2857 - newuidmap is lacking necessary privileges
lxc penguin 20180718141445.922 WARN     lxc_conf - conf.c:lxc_map_ids:2863 - newgidmap is lacking necessary privileges

(termina) chronos@localhost ~ $ 

To restart the default VM, does the following work?

1) crosh> vmc stop termina
2) click on the terminal icon or any other linux app icon in the launcher.

Starting the container from the UI makes sure all the right configurations are passed in to let the container know how to talk to Chrome.
No, that does not work. The termina icon spins on the taskbar forever.
Status: Fixed (was: Assigned)
this seems to work on more recent builds. vmc stop followed by clicking on the icon gives me a fresh terminal on nami M70

Sign in to add a comment