update libvirtd

[Expire0]

libvirtd must be started before you run minikube. Failure to do so will result in the below error
Failed to connect socket to '/var/run/libvirt/libvirt-sock'
I believe this should be noted in the documentation to assist other users.
Added lines 40-43

[k8s-ci-robot]

Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA.

It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.

---

• If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
• If you signed the CLA as a corporation, please sign in with your organization's credentials at https://identity.linuxfoundation.org/projects/cncf to be authorized.
• If you have done the above and are still having issues with the CLA being reported as unsigned, please email the CNCF helpdesk: helpdesk@rt.linuxfoundation.org

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[minikube-bot]

Can one of the admins verify this patch?

[afbjorklund]

This probably only applies to the KVM drivers ("kvm" and "kvm2") on Linux ? Not VirtualBox etc.

Also, I believe the daemon is started automatically on Debian and derivates like Ubuntu.

[Expire0]

Also, I believe the daemon is started automatically on Debian and derivates like Ubuntu.

I tested this on Ubuntu 18.04 and it does start automatically. The issue may only be related to Centos 7/Fedora 29 /Redhat 7

[afbjorklund]

On other hand, it doesn't really hurt to start it again... But the instructions should be up with the rest of the hypervisor install (like adding yourself to the root-equivalent libvirtd group), rather than with the driver:

To install the KVM2 driver, first install and configure the prereqs:

HERE: Make sure that the libvirt daemon actually started, after installation

Then you will need to add yourself to libvirt group (older distributions may use libvirtd instead)

Then to join the group with your current user session:

Now install the driver:

[Expire0]

I moved the instructions under the install as you suggested. Good idea

[afbjorklund]

Looking good! Just some minor changes

[afbjorklund]

Normally one wants to use "sudo" here, to avoid that annoying popup

[Expire0]

good suggestion. I found that i needed to be root to run through the documentation . If that's the case then sudo is not needed. I updated the doc to include sudo just in case

[afbjorklund]

Status seems a bit paranoid ?

[Expire0]

yeah just a little. I think it may be good to check before moving to the next step.

[Expire0]

updated the document to include sudo before systemctl. Good idea

[Expire0]

removed the extra ticks on line 24

[afbjorklund]

/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: afbjorklund, Expire0

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [afbjorklund]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment