Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

E0729 13:52:54.361550 7044 start.go:559] StartHost: create: creating: exit status 1 #4910

Closed
nels0nmaria opened this issue Jul 29, 2019 · 21 comments
Closed

E0729 13:52:54.361550 7044 start.go:559] StartHost: create: creating: exit status 1 #4910

nels0nmaria opened this issue Jul 29, 2019 · 21 comments
Labels
co/hyperv HyperV related issues priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. triage/needs-information Indicates an issue needs more information in order to work on it.

Comments

@nels0nmaria
Copy link

X Unable to start VM: create: creating: exit status 1

  • Sorry that minikube crashed. If this was unexpected, we would love to hear from you:
  • minikube v1.2.0 on windows (amd64)
  • Tip: Use 'minikube start -p ' to create a new cluster, or 'minikube delete' to delete this one.
  • Restarting existing hyperv VM for "minikube" ...
  • Waiting for SSH access ...
  • Configuring environment for Kubernetes v1.10.11 on Docker 18.09.6
    (from this point onwards, I am waiting, since nearly 10 minutes.... should it be that long?)
@sharifelgamal
Copy link
Collaborator

Could you provide the output of minikube logs? It would help us see what's actually happening while minikube start is hanging.

@sharifelgamal sharifelgamal added co/hyperv HyperV related issues priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. triage/needs-information Indicates an issue needs more information in order to work on it. labels Jul 30, 2019
@nels0nmaria
Copy link
Author

nels0nmaria commented Aug 2, 2019 via email

@sharifelgamal
Copy link
Collaborator

Sorry for not being more specific, if you append --alsologtostderr -v=4 to your minikube start call, you should get more verbose logs. If you want even more verbosity, you can make the -v number bigger.

@nels0nmaria
Copy link
Author

nels0nmaria commented Aug 2, 2019 via email

@nels0nmaria
Copy link
Author

nels0nmaria commented Aug 2, 2019 via email

@sharifelgamal
Copy link
Collaborator

It looks like the VM isn't even starting anymore, have you tried doing a minikube delete and retrying a minikube start after?

@nels0nmaria
Copy link
Author

nels0nmaria commented Aug 2, 2019 via email

@nels0nmaria
Copy link
Author

nels0nmaria commented Aug 2, 2019 via email

@nels0nmaria
Copy link
Author

nels0nmaria commented Aug 2, 2019 via email

@nels0nmaria
Copy link
Author

nels0nmaria commented Aug 13, 2019 via email

@medyagh
Copy link
Member

medyagh commented Aug 15, 2019

@fabricadd thanks for not giving up :)

@tstromberg
Copy link
Contributor

I think we're going to need -v=7 to see the machine driver logs: https://minikube.sigs.k8s.io/docs/tasks/debug/#enabling-debug-logs

I didn't see any useful error messages from Hyper-V in the previously attached logs. Do you mind sharing the output of minikube start --alsologtostderr -v=7 <your hyperv flags>

@nels0nmaria
Copy link
Author

nels0nmaria commented Aug 15, 2019 via email

@tstromberg
Copy link
Contributor

@fabricadd - The -p flag is meant to give your cluster a name. I think you can omit it, as it's confusingly setting your cluster name to --kubernetes-version="v1.15.0"

minikube start -p --kubernetes-version="v1.15.0" --vm-driver="hyperv" --memory=4096 --hyperv-virtual-switch="Minikube" --v=7 --alsologtostderr

If you remove the -p option, does the error message improve?

@nels0nmaria
Copy link
Author

nels0nmaria commented Aug 22, 2019 via email

@tstromberg
Copy link
Contributor

OK. If you ever get time, I'd be curious to see the output from minikube v1.3.1, but first run minikube delete to clear up the previous state. Thanks!

@nels0nmaria
Copy link
Author

nels0nmaria commented Aug 23, 2019 via email

@nels0nmaria
Copy link
Author

nels0nmaria commented Aug 23, 2019 via email

@tstromberg
Copy link
Contributor

Ouch. The latter issue seems to be #3963

@ahadmushir
Copy link

Hello,
I too faced the similar issue with minikube v1.3.0

Although, the interesting thing is that the minikube seems to work fine with 4gb RAM allocated in the config.json file but, it fails to create a new hyper-V vm with more than 4gb.

System specs:

System Boot Time: 8/30/2019, 2:05:32 PM
System Manufacturer: LENOVO
System Type: x64-based PC
Processor(s): 1 Processor(s) Installed.
[01]: Intel64 Family 6 Model 78 Stepping 3 GenuineIntel ~2396 Mhz
BIOS Version: LENOVO N1KET39W (1.26 ), 5/28/2018
Windows Directory: C:\Windows
System Directory: C:\Windows\system32
Boot Device: \Device\HarddiskVolume2
System Locale: de;German (Germany)
Input Locale: en-us;English (United States)
Time Zone: (UTC+01:00) Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna
Total Physical Memory: 16,205 MB
Available Physical Memory: 4,437 MB
Virtual Memory: Max Size: 33,613 MB
Virtual Memory: Available: 18,875 MB
Virtual Memory: In Use: 14,738 MB
Page File Location(s): C:\pagefile.sys

Config.json

{
    "WantReportErrorPrompt": false,
    "WantUpdateNotification": false,
    "dashboard": true,
    "disk-size": "50GB",
    "hyperv-virtual-switch": "Primary Virtual Switch",
    "memory": 8192,
    "vm-driver": "hyperv"
}

Output

* minikube v1.3.1 on Microsoft Windows 10 Enterprise 10.0.17763 Build 17763
* Tip: Use 'minikube start -p <name>' to create a new cluster, or 'minikube delete' to delete this one.
[executing ==>] : C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -NoProfile -NonInteractive ( Hyper-V\Get-VM minikube ).state
[stdout =====>] : Off

[stderr =====>] :
* Starting existing hyperv VM for "minikube" ...
[executing ==>] : C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -NoProfile -NonInteractive Hyper-V\Start-VM minikube
[stdout =====>] :
[stderr =====>] : Hyper-V\Start-VM : 'minikube' failed to change state.
The operation failed with error code '32788'.
At line:1 char:1
+ Hyper-V\Start-VM minikube
+ ~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Start-VM], VirtualizationException
    + FullyQualifiedErrorId : Unspecified,Microsoft.HyperV.PowerShell.Commands.StartVM


E0904 09:30:13.655827   25596 start.go:723] StartHost: start: exit status 1
*
X Unable to start VM: start: exit status 1
*
* Sorry that minikube crashed. If this was unexpected, we would love to hear from you:
  - https://github.com/kubernetes/minikube/issues/new/choose

@tstromberg
Copy link
Contributor

@fabricadd I believe the final issue is now addressed by minikube v1.4, as it now forcibly resets broken VM's, and uses the hyperv "Default Switch" for networking. If you still see this issue with minikube v1.4 or higher, please reopen this issue by commenting with /reopen

Thank you for reporting this issue!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
co/hyperv HyperV related issues priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. triage/needs-information Indicates an issue needs more information in order to work on it.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@tstromberg @medyagh @ahadmushir @sharifelgamal @nels0nmaria