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

gpu memory incorretly allocated using vgpu-memory-percentage resource name #3465

Open
abowloflrf opened this issue May 13, 2024 · 3 comments · May be fixed by #3466
Open

gpu memory incorretly allocated using vgpu-memory-percentage resource name #3465

abowloflrf opened this issue May 13, 2024 · 3 comments · May be fixed by #3466
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@abowloflrf
Copy link

What happened:

I'm using volcano-vgpu-device-plugin with Volcano, when i'm trying to allocate vgpu with resource:

volcano.sh/vgpu-number: 1
volcano.sh/vgpu-cores: 50
volcano.sh/vgpu-memory-percentage: 20

The allocation results in Pod annotations show 0 memory was allocated, which is incorrect.

Volcano scheduler logs:

image

What you expected to happen:

The allocated memory should be totalMemory * percetage / 100 but not 0

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

  • Volcano Version: v1.8.2
  • Kubernetes version (use kubectl version):
  • Cloud provider or hardware configuration:
  • OS (e.g. from /etc/os-release):
  • Kernel (e.g. uname -a):
  • Install tools:
  • Others:
@abowloflrf abowloflrf added the kind/bug Categorizes issue or PR as related to a bug. label May 13, 2024
@Monokaix
Copy link
Member

Thanks, we'd better add some ut.

@Monokaix
Copy link
Member

cc @archlitchi

@archlitchi
Copy link
Contributor

'vgpu-memory-percentage' is not supported for volcano in this version, we plan to implement in the future

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants