Recent content by Randell

I believe I only got this error with kernel version after (not including) 6.8 (doesn't seem to matter the driver version, official supported 16.11, or older "patched" 16.x drivers, or 17.x (patched/unpatched). I have yet to try patching everything with patched 18 series drivers yet. I'm...

That looks familiar https://forum.proxmox.com/threads/kernel-6-14-nvidia-16-11-warning-remap_pfn_range_internal.169401/

# cat blacklist.conf blacklist nouveau options nouveau modeset=0 I have it blacklisted on all my hosts. I don't remember why I have `options nouveau modeset=0` there.

Do you not have the virtio drivers installed on the guest? Also, what CPU type is assigned to the VM? There has been discussion about not using `host` with a windows guest.

I have 2 VMs that I pass an instance to. Both are Debian 13 hosts with docker installed (and the nvidia container toolkit). It is then passed to the docker containers. One is a codeproject.ai image (codeproject/ai-server:cuda12_2-2.9.7) The other is Emby server, and I'm passing the instance...

I haven't seen any kernel panics, but I am only passing them to Linux VMs and only using the CUDA and video encoding stuff. I am not using it as an actual display adapter in the VM. Maybe that makes a difference.

This might not matter or help at all... When you are booted into the previous kernel, you say your pool is working? If so, then do a `zpool status pool` (or whatever the name of the pool is). If it has sda and sdc listed, then I would export and reimport it With your VMs/containers all...

I use the GPU for a couple of VMs, so I have no choice but to use the vGPU drivers. But yes, the 16.11 drivers will compile just fine with a 6.14 kernel. I only get the above error after the VM starts up. I assume whenever the driver inside there "talks" to host is when I get this message. As...

I went ahead and updated to PVE 9 even though I knew it came with 6.14 and I had this problem and posted in a different thread. Back then I was using patched drivers (I'm using a Tesla P4) because the 16.9 version of the drivers didn't support newer kernels. I saw that 16.11 supported kernel...

Hmm, that's interesting. I've been disappointed with networking as well, and I went with a 7302P by choice to avoid NUMA, but you are saying you see better networking performance when that option is disabled and allow it to present multiple nodes to the OS?

My understanding of ECC is really more for hardware faults, a little power blip or cosmic ray flipping a bit here or there. I definitely wanted it for my system memory with ZFS but for GPU workload (transcoding and codeprojectai for person/vehicle detection with blue iris) I can live with a...

Funny, I just came across this post talking about ECC vram settings. I just turned it off rebooted and now it shows up as the full 8GB https://forum.proxmox.com/threads/disable-vgpu-ecc-memory.121851/ +-----------------------------------------------------------------------------------------+ |...

Yeah, I noticed the 512MB and was proceeding along the same thoughts about something reserving that. It is indeed the only GPU in the system, the board is "Supermicro H11SSL-NC 2.0". (all 3 nodes are the same). I poked and prodded the BIOS and nothing stands out and I don't really remember if...

I'm investigating the vram issue now. Going thru my bios settings, etc. Yeah, I ended up using 1x4GB and 1x2GB vms for now. I'm more curious about the *why* right now. Just to be sure it doesn't cause some other issue.

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...