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

The virtual machine was created by kubevirt and the card was used, but the number of available allocations is still 1 #126

Open
RonaldFletcher opened this issue Nov 27, 2024 · 0 comments

Comments

@RonaldFletcher
Copy link

What happened:

I have a t4 card in my node, and a virtual machine has been started to occupy it, but the node shows that the number of allocable cards is still 1
image
What you expected to happen:

image

allocateable:
nvidia.com/TU104GL_TESLA T4: 0

How to reproduce it (as minimally and precisely as possible):
Steps to reproduce the behavior.

Additional context:
Add any other context about the problem here.

Environment:

  • KubeVirt version (use virtctl version): 1.2
  • Kubernetes version (use kubectl version): 1.28.1+k3s
  • VM or VMI specifications: N/A
  • Cloud provider or hardware configuration: N/A
  • OS (e.g. from /etc/os-release): N/A
  • Kernel (e.g. uname -a): N/A
  • Install tools: N/A
  • Others: N/A
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant