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

kvm2: Error creating VM: Failed to find user record for uid #3771

Closed
3 tasks
ashnair1 opened this issue Feb 28, 2019 · 7 comments
Closed
3 tasks

kvm2: Error creating VM: Failed to find user record for uid #3771

ashnair1 opened this issue Feb 28, 2019 · 7 comments
Labels
cause/vm-driver When a VM driver bug causes the failure (not nested) co/kvm2-driver KVM2 driver related issues help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/bug Categorizes issue or PR as related to a bug. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. r/2019q2 Issue was last reviewed 2019q2

Comments

@ashnair1
Copy link

ashnair1 commented Feb 28, 2019

If this is a bug report, please include:

  • How to replicate the error, including the exact command-lines used.
  • The full output of the command that failed
  • The operating system name and version used

Command used: minikube start
Output of failed command:

😄 minikube v0.34.1 on linux (amd64)
🔥 Creating kvm2 VM (CPUs=2, Memory=2048MB, Disk=20000MB) ...
💣 Unable to start VM: create: Error creating machine: Error in driver during machine creation: Error creating VM: virError(Code=38, Domain=0, Message='Failed to find user record for uid '64055'')

😿 Sorry that minikube crashed. If this was unexpected, we would love to hear from you:
👉 https://github.com/kubernetes/minikube/issues/new

OS: Ubuntu 16.04
Minikube version: v0.34.1

@afbjorklund
Copy link
Collaborator

Are you using LDAP ? Found this: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1382046

@afbjorklund afbjorklund added the co/kvm2-driver KVM2 driver related issues label Feb 28, 2019
@ashnair1
Copy link
Author

ashnair1 commented Mar 3, 2019

I'm not sure how to verify that. I tried uninstalling and reinstalling the libvirt-bin libvirt-daemon-system qemu-kvm files and now I'm getting this error :

😄 minikube v0.34.1 on linux (amd64)
🔥 Creating kvm2 VM (CPUs=2, Memory=2048MB, Disk=20000MB) ...
💣 Unable to start VM: create: Error creating machine: Error in driver during machine creation: ensuring active networks: setting autostart for network default: virError(Code=55, Domain=19, Message='Requested operation is not valid: cannot set autostart for transient network')

I've now moved on to using virtual box as the vm driver for minikube as I couldn't get kvm2 driver to work.

@tstromberg tstromberg added kind/bug Categorizes issue or PR as related to a bug. priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. cause/vm-driver When a VM driver bug causes the failure (not nested) help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. labels Mar 8, 2019
@tstromberg tstromberg added the r/2019q2 Issue was last reviewed 2019q2 label May 23, 2019
@tstromberg tstromberg changed the title Error creating machine: Error in driver during machine creation: Error creating VM: virError(Code=38, Domain=0, Message='Failed to find user record for uid '64055'') kvm2: Error creating VM: Failed to find user record for uid '64055' May 23, 2019
@tstromberg tstromberg changed the title kvm2: Error creating VM: Failed to find user record for uid '64055' kvm2: Error creating VM: Failed to find user record for uid May 23, 2019
@josedonizetti
Copy link
Member

I'm not sure how to verify that. I tried uninstalling and reinstalling the libvirt-bin libvirt-daemon-system qemu-kvm files and now I'm getting this error :

minikube v0.34.1 on linux (amd64)
Creating kvm2 VM (CPUs=2, Memory=2048MB, Disk=20000MB) ...
Unable to start VM: create: Error creating machine: Error in driver during machine creation: ensuring active networks: setting autostart for network default: virError(Code=55, Domain=19, Message='Requested operation is not valid: cannot set autostart for transient network')

Note for others having the same problem above. minikube (kvm2 driver) doesn't work with transient networks, only persistent networks. From libvirt documentation: transient network, once created (using net-create) lasts until destroyed or the libvirt daemon restarts. To create a persistent network, you can use the same XML used for the transient network but instead of net-create use net-define, then net-start.

If you are using the default network, you can delete it net-destroy and then use the kvm documentation to create a new one https://github.com/kubernetes/minikube/blob/master/docs/drivers.md#troubleshoot

@fejta-bot
Copy link

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 29, 2019
@tstromberg
Copy link
Contributor

I'm closing this issue as it hasn't seen activity in awhile, and it's unclear if this issue still exists. If this issue does continue to exist in the most recent release of minikube, please feel free to re-open it.

Thank you for opening the issue!

@olof-nord
Copy link

olof-nord commented Feb 10, 2020

This issue unfortunately still exists.

EDIT: I was missing dnsmasq and ebtables, more info here.
https://superuser.com/questions/1063240/libvirt-failed-to-initialize-a-valid-firewall-backend

minikube version: v1.6.2
commit: 54f28ac

minikube start
😄 minikube v1.6.2 on Arch rolling
✨ Automatically selected the 'kvm2' driver (alternates: [virtualbox none])
🔥 Creating kvm2 VM (CPUs=2, Memory=2000MB, Disk=20000MB) ...

💣 Unable to start VM. Please investigate and run 'minikube delete' if possible: create: Error creating machine: Error in driver during machine creation: ensuring active networks: starting network default: virError(Code=1, Domain=59, Message='internal error: Failed to initialize a valid firewall backend')

😿 minikube is exiting due to an error. If the above message is not useful, open an issue:
👉 https://github.com/kubernetes/minikube/issues/new/choose

@tstromberg
Copy link
Contributor

@olof-nord - Your issue appears to be an unrelated system configuration issue. Please check:

If those don't help, please open a new issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cause/vm-driver When a VM driver bug causes the failure (not nested) co/kvm2-driver KVM2 driver related issues help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/bug Categorizes issue or PR as related to a bug. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. r/2019q2 Issue was last reviewed 2019q2
Projects
None yet
Development

No branches or pull requests

7 participants