Posts

Kasm flooding with kasm_agent error GPU caps helper stderr: amdgpu: os_same_file_description couldn't determine if two DRM fds reference the same file description.

After upgrading Kasm on TrueNAS Scale to 1.19.0, there is a flood of error messages like below. host : proxy ingest_date : 20260701143256 application : kasm_agent levelname : ERROR process : __main__.handler server_id : a9d2.............................c74 message GPU caps helper stderr: amdgpu: os_same_file_description couldn't determine if two DRM fds reference the same file description. If they do, bad things may happen! Some online posts suggest that it is MESA issue so changed the Workspaces' Graphics Acceleration Method Preference to DRI3 but it had no effect to the flood of error messages. Reinstall didn't really fix the issue. Noticed a message in Kasm Install Settings that said: GPU acceleration is automatically managed by Kasm Workspaces 1.19.0. Configure GPU settings after installation in the admin panel under Infrastructure > Agents. hence the 'Passthru available GPU' should be checked even if there is no available GPU? Still troubleshooting... [quot...
Post a Comment
Read more

If your kasm-workspaces resets after upgrade in Truenas Scale...

 It can be annoying when Kasm resets every time after Truenas Scale kasm-workspaces app upgrade. In my case every upgrade deleted my Ubuntu instance in the workspace, along with the configuration changes I made. And it just happened to me today. This may be to do with how the app defaults to using "ixVolume (Data created automatically by the system)" for storage and profile. I am guessing that assigning a host path would make the data persist... I'll find out at the next upgrade. Try the following steps to create persistent dataset and use them for kasm-workspaces app installation to avoid automatic reset. 1. Go to Datasets 2. Select '<DataPoolOfYourChoice>' then click [Add Dataset] to create a new dataset called 'kasm' of type 'Generic' Dataset Preset. 3. Select 'kasm' and repeat the same to create 'data' and 'profiles' under it.     [DataPoolOfYourChoice] -+- [kasm] -+- [data]                       ...
Post a Comment
Read more

Kasm stuck on "Creating a secure connection - 100%" accessing through Cloudflare tunnel

The most likely cause is that your browser failed to establish the WebSocket connection needed to stream the session's audio and visuals, or there is a reverse proxy/firewall misconfiguration blocking Kasm's upstream protocols. If you are accessing Kasm workspace through Cloudflare tunnel especially, then Kasm's internal proxy ports (eg. 30128) wouldn't be reachable because you are accessing the page through: [Your browser] --https--> [hostname on Cloudflare:443] --cloudflare tunnel--> [Kasm host:port] So if your Kasm host uses an internal proxy port like 30128, then your browser has no way of reaching it. The solution is to disable the proxy. Go to Kasm's Admin panel Open Admin > Infrastructure > Zones Edit the default zone Change Proxy Port to 0 (zero) Save/Apply
Post a Comment
Read more

Open WebUI cannot see your models in ollama after upgrade

After upgrading Ollama & Open WebUI, my Open WebUI no longer displayed the LLMs in Ollama. Initially I thought it may be to do with the Open WebUI configuration issue so I fiddled around with the IP Addresses of the Ollama API URLs. Especially when I could still access the LLMs in Ollama via Terminal. But a quick search revealed that the most likely cause was Ollama only listening to the local loopback address (127.0.0.1), hence Open WebUI could not connect to Ollama API port. To do so, 1. run the following command in terminal sudo systemctl edit ollama.service 2. Add the following lines in the editor to let Ollama listen to any IP address on the machine [Service] Environment="OLLAMA_HOST=0.0.0.0" 3. Save and close the editor 4. Restart processes and ollama by sudo systemctl daemon-reload sudo systemctl restart ollama   Then the Open WebUI started to show the models available in Ollama.
Post a Comment
Read more

Proxmox VM PCI Passthru Error MSIX PBA outside of specified BAR

Proxmox VM PCIE Passthru Error  MSIX PBA outside of specified BAR I created a Proxmox VM created for LLM purposes, with a NVIDIA RTX 3060 allocated to it through PCIE Passthru, which there are plenty of literature about. Essentially, Enabled "above 4g decoding" in BIOS. Ensure "Re-size BAR Support" is Disabled in BIOS. In PVE host, blacklist the NVIDIA drivers to ensure it is not used by the host so that the GPU can be passed on to the VM. Create a VM which will use the host's virtual GPU as the primary display. While the VM is offline open Hardware to add PCI device, select the GPU with all functions etc. It worked smoothly with the NVIDIA RTX 3060. Then... Later I replaced NVIDIA RTX 3060 with a RTX 5060Ti, thinking that it should be a smooth upgrade because the new card is using the same PCIE slot & the VM would use the same NVIDIA driver,  Upon replacing the GPU though, the VM would refuse to start with the following error message: MSIX PBA outside of sp...
Post a Comment
Read more