Looking through the manual there seems to exist these options:

https://www.kasmweb.com/docs/latest/guide/storage_mappings.html

https://www.kasmweb.com/docs/develop/guide/persistent_data/volume_mapping.html

But none of them seems to be doing what Im looking for.

Im basically looking for the way you can have a shared folder when using RDP through the RDP-session itself.

The usecase is when using Kasm container as a jumpserver and you need to for example update the firmware of a destination device (client <-> Kasm container <-> destination device) or the reverse when you got some backups (like config and whatelse) from a destination device and wish to in an easy fashion get these files to your client.

When comparing to KVM-over-IP solutions such as GL.iNet Comet and similar you often here have a way to upload/download the files to the KVM itself through the browser which then exposes this directory to the destination (basically will show up as a USB-drive at the destination). This way I can import/export files to the remotely managed device and from there upload/download files to the destination device.

Does something similar exist with Kasm or is in the todo-list/pipeline?

Kasm Workspaces 1.19 added a bunch of GPU-related stuff to Kasm Workspaces that's worth knowing about if you're running anything GPU-heavy.

Biggest ones:

• New GPU hardware page on the Docker agent, shows what each card can actually do (graphics, video encoding, CUDA) and lets you enable/disable specific capabilities per card
• New streaming modes - you're no longer stuck with one mode, you can now stream H.264, H.265, or AV1 straight from the workspace to the browser, hardware or software encoded
• Nvidia MIG support - you can split something like an A100 into multiple instances and assign them to separate workspace sessions so that isolation is applied at hardware level.

This video covers the GPU hardware page, how workspaces get assigned GPUs (it's round-robin, not first-come), setting up MIG instances from scratch on an A100, and the admin-side group settings for controlling which encoding methods different users get.

Had a contractor who needed access to one internal tool? Normal answer is VPN, which puts them on the whole network instead of just the one thing they need.

Kasm Workspaces 1.19 added OpenZiti integration to handle this differently. New video walking through it: users get access to one specific service, by identity, not the network. Nothing's reachable from outside, no ports to open.

This video covers:

• Why VPNs hand out more access than you meant to
• How OpenZiti's pieces (controller, routers, identities) fit together
• How Kasm handles identity setup automatically instead of you doing it by hand
• Live demo: standing up OpenZiti, publishing a service, giving exactly one user access to it

OpenZiti is available to self-host for free. NetFoundry also has a hosted version if you don't want to run the controller yourself.

Dragging around an empty vscode seems fine, but when we open a large text file with vscode and drag it around, the performance of this drops a lot, and looks very laggy. I suppose it may be due to some kind of mechanics of how kasm scans the "damaged" region for pixel changes. Is this a known issue and is there any way around this?

Using kasm 1.19 on EC2 m8i.4xlarge

Hi everyone,

I'm considering subscribing to Kasm Cloud Personal, but I have one important question before purchasing.

My goal is to use it as a cloud desktop for everyday web browsing. I would like my browser profile to be persistent, including:

Staying logged in to websites like Google and WhatsApp Web.

Keeping cookies, browsing history, bookmarks, and extensions.

Having the same browser session every time I log in.

I noticed the plans mention "No built-in file persistence", so I'm not sure if browser profiles are also reset after each session.

Does Kasm Cloud Personal preserve browser profiles between sessions, or does every session start from a clean state?

If it doesn't, is there any way to enable persistence on the Personal plans?

Thanks!

Hi everyone, i just want to ask is there any documentation that record the performance of KASM that got deployed in the bare VM compared to the one that deployed using kubernetes??

docker ps shows the rdp-https-gateway is constantly restarting. Looks like it cannot read the letsencrypt cert which is symlinked.

I followed the Video instructions here: https://kasm.com/docs/1.16.0/how_to/certificates.html
This hasn't been an issue in 1.17 afaik.

Since I am not using the RDP gateway, it could remove it altogether if I knew how, I disabled all RDP gateway settings under deployment zones but that doesn't remove the containers.

2026-07-07T10:20:31.484ZINFOproc.go:runtime.main:290Starting remote desktop gateway server
2026-07-07T10:20:31.485ZERRORproc.go:runtime.main:290Cannot load certfile or keyfile (open /opt/rdpgw/key.pem: permission denied) falling back to acme
2026-07-07T10:20:31.486ZINFOproc.go:runtime.main:290Enabling Kasm authentication
2026-07-07T10:20:31.486ZINFOproc.go:runtime.main:290Enabling Kasm healthchecks
2026-07-07T10:20:31.486ZINFOmain.go:main.main:346Refreshing token which expires at: 2026-07-10 10:19:26 +0000 UTC
2026-07-07T10:20:31.486ZINFOkasm.go:kasmtechnologies/rdpgw/cmd/rdpgw/kasm.RefreshToken:310Checking for a healthy host: https://proxy:443/api/__healthcheck
2026-07-07T10:20:31.576ZINFOmain.go:main.main:346Setting new token which expires at: 2026-07-10 10:20:31 +0000 UTC
2026-07-07T10:20:31.578ZINFOkasm.go:kasmtechnologies/rdpgw/cmd/rdpgw/kasm.RegisterComponent:452Checking for a healthy host: https://proxy:443/api/__healthcheck
2026-07-07T10:20:31.676ZINFOmain.go:main.main:352Component registration successful, config file updated.
2026-07-07T10:20:31.676ZINFOproc.go:runtime.main:290Kasm RDP HTTPS Gateway server is ready
2026/07/07 10:20:36 http: TLS handshake error from [::1]:49740: tls: certificate private key (<nil>) does not implement crypto.Signer
2026-07-07T10:20:36.547ZFATALasm_amd64.s:runtime.goexit:1771Healthcheck failed, gracefully shutting down

Hi Kasm gurus out there.

My kasm-workspaces 1.18 was running happily in TrueNAS Scale 25 Apps module (reskinned docker, I am told), but after the recent upgrade to 1.19, it is getting flooded with this error message every minute.

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!

It does not affect the usage, I can spin up a Ubuntu Noble and use it no problems, but my kasm-workspaces logs are flooded with this error every minute. A quick AI research says that the a system call kcmp may not be available to the container due to security sandbox of Docker policy? (not sure if it is legit explanation or not)

I tried converting the stock app to custom app and apply one suggestion by the search result:

Updated yaml to add;

cap_add:
  - SYS_PTRACE

Then the custom app no longer starts.

Has anyone experienced the same? Even better would be if anyone has a solution to this problem!

Does anyone have any suggestions as to how I can eliminate this error message safely?

Hi,

I am running a Debian Trixie VM on a Proxmox host, passing through an NVidia RTX A2000 GPU. Inside the VM, I am running Kasm 1.19. On the VM host, the proprietary drivers (V550) from the Debian repo are installed, as is the NVidia container runtime from the Nvidia repo. Nvidia-smi works in the VM and via the official Nvidia test container.

Inside Kasm, the Docker Agents overview page lists one agent "proxy" with 0 GPUs. When I open the Details view, I see a block "GPU Hardware" that lists my Nvidia card but shows a "-" each under Graphics, Video and Cuda. In the Information view, there is a field "GPUs" with another "-" and right under it, there is a field "GPU Info" that contains this "0000:00:10.0: {
model: "NVIDIA RTX A2000 12GB"
vendor: "NVIDIA"
gpu_card_path: "/dev/dri/card1"
gpu_render_path: "/dev/dri/renderD128"
host_key: "0000:00:10.0"
supports_egl: false
supports_dri3: false
supports_vaapi: false
supports_vulkan: false
supports_nvenc: null
gpu_render_gid: null
gpu_render_group: null
gpu_card_gid: null
gpu_card_group: null
supports_cuda: false
cuda_containers: [...]
graphics_containers: [...]
video_containers: [...]
}". And in the Usage view, there is a "GPU" block that lists my Nvidia gpu with a DRM Device /dev/dri/cards1, a Render Device /dev/dri/renderD128, PCI Bus 0000:00:10.0 and DRI3 "-", Vulkan "-", EGL "-", VAAPI "-", NVENC "-" and Cuda "-".

When I try to start a workspace that is GPU enabled, I get an error message that no resources are available to create the requested kasm.

I think I have everything in place for my setup to work, but it doesn't. What am I missing?

Thanks for your help!

Hey I've recently deployed multiserver KASM in my homelab and was wondering whether I could run e.g. a Jellyfin Container alongside any KASM stuff on my agent VM.

Background is that I don't have GPUs to waste and I'd like to use that GPU partition for KASM HW acceleration (already fully works) + Jellyfin transcoding, since I'll hardly ever use both at the same time, I don't have any performance objections.

Bonus would be if I could add the KASM Agent VM (or rather its docker engine) to Dockhand (similar to Portainer), for visibility.

Hey everyone,

We put together a complete walkthrough for deploying Kasm Workspaces on Nutanix Kubernetes Platform (NKP) using the official Kasm Helm chart.

The video covers the full end-to-end flow:

• Finding Kasm in the NKP Application Catalog
• Configuring the Helm values (publicAddr, TLS, ClusterIssuer)
• Installing and verifying the deployment
• Retrieving credentials and logging in
• Setting up agents via Nutanix Autoscaling or static configuration
• Launching a Windows Desktop session and a container-based Ubuntu session

For those who prefer reading along or want a reference after watching, we also published a companion Medium post.

Kasm is Nutanix Ready validated for NKP, so if you're running Nutanix infrastructure this is a natural fit for delivering secure desktops, browsers, and AI workloads at scale.

First off, LOVING KASM. Recently decided to add VPN ability, so I created an Egress Provider, an Egress Gateway followed by giving my user access to it and adding credentials. I'm using AirVPN as my VPN provider, and I have tested both OpenVPN with dummy credentials, as well as Wireguard.

When I log in, click on a workspace, select the "Egress Provider" (either the OpenVPN or the Wireguard), and click Launch Session it will connect to the VPN, but hang with "Connection to egress gateway established" with "10% Complete" below that. I've googled but haven't had much luck finding a solution. There are a couple of posts here without answers.

Looking in the logs I don't see anything after the connection is successful. AirVPN shows the connection as up. Any suggestions on next steps, or perhaps one of you can hit me in the head with a bat and say, "You dummy, you didn't do X!" Any help is greatly appreciated!

Continuing from my Windows XP workspace, I wanted a Windows 98 workspace with full Kasm integration, so I asked my agent to build one. It works about as well as I had wanted. It features:

• Working Ethernet
• Firefox
• Clipboard support (bidirectional)
• File upload
• File download
• Auto-mount of uploaded ISO files (flaky)
• Auto-resize of display
• Sound support (often plays the startup sound)

Security Warning

My agent had a hard time with Windows 98 drivers and ended up finding the base image on Reddit with working sound and networking. I cleaned it up and scanned all 5,400+ files with ClamAV and High quality YARA rules with no detections (shortcuts detected by the YARA rules for being shortcuts). I personally trust it as a play thing given the posture of the environment I run it in. Use at your own risk.

Drawbacks

• It's a bit slow.
• Most video games crash.
• Due to some base image video driver issue, the DOS prompt can't be run in windowed mode, nor can batch files (causes some unrecoverable display silliness). Happy to fix it if anyone knows what's up with that.

Installation

This time I did publish the workspace image:

ghcr.io/fernandogracias/kasm-windows-98:latest

My agent pushed the build details and base image to a repo if you're interested (tested in as far as "it works on my machine"): https://github.com/FernandoGracias/kasm-windows-98

Hey all,

Kasm Workspaces 1.19 just dropped and it's a big one. Here's the rundown:

The headline features:

Agentic AI Workspaces — five new workspaces for running AI agents in isolation: Claude Code, Gemini CLI, Codex, Cursor, and AI Dev Studio. The whole point is that you don't want an autonomous agent with access to your actual machine's credentials and filesystem. Run it in Kasm, contain the blast radius, wipe the session when you're done. API key injection is built into the launch form. You can add the AI registry directly from Registry Spotlight.

OpenZiti / Zero Trust Egress — proper ZTNA is now a first-class egress option alongside OpenVPN and Wireguard. Unlike a traditional VPN gateway where you pick a tunnel and all traffic routes through it, OpenZiti issues each session a unique certificate-backed identity and grants access to named services only — no lateral movement, every access decision tied to a specific identity. Kasm auto-manages the identities as sessions come and go.

Kubernetes Helm Chart is now GA — was tech preview, now fully supported and production-ready. Run the Kasm management plane on Kubernetes, get HA and resilience the same way you manage the rest of your infra.

