When using --kvm-gpu: ❌ Exiting due to GUEST_KVM2_NO_DOMAIN

[r-matsuzaka]

What Happened?

I could start minikube without --kvm-gpu but if I add it then I got the errors as Exiting due to GUEST_KVM2_NO_DOMAIN.

I already read https://minikube.sigs.k8s.io/docs/tutorials/nvidia_gpu/

You must enable IOMMU in the kernel: add intel_iommu=on or amd_iommu=on (depending to your CPU vendor) to the kernel command line. Also add iommu=pt to the kernel command line.

I also ran

$ iommu=pt
$ intel_iommu=on

But I got the same error. Is it correct to run in the terminal?

mypc@mypc:$ minikube start --cpus 4 --memory 20G --disk-size 50G --kubernetes-version v1.21.14 --driver=kvm2
😄 minikube v1.28.0 on Ubuntu 22.04
✨ Using the kvm2 driver based on user configuration
👍 Starting control plane node minikube in cluster minikube
🔥 Creating kvm2 VM (CPUs=4, Memory=20480MB, Disk=51200MB) ...
🐳 Preparing Kubernetes v1.21.14 on Docker 20.10.20 ...
▪ Generating certificates and keys ...
▪ Booting up control plane ...
▪ Configuring RBAC rules ...
🔎 Verifying Kubernetes components...
▪ Using image gcr.io/k8s-minikube/storage-provisioner:v5
🌟 Enabled addons: storage-provisioner, default-storageclass
🏄 Done! kubectl is now configured to use "minikube" cluster and "default" namespace by default
mypc@mypc:$ minikube delete
🔥 Deleting "minikube" in kvm2 ...
💀 Removed all traces of the "minikube" cluster.
mypc@mypc:$ minikube start --cpus 4 --memory 20G --disk-size 50G --kubernetes-version v1.21.14 --driver=kvm2 --kvm-gpu
😄 minikube v1.28.0 on Ubuntu 22.04
✨ Using the kvm2 driver based on user configuration
👍 Starting control plane node minikube in cluster minikube
🔥 Creating kvm2 VM (CPUs=4, Memory=20480MB, Disk=51200MB) ...
🤦 StartHost failed, but will try again: creating host: create: Error creating machine: Error in driver during machine creation: creating devices: couldn't generate devices XML: no IOMMU groups found at "/sys/kernel/iommu_groups/". Make sure your host supports IOMMU. See instructions at https://minikube.sigs.k8s.io/docs/tutorials/nvidia_gpu/
🔄 Restarting existing kvm2 VM for "minikube" ...
😿 Failed to start kvm2 VM. Running "minikube delete" may fix it: driver start: getting connection: looking up domain: virError(Code=42, Domain=10, Message='Domain not found: no domain with matching name 'minikube'')

❌ Exiting due to GUEST_KVM2_NO_DOMAIN: Failed to start host: driver start: 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

mypc@mypc:~$ minikube logs --file=log.txt

❌ 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

Attach the log file

I cannot create and attach log file due to the issue.

Operating System

Ubuntu

Driver

KVM2

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

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.