Search results for query: nvidia-smi

...patched vgpu-kvm drivers, version 550.90.05. Patching was done with the guide by polloloco (https://gitlab.com/polloloco/vgpu-proxmox) nvidia-smi shows expected output nvidia-smi vgpu shows expected output mdevctl types shows expected output Nouveau driver has been blacklisted Iommu confirmed...

...2025] NVRM: Attempting to remove device 0000:27:00.0 with non-zero usage count! It turns out that NetData and Beszel both use the nvidia-smi command in a persistent mode to monitor the temperature, which was preventing the kernel from unloading it. I uninstalled the nVidia drivers from the...

...nothing has changed with the config afaik (last rebooted about a week ago). What the heck is happening?? I'm able to view the card from `nvidia-smi` on the host, so I know it "works": root@proxmox:~# nvidia-smi Fri May 9 11:49:13 2025...

...day. Lots piling up around that needed to be addressed. The story so far: I loaded the tesla-470 drivers and this is acknowledged, but nvidia-smi is still showing 470-520 drivers. I have read a few places this is just a hang over as lo long as the 470-drivers are installed. nvidia-smi is...

normally you would not install manually the .run package or .deb package but use the built in package manager, e.g. apt install <some-package> this will download the package automatically you can't install both the package and the .run file simultaneously since those will conflict with each...

...are *.deb and I have no idea how to switch between the two. The dev setup you advised corelated with the set up I followed. I can get the nvidia-smi working on both my pve and lxc, but I have no idea how to install the .deb files with the method that got me so far. I am on my fifth Proxmox...

Some old, same old: I keep getting NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running. Also the info you sent has me installing Version 535.183.01 drivers, yet even Proxmox is telling me to install the...

...When i went to test install an App just to make sure the video cards would show up in the app and neither card is there. When I go to nvidia-smi I can see both cards and they do not have any processes. If i sudo nvidia-smi -i -pm ENABLED to each card i can now see them in the app but i get a...

...way. Installed the Nvidia Host drivers for the Linux KVM OS which is compatible to ProxMox. We are able to see the Nvidia GPU via nvidia-smi command. But when we try to do the Resource Mapping it is not showing VGPU slices i.e. 2Q, 4Q, 6Q etc. The only difference I have noticed is in the...

...the drivers, Cuda and other supporting things [don’t quite remember] on the host then install the same driver on the vm/ct. Then running “nvidia-smi” I got GPU details both on node and vm level. I remember creating documentation on the process to try to help but it was all over the place as...

Think I'm in the same boat. nvidia-smi on the host: nvidia-smi Fri Apr 25 01:04:56 2025 +---------------------------------------------------------------------------------------+ | NVIDIA-SMI 535.247.02 Driver Version: 535.247.02 CUDA Version: N/A |...

...modded vbios. uefi...csm... The monitor turns on but I get no image. SSHing into the VM the nvidia driver is loaded but without output. nvidia-smi confirms no monitor detected. I've yet to see the ovmf bios screen ! Tried proxmox kernel 6.8, 611 and 6.14, 4G decoding and rebar on/off in bios...

...GRID RTX6000-4Q Display Adapter On an Ubuntu VM, I believe the VGPU works fine, I tried transcoding Jellyfin and I can the status with nvidia-smi Here is my Windows VM config: agent: 1 balloon: 0 bios: ovmf boot: order=scsi0 cores: 4 cpu: host efidisk0...

...let vGPU on A100 work? I got the same issue as others, `mdevctl types` got empty output. ``` root@pve:~# mdevctl types root@pve:~# nvidia-smi Thu Apr 24 12:14:38 2025 +---------------------------------------------------------------------------------------+ | NVIDIA-SMI 535.161.05...

...+-----------------------------------------------------------------------------------------+ | NVIDIA-SMI 550.144.02 Driver Version: 550.144.02 CUDA Version: N/A | |-----------------------------------------+------------------------+----------------------+ | GPU Name...

...for the sake of future reference as thats kind of an annoyance. one thing that can reduce ram is ECC but it appears to be off in your nvidia-smi and that should be 12.5% so 1024mb on 8gb, which would make it 7168mb and vGPU then shouldnt work if it was enabled. so it doesnt appear to be that...

...issue myself, i found another post on a blog in Chinese that the user was also using vgpu with proxmox using a P4 and they had the exact nvidia-smi output you have, so it seems like some kind of bios setting or issue on some of the P4s, have you noticed it saying 8192mb before at any point or...

...mine shows with the 2x4GB profiles running. +-----------------------------------------------------------------------------------------+ | NVIDIA-SMI 550.144.02 Driver Version: 550.144.02 CUDA Version: N/A |...

Yeah, it is set. But I'll go back thru everything just to make sure. Here is my nvidia-smi from one host that just has a single vm/vgpu in use: The mdev type is nvidia-765. I wonder if there is something on the host causing some memory usage and taking a bit off the max? 7680MiB...

...did the cargo build step and rebooted. Installed the 17.5 host drivers and copied the vgpuConfig.xml over. I am able to see my P4 with nvidia-smi and I can see the mdev types. I set the vendor/subvendor to 0x10de / 0x10de I set the device-id/sub-device-id to 0x2233 / 0x165a When I boot up...