Unable to start minikube:The Virtual Machine Management Service failed to start the virtual machine 'minikube' because one of the Hyper-V components is not running

[akhilkumar438]

minikube start --vm-driver hyperv --hyperv-virtual-switch "Switch" * minikube v1.13.0 on Microsoft Windows 10 Pro 10.0.18363 Build 18363

• Using the hyperv driver based on existing profile
  *** Starting control plane node minikube in cluster minikube
  ! StartHost failed, but will try again: Error loading existing host. Please try running [minikube delete], then run [minikube start] again.: filestore "minikube": open C:\Users\someuser.minikube\machines\minikube\config.json: The system cannot find the file specified.**
• Failed to start hyperv VM. Running "minikube delete" may fix it: Error loading existing host. Please try running [minikube delete], then run [minikube start] again.: filestore "minikube": open C:\Users\someuser.minikube\machines\minikube\config.json: The system cannot find the file specified.

X Exiting due to GUEST_NOT_FOUND: Failed to start host: Error loading existing host. Please try running [minikube delete], then run [minikube start] again.: filestore "minikube": open C:\Users\Someuser.minikube\machines\minikube\config.json: The system cannot find the file specified.

• Suggestion: minikube is missing files relating to your guest environment. This can be fixed by running 'minikube delete'
• Related issue: StartHost failed, but will try again: Error loading existing host. Please try running [minikube delete], then run [minikube start] again.: filestore "minikube": #9130

C:\WINDOWS\system32>minikube delete

• Removing C:\Users\Someuser.minikube\machines\minikube ...
• Removed all traces of the "minikube" cluster.

C:\WINDOWS\system32>minikube start --vm-driver hyperv --hyperv-virtual-switch "Switch"

• minikube v1.13.0 on Microsoft Windows 10 Pro 10.0.18363 Build 18363
  ! Both driver=hyperv and vm-driver=hyperv have been set.

  Since vm-driver is deprecated, minikube will default to driver=hyperv.

  If vm-driver is set in the global config, please run "minikube config unset vm-driver" to resolve this warning.

• Using the hyperv driver based on user configuration

• Starting control plane node minikube in cluster minikube

• Creating hyperv VM (CPUs=2, Memory=4000MB, Disk=20000MB) ...
  E0919 23:33:08.764683 8212 main.go:111] libmachine: [stderr =====>] : Hyper-V\Start-VM : 'minikube' failed to start.
  Failed to start the virtual machine 'minikube' because one of the Hyper-V components is not running.
  'minikube' failed to start
  The Virtual Machine Management Service failed to start the virtual machine 'minikube' because one of the Hyper-V components is not running
  At line:1 char:1

• Hyper-V\Start-VM minikube

•   + CategoryInfo          : NotSpecified: (:) [Start-VM], VirtualizationException
    + FullyQualifiedErrorId : OperationFailed,Microsoft.HyperV.PowerShell.Commands.StartVM
  
  
  

• Stopping node "minikube" ...
• Deleting "minikube" in hyperv ...
  ! StartHost failed, but will try again: creating host: create: creating: exit status 1
• Failed to start hyperv VM. Running "minikube delete" may fix it: Error loading existing host. Please try running [minikube delete], then run [minikube start] again.: filestore "minikube": open C:\Users\someuser.minikube\machines\minikube\config.json: The system cannot find the file specified.

X Exiting due to GUEST_NOT_FOUND: Failed to start host: Error loading existing host. Please try running [minikube delete], then run [minikube start] again.: filestore "minikube": open C:\Users\someuser.minikube\machines\minikube\config.json: The system cannot find the file specified.

• Suggestion: minikube is missing files relating to your guest environment. This can be fixed by running 'minikube delete'
• Related issue: StartHost failed, but will try again: Error loading existing host. Please try running [minikube delete], then run [minikube start] again.: filestore "minikube": #9130

Hyperv is enabled and its a virtual box tried to install, uninstall and installed drivers, start and stop hyperv services but none of the solution is worked - please help -

[RA489]

/triage support

[herrsergio]

I'm having the same issue.

[herrsergio]

Here are the last log lines:

I1019 16:19:26.763088    6356 main.go:118] libmachine: Writing magic tar header
I1019 16:19:26.764080    6356 main.go:118] libmachine: Writing SSH key tar header
I1019 16:19:26.775080    6356 main.go:118] libmachine: [executing ==>] : C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -NoProfile -NonInteractive Hyper-V\Convert-VHD -Path 'C:\Users\scuellarv\.minikube\machines\minikube\fixed.vhd' -DestinationPath 'C:\Users\s
cuellarv\.minikube\machines\minikube\disk.vhd' -VHDType Dynamic -DeleteSource
I1019 16:19:32.490754    6356 main.go:118] libmachine: [stdout =====>] :
I1019 16:19:32.494789    6356 main.go:118] libmachine: [stderr =====>] :
I1019 16:19:32.494789    6356 main.go:118] libmachine: [executing ==>] : C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -NoProfile -NonInteractive Hyper-V\Resize-VHD -Path 'C:\Users\scuellarv\.minikube\machines\minikube\disk.vhd' -SizeBytes 20000MB
I1019 16:19:36.524026    6356 main.go:118] libmachine: [stdout =====>] :
I1019 16:19:36.528024    6356 main.go:118] libmachine: [stderr =====>] :
I1019 16:19:36.528024    6356 main.go:118] libmachine: [executing ==>] : C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -NoProfile -NonInteractive Hyper-V\New-VM minikube -Path 'C:\Users\scuellarv\.minikube\machines\minikube' -SwitchName 'My_HyperV_Virtual_Swi
tch' -MemoryStartupBytes 6000MB
I1019 16:19:40.027339    6356 main.go:118] libmachine: [stdout =====>] :
Name     State CPUUsage(%) MemoryAssigned(M) Uptime   Status             Version
----     ----- ----------- ----------------- ------   ------             -------
minikube Off   0           0                 00:00:00 Operating normally 8.0



I1019 16:19:40.032125    6356 main.go:118] libmachine: [stderr =====>] :
I1019 16:19:40.032125    6356 main.go:118] libmachine: [executing ==>] : C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -NoProfile -NonInteractive Hyper-V\Set-VMMemory -VMName minikube -DynamicMemoryEnabled $false
I1019 16:19:44.587577    6356 main.go:118] libmachine: [stdout =====>] :
I1019 16:19:44.591615    6356 main.go:118] libmachine: [stderr =====>] :
I1019 16:19:44.591615    6356 main.go:118] libmachine: [executing ==>] : C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -NoProfile -NonInteractive Hyper-V\Set-VMProcessor minikube -Count 2
I1019 16:19:47.725546    6356 main.go:118] libmachine: [stdout =====>] :
I1019 16:19:47.728548    6356 main.go:118] libmachine: [stderr =====>] :
I1019 16:19:47.729548    6356 main.go:118] libmachine: [executing ==>] : C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -NoProfile -NonInteractive Hyper-V\Set-VMDvdDrive -VMName minikube -Path 'C:\Users\scuellarv\.minikube\machines\minikube\boot2docker.iso'
I1019 16:19:55.040578    6356 main.go:118] libmachine: [stdout =====>] :
I1019 16:19:55.044577    6356 main.go:118] libmachine: [stderr =====>] :
I1019 16:19:55.044577    6356 main.go:118] libmachine: [executing ==>] : C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -NoProfile -NonInteractive Hyper-V\Add-VMHardDiskDrive -VMName minikube -Path 'C:\Users\scuellarv\.minikube\machines\minikube\disk.vhd'
I1019 16:20:02.272987    6356 main.go:118] libmachine: [stdout =====>] :
I1019 16:20:02.275014    6356 main.go:118] libmachine: [stderr =====>] :
I1019 16:20:02.275014    6356 main.go:118] libmachine: Starting VM...
I1019 16:20:02.275014    6356 main.go:118] libmachine: [executing ==>] : C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -NoProfile -NonInteractive Hyper-V\Start-VM minikube
I1019 16:20:09.130154    6356 main.go:118] libmachine: [stdout =====>] :
E1019 16:20:09.340324    6356 main.go:114] libmachine: [stderr =====>] : Hyper-V\Start-VM : 'minikube' failed to start.
Failed to start the virtual machine 'minikube' because one of the Hyper-V components is not running.
'minikube' failed to start. (Virtual machine ID B3890AA6-EFAF-475C-9480-4D260FD02782)
The Virtual Machine Management Service failed to start the virtual machine 'minikube' because one of the Hyper-V components is not running (Virtual machine ID B3890AA6-EFAF-475C-9480-4D260FD02782).
At line:1 char:1
+ Hyper-V\Start-VM minikube
+ ~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Start-VM], VirtualizationException
    + FullyQualifiedErrorId : OperationFailed,Microsoft.HyperV.PowerShell.Commands.StartVM


I1019 16:20:11.264900    6356 client.go:168] LocalClient.Create took 1m6.1494976s
I1019 16:20:13.477726    6356 start.go:130] duration metric: createHost completed in 1m8.3673176s
I1019 16:20:13.480719    6356 start.go:81] releasing machines lock for "minikube", held for 1m8.3713112s
W1019 16:20:13.482718    6356 out.go:145] * Failed to start hyperv VM. Running "minikube delete" may fix it: creating host: create: creating: exit status 1
* Failed to start hyperv VM. Running "minikube delete" may fix it: creating host: create: creating: exit status 1
I1019 16:20:13.486719    6356 out.go:109]

W1019 16:20:13.487720    6356 out.go:145] X Exiting due to GUEST_PROVISION: Failed to start host: creating host: create: creating: exit status 1
X Exiting due to GUEST_PROVISION: Failed to start host: creating host: create: creating: exit status 1
W1019 16:20:13.488718    6356 out.go:145] *
*
W1019 16:20:13.494719    6356 out.go:145] * If the above advice does not help, please let us know:
* If the above advice does not help, please let us know:
W1019 16:20:13.495720    6356 out.go:145]   - https://github.com/kubernetes/minikube/issues/new/choose
  - https://github.com/kubernetes/minikube/issues/new/choose
I1019 16:20:13.499719    6356 out.go:109]

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

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

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten

[sharifelgamal]

Hyper-V\Start-VM : 'minikube' failed to start. Failed to start the virtual machine 'minikube' because one of the Hyper-V components is not running. is the most telling line of logs here. This implies that, yes, Hyper-V is installed, but that not all of its components have been enabled.

You can fix that by running the following in an elevated Powershell terminal:
Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V -All

[sharifelgamal]

@akhilkumar438 did the above suggestion help?

[spowelljr]

Hi @akhilkumar438, we haven't heard back from you, do you still have this issue?
There isn't enough information in this issue to make it actionable, and a long enough duration has passed, so this issue is likely difficult to replicate.

I will close this issue for now but feel free to reopen when you feel ready to provide more information.

[davidkhala]

I have a same issue.