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

Hide KVM signature when using GPU passthrough to support more GPU models #3459

Merged
merged 1 commit into from
Dec 18, 2018

Conversation

alasdairtran
Copy link
Contributor

Currently, when using the GPU passthrough mode, certain GPU models such as Titan X will not work. To reproduce the error:

  1. Use a GPU such as Titan X Pascal.
  2. Start minikube with minikube start --vm-driver kvm2 --gpu
  3. Install the NVIDIA driver: minikube addons enable nvidia-driver-installer

The driver installation will then fail. Further investigation shows that this is because the command nvidia-smi fails with the error Unable to determine the device handle for GPU 0000:0X:00.0: Unknown Error.

The error occurs because NVIDIA doesn't seem to support GPU passthrough for certain lower-end models such as the Titan X family.

The fix for this is to hide the KVM hypervisor signature (see here). I have tested this fix with Titan X Pascal and the NVIDIA driver was installed successfully and the GPU works well without any problem in Minikube. As far as I can tell, I don't think there is any negative side effects of hiding the KVM signature.

@k8s-ci-robot
Copy link
Contributor

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.


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.

@k8s-ci-robot k8s-ci-robot added cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Dec 15, 2018
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: alasdairtran
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: luxas

If they are not already assigned, you can assign the PR to them by writing /assign @luxas in a comment when ready.

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:

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

@minikube-bot
Copy link
Collaborator

Can one of the admins verify this patch?

@alasdairtran
Copy link
Contributor Author

I've signed the CLA.

@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. and removed cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. labels Dec 15, 2018
@tstromberg
Copy link
Contributor

@minikube-bot OK to test

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants