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.

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

minikube start with kvm-qemu-uri still fails due to non-existent "default" network #9190

Closed
ge79so opened this issue Sep 5, 2020 · 2 comments
Labels
co/kvm2-driver KVM2 driver related issues kind/feature Categorizes issue or PR as related to a new feature.

Comments

@ge79so
Copy link

ge79so commented Sep 5, 2020

Steps to reproduce the issue:

On Debian stable 10.5
NB. KVM is installed and working with virt-manager

$ minikube start --kvm-qemu-uri qemu:///session

Full output of failed command:

🔄 Restarting existing kvm2 VM for "minikube" ...
😿 Failed to start kvm2 VM. Running "minikube delete" may fix it: driver start: creating network: network default doesn't exist: virError(Code=43, Domain=19, Message='Network not found: no network with matching name 'default'')

❌ Exiting due to GUEST_PROVISION: Failed to start host: driver start: creating network: network default doesn't exist: virError(Code=43, Domain=19, Message='Network not found: no network with matching name 'default'')

😿 If the above advice does not help, please let us know:
👉 https://github.com/kubernetes/minikube/issues/new/choose

$ user@pc:/usr/local/bin$ minikube delete

🔥 Removing /home/user/.minikube/machines/minikube ...
💀 Removed all traces of the "minikube" cluster.

user@pc:/usr/local/bin$ minikube start --kvm-qemu-uri qemu:///session

😄 minikube v1.13.0 on Debian 10.5
✨ Automatically selected the kvm2 driver
👍 Starting control plane node minikube in cluster minikube
🔥 Creating kvm2 VM (CPUs=2, Memory=2200MB, Disk=20000MB) ...
🤦 StartHost failed, but will try again: creating host: create: Error creating machine: Error in driver during machine creation: creating network: network default doesn't exist: virError(Code=43, Domain=19, Message='Network not found: no network with matching name 'default'')
🔄 Restarting existing kvm2 VM for "minikube" ...
😿 Failed to start kvm2 VM. Running "minikube delete" may fix it: driver start: creating network: network default doesn't exist: virError(Code=43, Domain=19, Message='Network not found: no network with matching name 'default'')

❌ Exiting due to GUEST_PROVISION: Failed to start host: driver start: creating network: network default doesn't exist: virError(Code=43, Domain=19, Message='Network not found: no network with matching name 'default'')

😿 If the above advice does not help, please let us know:
👉 https://github.com/kubernetes/minikube/issues/new/choose

Full output of minikube start command used, if not already included:

Optional: Full output of minikube logs command:

$ minikube logs

❌ Exiting due to GUEST_KVM2_NO_DOMAIN: state: getting connection: looking up domain: virError(Code=42, Domain=10, Message='Domain not found: no domain with matching name 'minikube'')
💡 Suggestion: The VM that minikube is configured for no longer exists. Run 'minikube delete'
🍿 Related issue: #3636

@afbjorklund
Copy link
Collaborator

It is not possible to run the libvirt driver (kvm2) as user, due to the missing network. See #4288

Duplicated request in #9009

@afbjorklund afbjorklund added co/kvm2-driver KVM2 driver related issues kind/feature Categorizes issue or PR as related to a new feature. labels Sep 5, 2020
@tstromberg
Copy link
Contributor

This issue appears to be a duplicate of #9009 do you mind if we move the conversation there?

Ths way we can centralize the content relating to the issue. If you feel that this issue is not in fact a duplicate, please re-open it using /reopen. If you have additional information to share, please add it to the new issue.

Thank you for reporting this!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
co/kvm2-driver KVM2 driver related issues kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

No branches or pull requests

3 participants