You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
would there be a way to unlock the limiter or set it to another value than the listed 60 or 45 hz found in the description of the mdev type (frl_config=60) (file: /sys/bus/pci/devices/0000:06:00.0/mdev_supported_types/nvidia-259/description)
the gpu tasks (games and such) also dont go above 60hz even when vsync is turned off (tested with multiple games)
tested on a gtx 1660 6GB, Proxmox 8.2.7
The text was updated successfully, but these errors were encountered:
I don't know if this works for you, but I found this
"vGPU overrides
Further up we have created the file /etc/vgpu_unlock/profile_override.toml and I didn't explain what it was for yet. Using that file you can override lots of parameters for your vGPU instances: For example you can change the maximum resolution, enable/disable the frame rate limiter, enable/disable support for CUDA or change the vram size of your virtual gpus."
form: https://gitlab.com/polloloco/vgpu-proxmox#psa-for-pascal-and-older-gpus-like-the-p4-gtx-1080
nope still no difference
also as you can see i have it set to be able to display 2560x1080 (1080p ultrawide) but that is also not available, i can set the resolution via CRU but whenever i restart the vm it just bluescreens indefinitely. (error: Video Tdr Failure nvlddmkm.sys) so i guess its 1920x1080@60 for now.
there is also no custom resolution support in nvidia control panel to add a resolution
would there be a way to unlock the limiter or set it to another value than the listed 60 or 45 hz found in the description of the mdev type (frl_config=60) (file: /sys/bus/pci/devices/0000:06:00.0/mdev_supported_types/nvidia-259/description)
the gpu tasks (games and such) also dont go above 60hz even when vsync is turned off (tested with multiple games)
tested on a gtx 1660 6GB, Proxmox 8.2.7
The text was updated successfully, but these errors were encountered: