寻求开源方案：服务器向瘦客户机提供VM并支持PXE启动

Hey there! Let's break down the best open-source solutions tailored to your setup—high-performance server, 2 thin clients, and PXE-booted VM/streamed sessions:

1. Proxmox VE + iPXE #

Proxmox is a rock-solid open-source hypervisor (built on KVM/LXC) that’s perfect for managing VMs for your thin clients. Here’s how to tie it to PXE:

• First, spin up your desired VMs on Proxmox—install the OS, set up SPICE/VNC (both open-source remote display protocols), and enable qemu-guest-agent for tighter integration.
• Set up an iPXE server (use dnsmasq or tftp-hpa on your Proxmox host or a separate machine) to serve the iPXE boot script.
• Write a simple iPXE script that directs the thin client to connect directly to the Proxmox VM’s SPICE/VNC endpoint, or boot a lightweight iPXE client that initiates a VM console session.
• Why this works: Proxmox has an intuitive web UI for managing VMs, supports snapshots/cloning (great for duplicating setups for your two clients), and plays seamlessly with open-source remote display tools.

2. LTSP (Linux Terminal Server Project) #

LTSP is purpose-built for thin client deployments and 100% open-source. It’s ideal if you want either shared desktop sessions or dedicated VMs per client:

• Install LTSP on your server—it comes with built-in PXE server tools, so you won’t need a separate TFTP/DHCP server (you can also integrate with your existing network’s DHCP if preferred).
• Choose between two modes:
  • Terminal mode: Thin clients boot via PXE and connect to a shared or dedicated X11 desktop session on the server (low bandwidth usage, perfect for basic tasks).
  • VM mode: Configure LTSP to spin up a dedicated KVM VM for each thin client, with the client booting directly into that VM via PXE.
• Why this works: LTSP is streamlined for thin client use cases, requires minimal configuration compared to full hypervisor stacks, and supports all major Linux desktop environments.

3. Xen Orchestra + iPXE #

If you prefer Xen as your hypervisor (another powerful open-source option), Xen Orchestra is the open-source management layer that simplifies tying into PXE:

• Set up Xen on your server, create your VMs, and configure Xen’s built-in VNC/SPICE access for each VM.
• Deploy an iPXE server (again, dnsmasq or tftp-hpa works) with a script that directs thin clients to boot into the Xen VM’s remote console.
• Xen Orchestra gives you a web UI to manage VM lifecycle, resource allocation, and performance monitoring—great for keeping your two clients running smoothly.

4. OpenStack (For Future Scaling) #

If you think you might add more thin clients down the line, OpenStack is a full open-source cloud platform that supports PXE-booted instances:

• Set up the OpenStack Compute (Nova) and Bare Metal (Ironic) services to manage VMs for your thin clients.
• Configure PXE boot via OpenStack’s integrated services, which handle DHCP/TFTP automatically.
• Note: This has a steeper learning curve, so it’s overkill for just two clients, but it’s worth keeping in mind if you plan to scale up.

Quick Setup Tips #

• Make sure your thin clients have PXE boot enabled in their BIOS/UEFI settings.
• Ensure your server (or PXE server) is on the same network as the thin clients, or configure your network’s DHCP server to point clients to the PXE TFTP server.
• For better performance, use a wired network connection between server and thin clients—wireless can introduce latency for VM streaming.

内容的提问来源于stack exchange，提问作者KHaemels