Docker Community Forums

Share and learn in the Docker community.

MobyLinux cannot start because Hyper-V is not running... but the log says it running


(Sleroux) #1

Expected behavior

Docker should initialize properly…

Actual behavior

MobyLinux VM fail to start

Information

[21:23:42.607][Updater ][Info ] Checking for updates on the Beta channel…
[21:23:42.960][Updater ][Info ] Found remote version. Version = 1.11.1.2446
[21:23:42.968][Updater ][Info ] Local version is up to date.
[21:23:42.978][Notifications ][Info ] Docker is up-to-date
[21:23:43.117][Updater ][Info ] Check for update done.
[21:24:00.704][NamedPipeServer][Info ] GetVmMaxMemory:[]
[21:24:00.808][PowerShell ][Info ] Run script…
[21:24:00.970][NamedPipeServer][Info ] GetVmMaxMemory done.
[21:24:08.641][Notifications ][Info ] Docker is applying your changes…
[21:24:08.662][NamedPipeServer][Info ] Restart:[2,3072]
[21:24:08.671][HyperV ][Info ] Stop
[21:24:08.676][PowerShell ][Info ] Run script with parameters: -Stop True…
[21:24:10.107][HyperV ][Info ] Kill VM MobyLinuxVM…
[21:24:10.193][HyperV ][Info ] VM MobyLinuxVM is stopped
[21:24:10.200][HyperV ][Info ] Create
[21:24:10.207][PowerShell ][Info ] Run script with parameters: -Create True -CPUs 2 -Memory 3072 -IsoFile C:\Program Files\Docker\Docker\Resources\mobylinux.iso…
[21:24:11.227][HyperV ][Info ] Using existing Switch: DockerNAT
[21:24:11.392][HyperV ][Info ] Using existing Switch IP address
[21:24:11.416][HyperV ][Info ] Using existing Net NAT: DockerNAT
[21:24:11.437][HyperV ][Info ] Using existing: MobyLinuxVM
[21:24:11.618][HyperV ][Info ] Setting MobyLinuxVM vm CPUs to 2 and Memory to 3072 MB
[21:24:11.623][Dhcp ][Info ] Dhcp starting on port 67, on interface vEthernet (DockerNAT)…
[21:24:11.703][Dhcp ][Info ] Dhcp started.
[21:24:11.707][HyperV ][Info ] Start
[21:24:11.712][PowerShell ][Info ] Run script with parameters: -Start True…
[21:24:12.522][HyperV ][Info ] Starting VM MobyLinuxVM…
[21:24:12.580][Notifications ][Error ] Error: Failed to start VM “MobyLinuxVM”: ‘MobyLinuxVM’: falha ao iniciar… . Não foi possível iniciar a máquina virtual ‘MobyLinuxVM’ porque o hipervisor não está em execução… . ‘MobyLinuxVM’: falha ao iniciar. (ID de máquina virtual E8B72270-AFC9-478D-AD40-2ECE20FA8390). . Não foi possível iniciar a máquina virtual ‘MobyLinuxVM’ porque o hipervisor não está em execução (ID de máquina virtual E8B72270-AFC9-478D-AD40-2ECE20FA8390)… As ações que se seguem podem ajudar a resolver o problema:. 1) Verifique se o processador do computador físico tem uma versão suportada da virtualização assistida por hardware… 2) Verifique se a virtualização assistida por hardware e a proteção de execução de dados assistida por hardware estão ativadas no BIOS do computador físico. (Se editar o BIOS para ativar qualquer uma destas definições, tem de desligar a alimentação do computador físico e voltar a ligá-la. Não é suficiente reinicializar o computador físico.). 3) Se tiver efetuado alterações ao arquivo de Dados de Configuração de Arranque, reveja estas alterações para assegurar que o hipervisor está configurado para ser iniciado automaticamente…
[21:24:12.583][Program ][Info ] Sending Bugsnag report 8667addf-7d79-4e48-b39e-ff274901ec05 …
[21:24:13.028][Program ][Info ] Bugsnag report sent


(Rolf Neugebauer) #2

Hi

in the logs we check if Hyper-V is installed but it appears that there was an issue with Hyper-V itself. The line following
[21:24:12.580][Notifications ][Error ] Error: Failed to start VM “MobyLinuxVM”: ‘MobyLinuxVM’: falha ao iniciar
suggest various things to check on your system, including if Virtualisation support is enabled in the BIOS

Could you check these things?

Thanks
Rolf


(Sleroux) #3

Virtualisation appears to be enabled:

How can I check if Hypervisor is running? (i updated Windows 10 Home to Windows 10 Pro, i can open the Hyper-V manager, but the same error occurs if i try t start the VM…)


(Rolf Neugebauer) #4

Hi

thanks for the quick response. AFAIK, the Intel utility will only check if a certain feature is supported but some BIOSes have an option where you can enable/disable features like the Virtualisation support. Can you check your BIOS settings?

Thanks
Rolf


(Sleroux) #5

My BIOS doesn’t have any options to enable/disable Virtualization support… I was trying to install on an Acer V3-578G-5881 laptop…

Hypervisor is not running… I had Windows 10 Home (with vmware and virtual box), I update it to Windows 10 Pro, removed Virtual Box and vmware… But hypervisor is not running…

Any idea?


(Sleroux) #6

Now, I’m Having the following issue:

[00:38:38.143][PowerShell ][Info ] Run script with parameters: -Create True -CPUs 2 -Memory 2048 -IsoFile C:\Program Files\Docker\Docker\Resources\mobylinux.iso…
[00:38:39.031][HyperV ][Info ] Enabled workaround for Build 10586 VMSwitch issue
[00:38:44.896][HyperV ][Info ] Creating Switch: DockerNAT…
[00:38:49.613][HyperV ][Info ] Deleted old IP address
[00:38:49.664][HyperV ][Info ] Switch created.
[00:38:50.349][Notifications ][Error ] Error: Failed to create Switch “DockerNAT”: Instance MSFT_NetIPAddress already exists.
[00:39:11.802][Program ][Info ] Sending Bugsnag report bbd5d059-477f-4030-85c5-b1259d047ad4 …
[00:39:13.156][Program ][Info ] Bugsnag report sent