Products › Proxmox
Proxmox Integration
Browser-based VM access, agentless per-VM RDP, and host boot observability — all integrated with Proxmox VE
What “Proxmox integration” means here
Proxmox VE is a popular open-source virtualization platform — KVM/QEMU virtual machines and LXC containers managed through a web UI. Its built-in console support is good for most Linux VMs (noVNC, SPICE), but it has real gaps: no first-class RDP experience for Windows VMs, no access when a guest has no agent, no visibility into the PVE host’s own boot health beyond what the dashboard shows.
Lamco’s Proxmox focus area fills those gaps with three products that cover different access and observability layers:
- Inside the PVE web UI — a native RDP console that replaces the noVNC experience for RDP-capable VMs (
lamco-rdp-console). - On the PVE host, per VM — an agentless RDP server that captures any VM’s framebuffer from outside the guest, including pre-boot (
lamco-qemu-rdp). - On the PVE host, system level — boot-time telemetry and SMART/health reporting surfaced back into the PVE dashboard (
LamBoot, in development).
These are a peer set, not a hierarchy. They solve different problems; most PVE deployments will want more than one.
Default PVE console vs. Lamco RDP Console
For RDP-capable VMs — Windows, xrdp, or lamco-qemu-rdp endpoints — the difference at the operator’s seat is substantial.
Default: noVNC in the PVE UI
- — VNC over WebSockets — single-codec, low-efficiency bitmap
- — Text rendering blurs at common resolutions; scaling is approximate
- — Clipboard is text-only, unreliable under Windows guests
- — No audio channel
- — High CPU on both host and operator browser at full framerate
- — No file transfer
With lamco-rdp-console
- — H.264 graphics; high-framerate motion without CPU burn
- — Crystal-clear text via AVC444 / multi-codec routing
- — Bidirectional clipboard with file transfer (MS-RDPECLIP)
- — Audio over RDP (OPUS / PCM)
- — Hardware-accelerated decode in the browser via WebCodecs
- — Runs entirely in the PVE UI — no desktop RDP client needed
Where each product sits
Operator's browser
│
▼
┌─────────────────────────────────────────────────────────────────┐
│ Proxmox VE Web UI │
│ ┌───────────────────────┐ │
│ │ lamco-rdp-console │ ← native RDP console (IronRDP/WASM) │
│ │ (ExtJS overlay via │ replaces noVNC for RDP-capable VMs│
│ │ lamco-pve-rdp) │ │
│ └───────────┬───────────┘ │
└──────────────┼──────────────────────────────────────────────────┘
│ RDP
▼
┌─────────────────────────────────────────────────────────────────┐
│ PVE Host (Linux) │
│ │
│ ┌─────────────────────┐ ┌────────────────────────┐ │
│ │ QEMU / KVM VM │ │ LamBoot (host) │ │
│ │ │ │ │ │
│ │ ┌───────────────┐ │◄───────►│ boot telemetry │ │
│ │ │ lamco-qemu- │ │ D-Bus │ SMART reporting │ │
│ │ │ rdp (per-VM) │ │ display │ disk health │ │
│ │ │ │ │ │ │ │
│ │ │ agentless, │ │ │ → surfaced back to │ │
│ │ │ pre-boot ok │ │ │ the PVE dashboard │ │
│ │ └───────────────┘ │ └────────────────────────┘ │
│ └─────────────────────┘ │
└─────────────────────────────────────────────────────────────────┘
lamco-pve-rdp is the AGPL-compatible ExtJS overlay + hookscripts that wire lamco-rdp-console into the PVE UI. It’s the integration glue, not a standalone product surface.
Three distinct products
Each solves a specific problem. “This is X, not Y” framing so the lines stay clear.
lamco-rdp-console
COMING SOONNative RDP console inside the PVE web UI
What it is
An RDP client that runs in the operator’s browser, inside the PVE web UI. Built on IronRDP compiled to WebAssembly. H.264 graphics, clipboard, audio, no plugins, no desktop client required.
What it is not
Not an RDP server; the VM still needs an RDP server running inside it (Windows built-in, xrdp on Linux, or lamco-qemu-rdp externally). This product is the console viewing that server from the PVE UI.
Use when:
You run Windows (or any RDP-capable) VMs on Proxmox and want the console experience inside the PVE web UI to actually feel like RDP — smooth H.264 framerates, working clipboard, audio — instead of the noVNC fallback.
lamco-qemu-rdp
COMING SOONPer-VM host-side RDP server for QEMU/KVM
What it is
An RDP server that runs on the host, one instance per VM, capturing the guest’s framebuffer via QEMU’s D-Bus display protocol. No agent inside the guest. Works during BIOS, bootloader, kernel panics — any state where the guest can render pixels.
What it is not
Not a replacement for Windows’ built-in RDP server when the guest is healthy and the guest-side server works fine — that path has lower overhead. This is for situations where the guest-side path isn’t available or isn’t trustworthy.
Use when:
You need RDP access to Linux VMs without xrdp, to appliance VMs with no agent, to VMs during boot or recovery, or to any VM where the guest-side story isn’t working. Also useful for testing and automation workflows that need deterministic access from outside the guest.
LamBoot
IN DEVELOPMENTHost boot-time observability surfaced to the PVE dashboard
What it is
A standalone Linux-native boot and health tool. Runs on the PVE host. Captures boot-time telemetry, SMART reports, disk health, and startup performance. For Proxmox deployments, surfaces that data back into the PVE dashboard as first-class panels.
What it is not
Not a Proxmox-only product. LamBoot stands on its own as a general Linux boot-health tool. Its PVE surface is one integration among several; listing it here is a cross-reference, not subsumption.
Use when:
You operate Proxmox hosts and want visibility into what the PVE dashboard doesn’t natively show — pre-systemd boot timing, SMART trend data, storage health patterns — without leaving the PVE UI to go check logs and tools on each host.
Canonical product page arriving when the repo goes public.
Which product should I use?
| If your goal is… | Use | Because |
|---|---|---|
| Access a Windows VM’s desktop through the PVE web UI | lamco-rdp-console | Replaces noVNC with real RDP in the browser; the guest already has an RDP server built in |
| Access a Linux VM that has no xrdp or RDP-capable server | lamco-qemu-rdp | Host-side capture; works regardless of what’s running in the guest |
| Watch a VM boot through BIOS / GRUB / initramfs | lamco-qemu-rdp | Host-side capture doesn’t depend on the guest kernel being up |
| Debug a kernel panic or recovery-mode VM | lamco-qemu-rdp | Same reason — no agent required inside the broken guest |
| Both of the above through one PVE-UI experience | console + qemu-rdp | qemu-rdp publishes a guest-agnostic RDP endpoint; console consumes it from the PVE UI |
| Monitor PVE host boot health and SMART trends | LamBoot | Host-level observability; not a VM-access story at all |
| Automate RDP test workflows against Proxmox VMs | lamco-rdp-tools | General-purpose RDP automation CLI; useful alongside Proxmox work but not specifically a Proxmox product |
Related pieces that aren’t anchors
lamco-pve-rdp
PVE integration glue
The AGPL-compatible ExtJS overlay + PVE hookscripts that wire lamco-rdp-console into the Proxmox UI. Integration code, not a standalone product surface — no separate page.
lamco-rdp-tools ↑
General-purpose RDP automation
A CLI toolkit for automating RDP sessions. Its canonical home is the RDP focus area; mentioned here because it’s a common companion tool for Proxmox VM testing.