Skip to content

Virtualization Platform Comparison

OpenIDCS supports 7 mainstream virtualization / container platforms. This page helps you pick the right one for your scenario.

🧭 One-Liner Recommendation

GoalRecommended Platform
🐳 Deploy web / microservices / CI environments, fastest startupDocker / Podman
📦 Run full Linux distros without VM overheadLXC / LXD
🖥️ Desktop-level dev/test, need Windows / custom ISOVMware Workstation
🏢 Enterprise production, need HA / cluster / storage migrationProxmox VE / VMware ESXi
🪟 Pure Windows Server environment, no 3rd-party componentsWindows Hyper-V
☁️ Integrate existing Qingzhou / QingCloud resourcesQingzhou

📋 Capability Matrix

Basic Capabilities

PlatformTypeOverheadBoot SpeedSupported OS
Docker / PodmanApp containerVery LowSecondsLinux (inside container)
LXC / LXDSystem containerVery LowSecondsLinux
VMware WorkstationType-2 HypervisorMedium10–30sAll OS
VMware ESXiType-1 HypervisorLow10–30sAll OS
Proxmox VEKVM + LXCLow5–20sAll OS
Windows Hyper-VType-1 HypervisorLow10–30sAll OS
QingzhouPublic Cloud API--All OS

Feature Support Matrix

Based on actual adapters in OpenIDCS HostServer:

FeatureDocker/OCILXC/LXDVMware WSProxmoxHyper-VESXiQingzhou
VM Lifecycle
Change Password VMPasswd✅*✅*
Screenshot VMScreen
Backup / Restore
List / Delete Backup⚠️
Disk Mount / Unmount
ISO Mount
Disk Check
Disk Migration
PCI Passthrough
USB Passthrough
VNC Console
Web Terminal (ttyd)

Note: * means changed via agent / external method; ⚠️ means partially supported.

Isolation Strength

Docker/Podman  ───────────●─────────────────→ Light (shared kernel)
LXC/LXD        ────────────●────────────────→ Medium (shared kernel + cgroup)
Hyper-V/ESXi   ────────────────────●────────→ Strong (hardware virtualization)
VMware WS/PVE  ────────────────────●────────→ Strong (hardware virtualization)
Qingzhou       ────────────────────────●────→ Multi-tenant isolation

🎯 Typical Scenarios

Scenario 1: SMB IT, Hybrid Environment

Recommended: Docker (container services) + Proxmox (core VMs)

mermaid
graph LR
    OIDCS[OpenIDCS]
    OIDCS --> D[Docker: Web/API]
    OIDCS --> P[Proxmox: Core VMs]
    OIDCS --> D2[LXC: Dev Envs]

Scenario 2: IDC Transitioning to Virtualization Sales

Recommended: Proxmox + LXD

  • Proxmox for KVM VMs (sold to users needing full Linux / Windows)
  • LXD for container plans (cheaper, higher density)
  • OpenIDCS integrates with zjmf billing for automatic provisioning / suspend / renewal

Scenario 3: R&D / Education

Recommended: VMware Workstation (local) or LXC / LXD (lightweight)

  • Workstation: students can snapshot/rollback anytime, run Windows labs
  • LXC: 3–5x higher density on the same hardware

Scenario 4: Pure Windows Server

Recommended: Hyper-V

  • No 3rd-party hypervisor needed
  • Deeply integrated with AD / WinRM / PowerShell
  • OpenIDCS manages it via PS scripts

🏗️ Architecture Differences

Idle Resource Footprint

PlatformMemoryCPUDisk
Docker Engine~100 MB<1%~500 MB
LXD~150 MB<1%~300 MB
VMware Workstation~400 MB1–3%~2 GB
Proxmox VE~800 MB1–3%~4 GB
Hyper-V~500 MB1–2%~3 GB
ESXi~1.5 GB2–5%Dedicated

Management Protocols

PlatformProtocolPortAuth
Docker / PodmanHTTPS (REST)2376Mutual TLS
LXC / LXDHTTPS (REST)8443Mutual TLS
VMware WorkstationHTTPS (REST)8697Basic Auth
Proxmox VEHTTPS (REST)8006Token / PAM
Hyper-VWinRM (PS)5985/5986NTLM / Kerberos
ESXiHTTPS (SOAP)443vSphere account
QingzhouHTTPS (REST)443AccessKey

📖 Detailed Configuration Docs

Next

Released under the AGPLv3 License.