listnr link: https://listnr.corp.google.com/product/208/report/85632264229

From the system-logs:
[990:990:0831/145313.217385:ERROR:object_proxy.cc(615)] Failed to call method: org.chromium.debugd.StartVmConcierge: object_path= /org/chromium/debugd: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
[990:990:0831/145313.217562:ERROR:crostini_manager.cc(638)] Failed to start Concierge service

Can we see if this is reproducible ASAP and the extent of the bisect (already present in M70 or if this is new per the latest revs)? Need to unblock the blocking status.   Note that M70 branched so any changes will need to include a merge request.  Thanks! 

This is a Braswell device, so this might be fixed by a recent timeout change. +smbarber/chirantan to confirm.

This device needs a cold reset (refresh + power) to enable VM extensions.

libminijail[1]: stat(/dev/kvm) failed: No such file or directory

I am seeing this issue on another device as well.

How do we notify users in case there are more cases in the field?

On other Intel devices we've taken advantage of firmware updates, which trigger a cold reset. Those firmware updates were required to enable virtualization extensions, but they aren't needed on ARM or on Braswell/Apollo Lake.

I'm not sure how we could trigger a cold reset without a firmware update, unless we do something hacky with the EC.