No activity detected on VM, aborting #2214

robrich · 2018-07-16T04:59:07Z

Diagnostics ID: 448D1A06-BF15-4908-834D-EB41D6F32ECC/2018-07-15_21-49-29 and 448D1A06-BF15-4908-834D-EB41D6F32ECC/2018-07-15_22-15-43 and a few more

Machine: Intel Core i9, Windows 10 Pro (1803), 64 gigs ram
Docker: 18.05.0-ce Edge

Start Docker for Windows as Admin, get "No activity detected on VM, aborting"

Tried reset to factory defaults

Tried #1221 (comment) (netcfg -d then reboot)

Tried #1221 (comment) (uninstall Docker, uninstall Hyper-V, delete everything, reinstall Hyper-V, reinstall Docker)

Still can't get Docker for Windows to start in Linux mode, Windows mode works just fine.

Unrelated? In Event Viewer:

Error occurred when creating network could not find plugin internal in v1 plugin registry: plugin not found
Unable to locate plugin: internal, retrying in 8s (and 4s and 2s and 1s)

Moved the drive from this machine where it was working:
Machine: Intel Core i7 - 3rd gen, Windows 10 Pro (1803), 32 gigs ram
Maybe Hyper-V doesn't understand new hardware?

The text was updated successfully, but these errors were encountered:

robrich · 2018-07-16T06:31:19Z

Same results when using dockercli -SwitchLinuxEngine

minikube starts up just fine.

robrich · 2018-07-20T23:31:05Z

Formatted machine, fresh Windows 10 Pro install from July updated MSDN disk, same behavior.

Diagnostics ID: DD4576AF-ACA8-4B38-B116-8C9384FE468E/20180720162602

Windows Version: Microsoft Windows [Version 10.0.17134.112]
Docker Version: Docker version 18.06.0-ce-rc3, build cbfa3d9

The last few lines of the log:

[16:16:52.319][Moby           ][Info   ] [    0.000000] tsc: Fast TSC calibration failed
[16:16:52.319][Moby           ][Info   ] [    0.000000] tsc: Unable to calibrate against PIT
[16:16:52.334][Moby           ][Info   ] [    0.000000] tsc: HPET/PMTIMER calibration failed
[16:17:22.394][NamedPipeServer][Error  ] Unable to execute Start: No activity detected on VM, aborting    at Docker.Backend.ContainerEngine.Linux.DoStart(Settings settings, String daemonOptions) in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Backend\ContainerEngine\Linux.cs:line 267
   at Docker.Backend.ContainerEngine.Linux.Start(Settings settings, String daemonOptions) in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Backend\ContainerEngine\Linux.cs:line 117
[16:17:22.410][NamedPipeClient][Error  ] Unable to send Start: No activity detected on VM, aborting
[16:17:22.410][Notifications  ][Error  ] No activity detected on VM, aborting

robrich · 2018-07-23T22:19:39Z

On the i7 machine, Docker starts correctly when I have KB4284835 installed, but fails to start correctly when Windows 10 auto-updates and installs KB4338819. On the i9 machine, Docker consistently fails to start whether KB4338819 is installed or not. Is i9 not compatible with D4W?

rheid · 2018-07-26T22:53:19Z

@robrich Do you any new about that issue. I have same problem.

robrich · 2018-07-28T18:39:38Z

@rheid: Nope, I'm pretty stuck. I'm going to give 18.06.0-win69 a try, and I know there were some bad Windows Updates this last go-round, so I'm going to give Windows Update a month. But pretty much I'm stuck.

QuintinRudman · 2018-07-30T16:21:38Z

Well my entire CI Pipeline is dead as a result of this.

QuintinRudman · 2018-07-30T16:30:36Z

If there is anything anyone can suggest that I perhaps did not try I'd really appreciate some help.

