Docker Community Forums

Share and learn in the Docker community.

MobyLinux could not be started because the hypervisor is not running. WIN10

beta
docker

(Decemb3r) #1

Expected behavior

Fresh installed OS WIN10 with Docker for Windows.

Actual behavior

Docker won’t start.

Information

[12:11:14.883][Program ][Info ] 1.12.0-rc4-beta19
[12:11:14.883][Program ][Info ] Starting on: 7/16/2016 12:11:14 PM
[12:11:14.898][Program ][Info ] Resources: C:\Program Files\Docker\Docker\Resources
[12:11:14.898][Program ][Info ] OS: Windows 10 Education
[12:11:14.898][Program ][Info ] Edition: Education
[12:11:14.914][Program ][Info ] Id: 1511
[12:11:14.914][Program ][Info ] Build: 10586
[12:11:14.914][Program ][Info ] BuildLabName: 10586.494.amd64fre.th2_release_sec.160630-1736
[12:11:14.914][Program ][Info ] Mixpanel Id: AEF596AB-878D-42F9-A1D2-3454E7EAB51F
[12:11:14.930][Program ][Info ] Sha1: c84feba3aa680f426b8fa66f688388611267cd53
[12:11:14.930][Program ][Info ] You can send feedback, including this log file, at https://forums.docker.com/c/docker-for-windows
[12:11:15.315][TrackingStatus ][Info ] Crash report and usage statistics are enabled
[12:11:15.368][Mixpanel ][Info ] Usage Statistic: appLaunched
[12:11:15.849][NamedPipeClient][Info ] Sending Version()…
[12:11:15.886][NamedPipeClient][Info ] Received response for Version
[12:11:15.886][Mixpanel ][Info ] Usage Statistic: heartbeat
[12:11:15.871][NamedPipeServer][Info ] Version done.
[12:11:16.134][NamedPipeClient][Info ] Sending Stop()…
[12:11:16.149][Updater ][Info ] Checking for updates on channel Beta…
[12:11:16.149][NamedPipeServer][Info ] Stop()
[12:11:16.169][HyperV ][Info ] Stop
[12:11:16.172][PowerShell ][Info ] Run script with parameters: -Stop True…
[12:11:16.535][Updater ][Info ] Local build 5465 is as good as the remote 5465 on channel Beta
[12:11:17.008][HyperV ][Info ] VM MobyLinuxVM is stopped
[12:11:17.040][NamedPipeClient][Info ] Received response for Stop
[12:11:17.024][NamedPipeServer][Info ] Stop done.
[12:11:17.040][NamedPipeClient][Info ] Sending Start(Docker.Core.Settings)…
[12:11:17.055][NamedPipeServer][Info ] Start(Docker.Core.Settings)
[12:11:17.055][HyperVGuids ][Info ] Installing GUIDs…
[12:11:17.071][HyperVGuids ][Info ] GUIDs installed
[12:11:17.093][Firewall ][Info ] Opening ports for C:\Program Files\Docker\Docker\Resources\com.docker.proxy.exe…
[12:11:18.326][Firewall ][Info ] Ports are opened
[12:11:18.326][HyperV ][Info ] Create
[12:11:18.341][PowerShell ][Info ] Run script with parameters: -Create True -SwitchSubnetAddress 10.0.75.0 -SwitchSubnetMaskSize 24 -CPUs 2 -Memory 2048 -IsoFile C:\Program Files\Docker\Docker\Resources\mobylinux.iso…
[12:11:19.257][HyperV ][Info ] Using existing Switch: DockerNAT
[12:11:19.827][HyperV ][Info ] Using existing Switch IP address
[12:11:19.843][HyperV ][Info ] Using existing: MobyLinuxVM
[12:11:20.027][HyperV ][Info ] Setting MobyLinuxVM vm CPUs to 2 and Memory to 2048 MB
[12:11:20.027][ProxyProcess ][Info ] Starting…
[12:11:20.043][PowerShell ][Info ] Run script…
[12:11:20.074][ProxyProcess ][Info ] Started
[12:11:20.090][Database ][Info ] Removing com.docker.driver.amd64-linux/proxy/exclude
[12:11:20.090][Database ][Info ] Removing com.docker.driver.amd64-linux/proxy/http
[12:11:20.105][Database ][Info ] Removing com.docker.driver.amd64-linux/proxy/https
[12:11:20.123][ProxyProcess ][Info ] Start com.docker.db.exe --git C:\ProgramData\Docker\database --url hyperv-connect://84575d41-a358-4969-89d4-568b92f9cc87,\.\pipe\dockerDataBase --color never
[12:11:20.127][ProxyProcess ][Info ] Start com.docker.slirp.exe --ethernet hyperv-connect://84575d41-a358-4969-89d4-568b92f9cc87 --dns 10.0.75.1 --port hyperv-connect://84575d41-a358-4969-89d4-568b92f9cc87 --debug
[12:11:20.148][ProxyProcess ][Info ] docker proxy (on deprecated port): ready
[12:11:20.165][ProxyProcess ][Info ] dns server: ready
[12:11:20.174][ProxyProcess ][Info ] poison pill com.docker.service
[12:11:20.172][ProxyProcess ][Info ] com.docker.slirp.exe: using DNS forwarder on 10.0.75.1:53
[12:11:20.184][ProxyProcess ][Info ] docker proxy: ready
[12:11:20.192][ProxyProcess ][Info ] com.docker.slirp.exe: starting port_forwarding port_control_url:hyperv-connect://84575d41-a358-4969-89d4-568b92f9cc87
[12:11:20.201][ProxyProcess ][Info ]
[12:11:20.209][ProxyProcess ][Info ] com.docker.slirp.exe: connecting to 84575d41-a358-4969-89d4-568b92f9cc87:0B95756A-9985-48AD-9470-78E060895BE7
[12:11:20.218][ProxyProcess ][Info ] +9419us Datakit Starting com.docker.db.exe…
[12:11:20.227][ProxyProcess ][Debug ] com.docker.slirp.exe: Waiting for connections on socket hyperv-connect://84575d41-a358-4969-89d4-568b92f9cc87
[12:11:20.246][ProxyProcess ][Warning] com.docker.slirp.exe: no database: using hardcoded network configuration values
[12:11:20.255][ProxyProcess ][Info ] com.docker.slirp.exe: connecting to 84575d41-a358-4969-89d4-568b92f9cc87:30D48B34-7D27-4B0B-AAAF-BBBED334DD59
[12:11:20.264][ProxyProcess ][Debug ] com.docker.slirp.exe: Waiting for connections on socket hyperv-connect://84575d41-a358-4969-89d4-568b92f9cc87
[12:11:20.327][ProxyProcess ][Info ]
[12:11:20.335][ProxyProcess ][Info ] +186855us fs9p [ERROR] dispatcher caught Unix.Unix_error(Unix.EPIPE, “bytes_read”, “”): no more requests will be handled
[12:11:20.868][Database ][Info ] Successfully removed 3 value(s)
[12:11:20.880][Database ][Info ] Writing com.docker.driver.amd64-linux/net/config=static
[12:11:20.892][Database ][Info ] Writing com.docker.driver.amd64-linux/net/address=10.0.75.2
[12:11:20.905][Database ][Info ] Writing com.docker.driver.amd64-linux/net/netmask=255.255.255.0
[12:11:20.914][Database ][Info ] Writing com.docker.driver.amd64-linux/net/gateway=10.0.75.1
[12:11:20.923][Database ][Info ] Writing com.docker.driver.amd64-linux/etc/resolv.conf=nameserver 10.0.75.1
[12:11:20.931][Database ][Info ] Writing com.docker.driver.amd64-linux/network=hybrid
[12:11:20.939][Database ][Info ] Writing com.docker.driver.amd64-linux/etc/docker/daemon.json={“registry-mirrors”:[],“insecure-registries”:[],“debug”:false}
[12:11:20.948][Database ][Info ] Writing com.docker.driver.amd64-linux/etc/sysctl.conf=
[12:11:20.956][Database ][Info ] Writing com.docker.driver.amd64-linux/native/port-forwarding=true
[12:11:21.961][ProxyProcess ][Info ]
[12:11:21.962][Database ][Info ] Successfully wrote 9 value(s)
[12:11:21.974][ProxyProcess ][Info ] +1820697us fs9p [ERROR] dispatcher caught Unix.Unix_error(Unix.EPIPE, “bytes_read”, “”): no more requests will be handled
[12:11:21.991][HyperV ][Info ] Start
[12:11:22.009][PowerShell ][Info ] Run script with parameters: -Start True…
[12:11:22.807][HyperV ][Info ] Starting VM MobyLinuxVM…
[12:11:22.921][NamedPipeServer][Error ] Unable to execute Start: Failed to start VM “MobyLinuxVM”: ‘MobyLinuxVM’ failed to start.