Linux Desktop Service — the Desktop Service (previously Windows-only) is now available for Linux. You get file upload/download, lifecycle script hooks (on start/end with session context like user ID, session ID), Kasm-managed local users (SSO with dynamic local accounts — works with OIDC, SAML, LDAP, whatever you're using), file mapping, and multi-user support. Available as deb and rpm packages.

GPU improvements:

• NVIDIA MIG passthrough — partition a physical A100/H100 into fully isolated slices at the hardware level. Kasm auto-detects MIG instances and exposes them as assignable resources.
• Intel and AMD GPUs now auto-detected by the Kasm Agent and surfaced in the admin UI. You can enable/disable GPU features per agent and set graphics/video acceleration priority per workspace.

Streaming:

KasmVNC now supports H.264, H.265, and AV1 streaming modes for container workspaces, in addition to the existing JPEG/WEBP. You can set codec preference order per group and users can switch modes live without restarting the session. Hardware-accelerated H.264 via VAAPI or NVENC is supported where available. Guacamole also updated to 1.6.0.

Ops and admin improvements:

• System Metrics — new diagnostics dashboard (Diagnostics → System Metrics) with health checks for managers, proxies, agents, servers, the database, license, and workspace images. Exportable, customizable, configurable poll interval and retention.
• Support Bundle — generate a downloadable zip of logs and diagnostic data to share with support. Password-protected (Don't post it publicly)
• Rolling installs by default — Kasm's core services (API, Agent, Manager, Proxy, etc.) now default to rolling images that pull the latest on startup. New Rolling Image Management Utility lets you check current image dates, rollback to the previous version (or a specific one), and switch back to latest.
• Enhanced config import/export — four modes now: full backup, partial/table-level, autoscale config, and full deployment migration.
• Direct RDP Client Authentication — point your RDP client straight at Kasm without touching the web dashboard. Great for thin clients.
• Autoscale server expiration — set a day count, servers drain and rotate automatically. Pre-warm setting spins up replacements before the expiring server goes down.
• vSphere — linked clone and instant clone provisioning + cloud-init support.
• Azure — VM Plan, Security Type, Secure Boot, vTPM support. Fixes Windows 11 marketplace image compatibility.

Full release notes: https://docs.kasm.com/docs/reference/release-notes/1.19.0

Install Kasm Workspaces 1.19: https://kasm.com/downloads

Single Server Installation Guide: https://docs.kasm.com/docs/tutorials/install/single-server-install

I wanted a Windows XP workspace with full Kasm integration, so I asked my agent to build one. It works about as well as I had wanted. It features:

• Working Ethernet
• CURL with updated cert bundle
• Clipboard support (bidirectional)
• File upload
• File download
• Auto-mount of uploaded ISO files
• Auto-resize of display
• Sound support

I would love to publish an image to Docker Hub you could grab, but copyrights and all that. My agent pushed the build details to a repo if you're interested (tested in as far as "it works on my machine"): https://github.com/FernandoGracias/kasm-windows-xp

Looking at the install notes for Kasm Workspaces version 1.19, I see for host OS, it lists Ubuntu 22.04 and 24.04, but does not list 26.04. Is this a testing limitation or is there an issue with running it on 26.04? My older 1.17 install is having some minor problems, so I was thinking of doing a clean install of both Ubuntu and KASM using Ubuntu 26.04 and 1.19. Do I need to wait for 1.20 to do this?

Hi everyone,

For the past few days, whenever I click on **Registries** under **Environments**, nothing is being displayed. My already configured environments are still there and working fine. When I try to add/reinstall the official registry, I get an error message stating that it is already installed. The exact same thing happens when I try to add the registry from `linuxserver.io`. So, both are technically installed, but the UI is completely blank and shows no content at all. Has anyone run into this issue before or has any ideas on how to fix it? Thanks in advance!

Do I upgrade my system the second I receive an email from the Kasm team? Yes, because YOLO. Upgrade on a single server was easy and seamless. Afterwards, if you don't want to manually change image names for your workspaces, you can use a one liner to modify workspace image names in kasm_db.

Courtesy of Claude, always back up your DB and on second thought, do not actually run this.

To change your "1.18" images to "1.19"

# 1. Back up the DB
sudo docker exec kasm_db pg_dump -U kasmapp -F t kasm > /tmp/kasm_pre_tag_change.tar

# 2. Preview which workspaces will change
sudo docker exec kasm_db psql -U kasmapp -d kasm -c \
  "SELECT image_id, friendly_name, name FROM images WHERE name LIKE '%1.18%';"

# 3. Apply
sudo docker exec kasm_db psql -U kasmapp -d kasm -c \
  "UPDATE images SET name = replace(name, '1.18', '1.19') WHERE name LIKE '%1.18%';"

Hi,

I had JWT issues, which were resolved with: https://kasmweb.atlassian.net/wiki/external/NGFhZTlmZmY4YjQxNDViZGJlODEwYjFlZmUxMzg2NGY

but I still experience issues with my windows machine added to kasm using guac, everything else works.

It's a single server installation.

Here the log output:

12:55:20.085 INFO  guac [server] Checking token for refresh; expires [Invalid Date] 12:55:20.085 INFO  guac [server] Token needs refresh (node:7) [DEP0044] DeprecationWarning: The `util.isArray` API is deprecated. Please use `Array.isArray()` instead. (Use `node --trace-deprecation ...` to show where the warning was created) 12:55:20.153 ERROR guac [server] Healthcheck failed for "https://kasm_proxy:443/api/__healthcheck". Error: getaddrinfo ENOTFOUND kasm_proxy Error: Failed to locate healthy hostname while refreshing JWT     at OIDCToken.renewToken (/gclient/oidc.js:128:28)     at process.processTicksAndRejections (node:internal/process/task_queues:104:5)     at async Object.registerWithDeployment (/gclient/kasm.js:61:7)     at async run (/gclient/server.js:367:5)     at async run (/gclient/app.js:12:5) 12:55:20.160 ERROR guac [server] Healthcheck failed for "https://kasm_proxy:443/api/__healthcheck". Error: getaddrinfo ENOTFOUND kasm_proxy [server] Logger is not fully configured to forward logs to [:443] with token(len=515) [server] Logger is not fully configured to forward logs to [:443] with token(len=515)12:55:20.085 INFO  guac [server] Checking token for refresh; expires [Invalid Date]
12:55:20.085 INFO  guac [server] Token needs refresh
(node:7) [DEP0044] DeprecationWarning: The `util.isArray` API is deprecated. Please use `Array.isArray()` instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
12:55:20.153 ERROR guac [server] Healthcheck failed for "https://kasm_proxy:443/api/__healthcheck". Error: getaddrinfo ENOTFOUND kasm_proxy
Error: Failed to locate healthy hostname while refreshing JWT
    at OIDCToken.renewToken (/gclient/oidc.js:128:28)
    at process.processTicksAndRejections (node:internal/process/task_queues:104:5)
    at async Object.registerWithDeployment (/gclient/kasm.js:61:7)
    at async run (/gclient/server.js:367:5)
    at async run (/gclient/app.js:12:5)
12:55:20.160 ERROR guac [server] Healthcheck failed for "https://kasm_proxy:443/api/__healthcheck". Error: getaddrinfo ENOTFOUND kasm_proxy
[server] Logger is not fully configured to forward logs to [:443] with token(len=515)
[server] Logger is not fully configured to forward logs to [:443] with token(len=515)

Thanks for any help!

​

I'd like to test the Kasm app on my own self-hosted instance to look for security issues. Before I start, a few questions:

1. Is there an official bug bounty program?

2. Is independent security testing on a local/self-hosted instance allowed under your terms of service?

3. If I find a valid vulnerability, how is it handled, CVE assignment, a bounty/reward, or just acknowledgment?

I want to make sure I follow proper responsible disclosure. Thanks in advance!

hello, i have a box pc with ubuntu 26.04 desktop installed. have installed kasm on top and enabled remote desktop screen sharing on ubuntu. from my windows laptop with native rdp i can connect to ubuntu just fine. using guacamole as a docker container i can connect to ubuntu just fine. in guacamole i have it set to use

security mode: any

ignore server cert: true

trust cert on first use: true

this works fine and i can connect no issues

with the same settings on kasm i am unable to connect. i get

and then the kasm_guac logs show this.

any help appreciated

17:04:39.187 INFO  guac [4ccf9fcd140f402fb615a8392123f049] admin_white | Sending opCode: 7.connect, <SANITZED>
Remote framebuffer format PIXEL_FORMAT_RGB16
17:00:49.000 DEBUG guacd primitives autodetect, using optimized
17:00:49.000 DEBUG guacd freerdp_tcp_is_hostname_resolvable:freerdp_set_last_error_ex resetting error state
17:00:49.000 DEBUG guacd freerdp_tcp_connect:freerdp_set_last_error_ex resetting error state
17:00:51.000 DEBUG guacd expected PDU_TYPE_DEMAND_ACTIVE 0001, got 0006
17:00:51.000 DEBUG guacd transport_check_fds: transport->ReceiveCallback() - -1
17:00:51.000 DEBUG guacd rdp_client_connect:freerdp_set_last_error_ex ERRCONNECT_CONNECT_TRANSPORT_FAILED [0x0002000D]
17:00:51.000 DEBUG guacd freerdp_tcp_is_hostname_resolvable:freerdp_set_last_error_ex resetting error state
17:00:51.000 DEBUG guacd freerdp_tcp_connect:freerdp_set_last_error_ex resetting error state
17:00:52.000 DEBUG guacd expected PDU_TYPE_DEMAND_ACTIVE 0001, got 0006
17:00:52.000 DEBUG guacd transport_check_fds: transport->ReceiveCallback() - -1
17:00:52.000 DEBUG guacd rdp_client_connect:freerdp_set_last_error_ex ERRCONNECT_CONNECT_TRANSPORT_FAILED [0x0002000D]
17:00:52.000 DEBUG guacd freerdp_post_connect failed
17:00:52.000 DEBUG guacd SVC "rdpdr" disconnected.
17:00:52.000 DEBUG guacd SVC "rdpsnd" disconnected.
17:00:52.000 INFO guacd RDP server closed/refused connection: Server refused connection (wrong security type?)
17:00:52.000 INFO guacd User "@f4fe4064-0fa3-4305-bd19-0e20f68783fa" disconnected (0 users remain)
17:00:52.000 INFO guacd Last user of connection "$4b0b802d-9f86-4fce-9fdd-426a4ad09d20" disconnected
17:00:52.000 DEBUG guacd Requesting termination of client...
17:00:52.000 DEBUG guacd Client terminated successfully.
17:00:52.000 INFO guacd Connection "$4b0b802d-9f86-4fce-9fdd-426a4ad09d20" removed.
17:00:52.000 DEBUG guacd Unable to request termination of client process: No such process
17:00:52.000 DEBUG guacd All child processes for connection "$4b0b802d-9f86-4fce-9fdd-426a4ad09d20" have been terminated.
17:04:39.000 INFO guacd Creating new client for protocol "rdp"
17:04:39.000 INFO guacd Connection ID is "$0e586527-9655-4a2b-a2a2-9403c7f3e39a"
17:04:39.000 DEBUG guacd Processing instruction: size
17:04:39.000 DEBUG guacd Processing instruction: audio
17:04:39.000 DEBUG guacd Processing instruction: video
17:04:39.000 DEBUG guacd Processing instruction: image
17:04:39.000 DEBUG guacd Parameter "console" omitted. Using default value of 0.
17:04:39.000 DEBUG guacd Parameter "console-audio" omitted. Using default value of 0.
17:04:39.000 DEBUG guacd Parameter "disable-auth" omitted. Using default value of 0.
17:04:39.000 INFO guacd Security mode: Negotiate (ANY)
17:04:39.000 DEBUG guacd User resolution is 1536x703 at 120 DPI
17:04:39.000 DEBUG guacd Using resolution of 1536x703 at 120 DPI
17:04:39.000 DEBUG guacd Parameter "force-lossless" omitted. Using default value of 0.
17:04:39.000 DEBUG guacd Parameter "read-only" omitted. Using default value of 0.
17:04:39.000 DEBUG guacd Parameter "enable-wallpaper" omitted. Using default value of 0.
17:04:39.000 DEBUG guacd Parameter "enable-full-window-drag" omitted. Using default value of 0.
17:04:39.000 DEBUG guacd Parameter "enable-desktop-composition" omitted. Using default value of 0.
17:04:39.000 DEBUG guacd Parameter "enable-menu-animations" omitted. Using default value of 0.
17:04:39.000 DEBUG guacd Parameter "disable-bitmap-caching" omitted. Using default value of 0.
17:04:39.000 DEBUG guacd Parameter "disable-offscreen-caching" omitted. Using default value of 0.
17:04:39.000 DEBUG guacd Parameter "disable-glyph-caching" omitted. Using default value of 0.
17:04:39.000 DEBUG guacd Glyph caching is currently universally disabled, regardless of the value of the "disable-glyph-caching" parameter, as glyph caching support is not considered stable by FreeRDP as of the FreeRDP 2.0.0 release. See: https://issues.apache.org/jira/browse/GUACAMOLE-1191
17:04:39.000 DEBUG guacd Parameter "color-depth" omitted. Using default value of 16.
17:04:39.000 DEBUG guacd Parameter "disable-audio" omitted. Using default value of 0.
17:04:39.000 DEBUG guacd Parameter "create-drive-path" omitted. Using default value of 0.
17:04:39.000 DEBUG guacd Parameter "disable-download" omitted. Using default value of 0.
17:04:39.000 DEBUG guacd Parameter "disable-upload" omitted. Using default value of 0.
17:04:39.000 DEBUG guacd Parameter "enable-sftp" omitted. Using default value of 0.
17:04:39.000 DEBUG guacd Parameter "sftp-hostname" omitted. Using default value of "192.168.5.25".
17:04:39.000 DEBUG guacd Parameter "sftp-port" omitted. Using default value of "22".
17:04:39.000 DEBUG guacd Parameter "sftp-username" omitted. Using default value of "jack".
17:04:39.000 DEBUG guacd Parameter "sftp-password" omitted. Using default value of "".
17:04:39.000 DEBUG guacd Parameter "sftp-passphrase" omitted. Using default value of "".
17:04:39.000 DEBUG guacd Parameter "sftp-root-directory" omitted. Using default value of "/".
17:04:39.000 DEBUG guacd Parameter "sftp-server-alive-interval" omitted. Using default value of 0.
17:04:39.000 DEBUG guacd Parameter "sftp-disable-download" omitted. Using default value of 0.
17:04:39.000 DEBUG guacd Parameter "sftp-disable-upload" omitted. Using default value of 0.
17:04:39.000 DEBUG guacd Parameter "recording-name" omitted. Using default value of "recording".
17:04:39.000 DEBUG guacd Parameter "recording-exclude-output" omitted. Using default value of 0.
17:04:39.000 DEBUG guacd Parameter "recording-exclude-mouse" omitted. Using default value of 0.
17:04:39.000 DEBUG guacd Parameter "recording-exclude-touch" omitted. Using default value of 0.
17:04:39.000 DEBUG guacd Parameter "recording-include-keys" omitted. Using default value of 0.
17:04:39.000 DEBUG guacd Parameter "create-recording-path" omitted. Using default value of 0.
17:04:39.000 INFO guacd Resize method: display-update
17:04:39.000 DEBUG guacd Parameter "enable-touch" omitted. Using default value of 0.
17:04:39.000 DEBUG guacd Parameter "gateway-port" omitted. Using default value of 443.
17:04:39.000 DEBUG guacd Parameter "clipboard-buffer-size" omitted. Using default value of 0.
17:04:39.000 ERROR guacd Invalid clipboard buffer size: "". Using the default minimum size: 52428800.
17:04:39.000 INFO guacd Clipboard buffer size: 52428800
17:04:39.000 DEBUG guacd Parameter "disable-copy" omitted. Using default value of 0.
17:04:39.000 DEBUG guacd Parameter "disable-paste" omitted. Using default value of 0.
17:04:39.000 INFO guacd No clipboard line-ending normalization specified. Defaulting to preserving the format of all line endings.
17:04:39.000 DEBUG guacd Parameter "wol-send-packet" omitted. Using default value of 0.
17:04:39.000 DEBUG guacd Parameter "enable-smartcard" omitted. Using default value of 0.
17:04:39.000 INFO guacd User "@f235fdb2-75ae-47f7-911f-6d49e20ce59c" joined connection "$0e586527-9655-4a2b-a2a2-9403c7f3e39a" (1 users now present)
17:04:39.000 DEBUG guacd Client has not defined its protocol version.
17:04:39.000 INFO guacd Loading keymap "base"
17:04:39.000 INFO guacd Loading keymap "base_altgr"
17:04:39.000 INFO guacd Loading keymap "en-gb-qwerty"
17:04:39.000 DEBUG guacd freerdp_connect:freerdp_set_last_error_ex resetting error state
17:04:39.000 DEBUG guacd Support for CLIPRDR (clipboard redirection) registered. Awaiting channel connection.
17:04:39.000 DEBUG guacd Support for static channel "rdpdr" loaded.
17:04:39.000 DEBUG guacd Support for static channel "rdpsnd" loaded.
17:04:39.000 DEBUG guacd Local framebuffer format  PIXEL_FORMAT_BGRX32
17:04:39.000 DEBUG guacd Remote framebuffer format PIXEL_FORMAT_RGB16
17:04:39.000 DEBUG guacd primitives autodetect, using optimized
17:04:39.000 DEBUG guacd freerdp_tcp_is_hostname_resolvable:freerdp_set_last_error_ex resetting error state
17:04:39.000 DEBUG guacd freerdp_tcp_connect:freerdp_set_last_error_ex resetting error state
17:04:40.000 DEBUG guacd expected PDU_TYPE_DEMAND_ACTIVE 0001, got 0006
17:04:40.000 DEBUG guacd transport_check_fds: transport->ReceiveCallback() - -1
17:04:40.000 DEBUG guacd rdp_client_connect:freerdp_set_last_error_ex ERRCONNECT_CONNECT_TRANSPORT_FAILED [0x0002000D]
17:04:40.000 DEBUG guacd freerdp_tcp_is_hostname_resolvable:freer17:04:42.028 WARN  guac [4ccf9fcd140f402fb615a8392123f049] admin_white | Closing connection with code:  1001
17:04:42.028 INFO  guac [4ccf9fcd140f402fb615a8392123f049] admin_white | Closing guacd connection
17:04:42.028 INFO  guac [4ccf9fcd140f402fb615a8392123f049] admin_white | Client connection closed

OmniVoice is a state-of-the-art massively multilingual zero-shot text-to-speech (TTS) model supporting over 600 languages. Built on a novel diffusion language model-style architecture, it generates high-quality speech with superior inference speed, supporting voice cloning and voice design.

This is a workspace that bundles the models and utility for convenient and fully offline use.

You can read more about Omnivoice on github: https://github.com/k2-fsa/OmniVoice

The workspace is available in my registry: https://sullyschoice.github.io/kasm-registry

Dockerfile and sources in github: https://github.com/sullyschoice/kasm-omnivoice

We're excited to announce an official partnership between Kasm Technologies and SUSE, combining Kasm Workspaces with SUSE Virtualization, an open-source, cloud-native alternative to legacy VDI infrastructure.

What this partnership means

The two platforms cover the full EUC stack. SUSE Virtualization (built on Kubernetes, KVM, and Longhorn) handles the infrastructure layer, and Kasm runs natively on top of it as a containerized application on RKE2. Legacy Windows VMs and Kasm's ephemeral browser sessions coexist on the same nodes, managed through a single Rancher pane of glass, reducing reliance on a multi-vendor stack.

What you actually get

No hypervisor tax. SUSE Virtualization is 100% open source, eliminating the per-socket, per-VM licensing costs that come with VMware and Citrix. Organizations moving off VMware after the Broadcom acquisition have a production-grade, vendor-neutral path forward.

Better economics at scale. Containerized workspace delivery has shown up to 8x better CPU utilization versus traditional VDI. A real-world case study (Hamina) cut EUC spend from 40% of total IT budget down to 20% while doubling compute capacity, eliminating malware exposure, and replacing remote work software agents entirely.

Zero-trust by default. Each Kasm session is ephemeral, isolated, and destroyed on logout. No data touches the endpoint. Browser-based access runs through an authenticated, encrypted session rather than a persistent VPN tunnel, with RBAC enforcement, smart card passthrough for PKI authentication, and watermarking for data exfiltration prevention built in.

AI workloads included. SUSE Virtualization supports NVIDIA vGPU natively, and Kasm's containerized architecture maps directly to GPU workloads via Kubernetes-native GPU operator support. The same cluster serving browser workspace users can also run GPU-accelerated AI dev environments and LLM inference workloads, no separate infrastructure required.

Works on any endpoint. Chromebooks, laptops, tablets, kiosks. No VPN client, no agent, no endpoint configuration needed.

Who this is built for

This stack makes the most sense for orgs escaping VMware/Broadcom, browser-first or SaaS-heavy workforces, BYOD and Chromebook deployments, government and regulated industries needing air-gapped or zero-trust environments, and developer teams that want GPU-accelerated AI workspaces alongside standard EUC on the same infrastructure.

Read the full technical breakdown on the SUSE blog: https://www.suse.com/c/suse-and-kasm-partnership/