Skip to content

Understanding the Role of Virtual GPU Software and Licensing #1381

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

Open
JT-Trend opened this issue Apr 3, 2025 · 0 comments
Open

Understanding the Role of Virtual GPU Software and Licensing #1381

JT-Trend opened this issue Apr 3, 2025 · 0 comments

Comments

@JT-Trend
Copy link

JT-Trend commented Apr 3, 2025

I’m in the process of setting up a server with a GPU for use in virtualized environments, specifically for running 3D modeling software. My setup involves partitioning the GPU into four separate instances and assigning each one to a different VM. These VMs will be running 3D modeling software that requires GPU acceleration.

I’ve already installed the necessary drivers, partitioned the GPU into four virtual instances, and confirmed that each VM is able to access its allocated portion of the GPU without any issues. Essentially, each of the four VMs can use its respective GPU partition for the software, and the setup seems to be working perfectly so far.

With this configuration, I’m wondering about the role of Virtual GPU (vGPU) software and licensing. Since I have successfully partitioned and assigned the GPU to my VMs, do I still need to purchase or install additional software or licenses? If so, what specific vGPU licensing model would apply to my scenario? I’m assuming the software is necessary for managing these GPU partitions, but I would appreciate more clarity on how it fits into the overall setup.

Any insights or advice would be greatly appreciated!

Thanks!

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