Virtual machine ‘MobyLinuxVM’ could not be started because the hypervisor is not running.

‘MobyLinuxVM’ failed to start. (Virtual machine ID 84575D41-A358-4969-89D4-568B92F9CC87)

Virtual machine ‘MobyLinuxVM’ could not be started because the hypervisor is not running (Virtual machine ID 84575D41-A358-4969-89D4-568B92F9CC87).

The following actions may help you resolve the problem:

  1. Verify that the processor of the physical computer has a supported version of hardware-assisted virtualization.

  2. Verify that hardware-assisted virtualization and hardware-assisted data execution protection are enabled in the BIOS of the physical computer. (If you edit the BIOS to enable either setting, you must turn off the power to the physical computer and then turn it back on. Resetting the physical computer is not sufficient.)

  3. If you have made changes to the Boot Configuration Data store, review these changes to ensure that the hypervisor is configured to launch automatically.

    at System.Management.Automation.Interpreter.ThrowInstruction.Run(InterpretedFrame frame)
    at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)
    [12:11:22.944][NamedPipeClient][Error ] Unable to send Start: Failed to start VM “MobyLinuxVM”: ‘MobyLinuxVM’ failed to start.

Virtual machine ‘MobyLinuxVM’ could not be started because the hypervisor is not running.

‘MobyLinuxVM’ failed to start. (Virtual machine ID 84575D41-A358-4969-89D4-568B92F9CC87)

Virtual machine ‘MobyLinuxVM’ could not be started because the hypervisor is not running (Virtual machine ID 84575D41-A358-4969-89D4-568B92F9CC87).

The following actions may help you resolve the problem:

  1. Verify that the processor of the physical computer has a supported version of hardware-assisted virtualization.

  2. Verify that hardware-assisted virtualization and hardware-assisted data execution protection are enabled in the BIOS of the physical computer. (If you edit the BIOS to enable either setting, you must turn off the power to the physical computer and then turn it back on. Resetting the physical computer is not sufficient.)

  3. If you have made changes to the Boot Configuration Data store, review these changes to ensure that the hypervisor is configured to launch automatically.

[12:11:22.960][NamedPipeClient][Info ] Sending CheckInstallation()…
[12:11:22.972][NamedPipeServer][Info ] CheckInstallation()
[12:11:22.985][HyperV ][Info ] Check Hyper-V Windows optional feature
[12:11:22.999][PowerShell ][Info ] Run script…
[12:11:24.460][HyperV ][Info ] Hyper-V Windows feature is enabled
[12:11:24.487][NamedPipeClient][Info ] Received response for CheckInstallation
[12:11:24.473][NamedPipeServer][Info ] CheckInstallation done.
[12:11:24.500][NamedPipeClient][Info ] Sending CheckHyperVState()…
[12:11:24.524][NamedPipeServer][Info ] CheckHyperVState()
[12:11:24.537][HyperV ][Info ] Check Hyper-V Service State
[12:11:24.550][PowerShell ][Info ] Run script with parameters: -Check True…
[12:11:25.370][HyperV ][Info ] Hyper-V is running and responding
[12:11:25.384][HyperV ][Info ] Hyper-V is running
[12:11:25.411][NamedPipeClient][Info ] Received response for CheckHyperVState
[12:11:25.397][NamedPipeServer][Info ] CheckHyperVState done.
[12:11:25.424][Notifications ][Error ] Failed to start VM “MobyLinuxVM”: ‘MobyLinuxVM’ failed to start.

Virtual machine ‘MobyLinuxVM’ could not be started because the hypervisor is not running.

‘MobyLinuxVM’ failed to start. (Virtual machine ID 84575D41-A358-4969-89D4-568B92F9CC87)

Virtual machine ‘MobyLinuxVM’ could not be started because the hypervisor is not running (Virtual machine ID 84575D41-A358-4969-89D4-568B92F9CC87).

The following actions may help you resolve the problem:

  1. Verify that the processor of the physical computer has a supported version of hardware-assisted virtualization.

  2. Verify that hardware-assisted virtualization and hardware-assisted data execution protection are enabled in the BIOS of the physical computer. (If you edit the BIOS to enable either setting, you must turn off the power to the physical computer and then turn it back on. Resetting the physical computer is not sufficient.)

  3. If you have made changes to the Boot Configuration Data store, review these changes to ensure that the hypervisor is configured to launch automatically.

[12:11:25.459][NamedPipeClient][Info ] Sending GetDebugInfo()…
[12:11:25.469][NamedPipeServer][Info ] GetDebugInfo()
[12:11:44.245][NamedPipeServer][Info ] GetDebugInfo done.
[12:11:44.265][NamedPipeClient][Info ] Received response for GetDebugInfo
[12:11:44.301][Program ][Info ] Sending Bugsnag report 45fa8a95-ce2c-4918-aaf3-1bbd9ba0e330…
[12:11:47.504][Program ][Info ] Bugsnag report 45fa8a95-ce2c-4918-aaf3-1bbd9ba0e330 sent
[12:11:47.543][NamedPipeClient][Info ] Sending DownloadVmLogs()…
[12:11:47.555][NamedPipeServer][Info ] DownloadVmLogs()
[12:11:47.576][PowerShell ][Info ] Run script…
[12:11:47.653][HyperV ][Warning] Unable to download logs: 2016/07/16 12:11:47 Failed to Dial 84575d41-a358-4969-89d4-568b92f9cc87 445ba2cb-e69b-4912-8b42-d7f494d007ea : An invalid argument was supplied.

[12:11:47.667][NamedPipeServer][Info ] DownloadVmLogs done.
[12:11:47.681][NamedPipeClient][Info ] Received response for DownloadVmLogs
[12:13:10.641][ErrorReportWindow][Info ] Open logs
[12:16:06.156][ErrorReportWindow][Info ] Open logs

INFO

BIOS virtualization enabled, intel q6600 processor


(Rolf Neugebauer) #2

Can you create other Hyper-V VMs?


(Fonebone) #3

I have this same issue.

Regarding this troubleshooting suggestion:

where can I find the list of the supported versions of hardware-assisted virtualization?


(Fonebone) #4

Ah, never mind. I found out my processor doesn’t have SLAT.