I have rebuilt Hyper-V, Containers, Docker, I have gone back several versions of Docker, Disabled Nexus and bamboo to free up about 8GB of RAM for the MobyLinuxVM, Removed/Deleted and Recreated NAT, VMSwitch, Netcfg -D, HNS.dat, daemon.json files under AppData, ProgramData, ../Docker/Resources/., Check Reg Entries, Windows Updates - Latest, Nested Virtualization, VT-x Support MMU HW enabled, Docker Daemon Service Elevated Access Rights,...not sure if I missed anything.

robrich · 2018-08-01T19:54:40Z

Diagnostics ID: 448D1A06-BF15-4908-834D-EB41D6F32ECC/20180801124844 Most recent updates, Docker 18.06.0-ce-win71, same result. On the up-side, I'm getting good at MiniKube.

ghost · 2018-08-13T15:42:02Z

Have we got an update on this issue as currently facing the exact same.

robrich · 2018-08-14T18:44:25Z

Docker version: Version 18.06.0-ce-win71 (19101)
Diagnostics ID: 448D1A06-BF15-4908-834D-EB41D6F32ECC/20180814114221
Same results.

carlead · 2018-08-17T13:34:24Z

On windows 10, if we uninstall windows docker, does it delete containers ?
We'd like to downgrade docker.

Thanks,

serialbandicoot · 2018-08-22T08:45:48Z

I'm seeing the same issue with 18.06.0-ce-win72 (19098)

Diagnostic Id: 3E0D1E60-A0A1-439A-881E-79E0A5DA0780/20180822102127

superzadeh · 2018-08-23T10:20:48Z

Also running into this daily. How can I help to get it fixed? Losing several hours every day because of this (factory reset, then rebuild all my images, then run into it again couple hours later).

Diganostic Id: BD2EB361-BE29-4A76-9BF5-8D17D0BAE512/20180823121210

talgat-ruby · 2018-08-23T17:20:48Z

@superzadeh Sometimes it works after several(for me today was 10 times) of restart Docker and quit-start Docker. I know it is not solution at all. But just to minimize time waste.

superzadeh · 2018-08-23T19:40:25Z

Yeah, I've noticed as well @talgat-ruby, trying multiple times to restart/quit and launch again seems more or less work, but it still takes a lot of time.

It also seems to be happening after my laptop becomes locked/sleep (using a Surface Pro and very often on the move, it goes to sleep quite often). Could anyone else confirm?
That would make me think that it's more related to some recent changes in Hyper-V/Windows, maybe related to battery optimizations that could change the way Hyper-V behaves when resuming from sleep, which could break Docker for some reason, but this is a very wild guess.

If there's anything I can do to help investigate, let me know.

robrich · 2018-08-24T18:18:29Z

on #2253 and #2404 they're suggesting to try this build. So far the consensus is it doesn't resolve it.

liujianm · 2018-08-28T02:03:09Z

I faced same issue #2489

syedhassaanahmed · 2018-10-24T00:28:43Z

Same issue on Stable 18.06.1-ce-win73 (19507)
Diagnostic ID: 9E546F03-92E7-4328-A05E-C51EAAD30B9A/20181024022318

marioanz · 2018-11-30T19:16:23Z

[ x ] I have tried with the latest version of my channel (Stable or Edge)
[ x ] I have uploaded Diagnostics
Diagnostics ID: 22ED990D-4E0D-4381-9AEB-F430CAE1AFD3/20181130103807

Expected behavior

Docker Start

Actual behavior

No activity detected on VM, aborting
at Docker.Core.Pipe.NamedPipeClient.Send(String action, Object[] parameters) in C:\workspaces\stable-18.09.x\src\github.com\docker\pinata\win\src\Docker.Core\pipe\NamedPipeClient.cs:line 36
at Docker.Actions.DoStart(SynchronizationContext syncCtx, Boolean showWelcomeWindow, Boolean executeAfterStartCleanup) in C:\workspaces\stable-18.09.x\src\github.com\docker\pinata\win\src\Docker.Windows\Actions.cs:line 92
at Docker.Actions.<>c__DisplayClass19_0.b__0() in C:\workspaces\stable-18.09.x\src\github.com\docker\pinata\win\src\Docker.Windows\Actions.cs:line 74
at Docker.WPF.TaskQueue.<>c__DisplayClass19_0.<.ctor>b__1() in C:\workspaces\stable-18.09.x\src\github.com\docker\pinata\win\src\Docker.WPF\TaskQueue.cs:line 59

Information

Windows Version:
Edition: Windows 10 Pro
Version: 1809
Installed on 11/29/2018
OS build: 17763.134
Docker for Windows Version: 18.09.0

Steps to reproduce the behavior

Build Windows 10 VM. Install Updates.
Enable nested virtualization
Turn on Features: Containers, Hyper-V
Download/Install Docker Desktop

docker-robott · 2019-02-28T02:00:52Z

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30d of inactivity.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle stale

docker-robott · 2020-06-29T03:11:52Z

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle locked

This was referenced Aug 14, 2018

No activity detected on VM, aborting #2253

Closed

No activity detected on VM, aborting #2316

Closed

docker for windows fails on start #2351

Closed

robrich mentioned this issue Aug 14, 2018

Docker fails to start after Windows Update #2317

Closed

liujianm mentioned this issue Aug 28, 2018

No activity detected on VM, aborting #2489

Closed

1 task

docker-robott added the lifecycle/stale label Feb 28, 2019

docker-robott closed this as completed Mar 30, 2019

docker-robott added the lifecycle/locked label Jun 29, 2020

docker locked and limited conversation to collaborators Jun 29, 2020

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

No activity detected on VM, aborting #2214

No activity detected on VM, aborting #2214

robrich commented Jul 16, 2018 •

edited

Loading

robrich commented Jul 16, 2018

robrich commented Jul 20, 2018 •

edited

Loading

robrich commented Jul 23, 2018

rheid commented Jul 26, 2018

robrich commented Jul 28, 2018

QuintinRudman commented Jul 30, 2018

QuintinRudman commented Jul 30, 2018 •

edited

Loading

robrich commented Aug 1, 2018

ghost commented Aug 13, 2018

robrich commented Aug 14, 2018

carlead commented Aug 17, 2018 •

edited

Loading

serialbandicoot commented Aug 22, 2018 •

edited

Loading

superzadeh commented Aug 23, 2018

talgat-ruby commented Aug 23, 2018

superzadeh commented Aug 23, 2018 •

edited

Loading

robrich commented Aug 24, 2018

liujianm commented Aug 28, 2018

syedhassaanahmed commented Oct 24, 2018

marioanz commented Nov 30, 2018

docker-robott commented Feb 28, 2019

docker-robott commented Jun 29, 2020

No activity detected on VM, aborting #2214

No activity detected on VM, aborting #2214

Comments

robrich commented Jul 16, 2018 • edited Loading

robrich commented Jul 16, 2018

robrich commented Jul 20, 2018 • edited Loading

robrich commented Jul 23, 2018

rheid commented Jul 26, 2018

robrich commented Jul 28, 2018

QuintinRudman commented Jul 30, 2018

QuintinRudman commented Jul 30, 2018 • edited Loading

robrich commented Aug 1, 2018

ghost commented Aug 13, 2018

robrich commented Aug 14, 2018

carlead commented Aug 17, 2018 • edited Loading

serialbandicoot commented Aug 22, 2018 • edited Loading

superzadeh commented Aug 23, 2018

talgat-ruby commented Aug 23, 2018

superzadeh commented Aug 23, 2018 • edited Loading

robrich commented Aug 24, 2018

liujianm commented Aug 28, 2018

syedhassaanahmed commented Oct 24, 2018

marioanz commented Nov 30, 2018

Expected behavior

Actual behavior

Information

Steps to reproduce the behavior

docker-robott commented Feb 28, 2019

docker-robott commented Jun 29, 2020

robrich commented Jul 16, 2018 •

edited

Loading

robrich commented Jul 20, 2018 •

edited

Loading

QuintinRudman commented Jul 30, 2018 •

edited

Loading

carlead commented Aug 17, 2018 •

edited

Loading

serialbandicoot commented Aug 22, 2018 •

edited

Loading

superzadeh commented Aug 23, 2018 •

edited

Loading