VM memory is the clearest scaling limit. A 16 GB host can run several light Linux appliances or fewer heavier Windows guests, but actual count depends on each guest's memory need and other host services.
Homelab users adding more simultaneously running VMs.Hardwareanforderungen für den Virtual Machine Manager: CPU, RAM und VM-Speicher
Erfahren Sie mehr über die Anforderungen des ZimaOS Virtual Machine Managers an CPU, RAM, KVM, Speicher und VM-Zuweisung und wählen Sie anschließend die passende Hardware für Linux- und Windows-VMs aus.
Virtual Machine Manager requirements at a glance
ZimaOS Virtual Machine Manager is a GTK Broadway Web UI for libvirt and virt-manager. virt-manager is only the management interface; the actual guests run through the host's virtualization stack such as KVM/QEMU. There is therefore no meaningful fixed VMM RAM minimum—the host must cover ZimaOS plus the RAM, vCPU, storage and device needs of every VM running concurrently.
- CPU virtualization
- KVM-accelerated x86 virtualization requires a compatible host virtualization path. Validate KVM/libvirt on the host before planning guests.
- Host RAM
- No universal VMM minimum. Leave RAM for ZimaOS/libvirt/QEMU plus all simultaneously running guests. Guest-assigned memory is the dominant requirement.
- CPU cores
- vCPUs can be allocated and overcommitted, but four physical cores do not become unlimited compute. More simultaneous CPU-busy VMs increase scheduling contention.
- Storage
- VM virtual disks are latency-sensitive and can grow quickly. SSD/NVMe is strongly preferable for interactive Windows/Linux VMs; bulk HDD capacity is better suited to colder images and backups.
- GPU / passthrough
- Not required for ordinary VMs. PCIe/GPU passthrough is an advanced workload that also depends on IOMMU groups, device isolation, drivers and host configuration.
- Best Zima starting point
- ZimaBoard 2 1664 is the better compact VM host because 16 GB RAM provides materially more guest headroom than 8 GB. ZimaCube 2 Pro is the stronger current stock choice for multiple VMs and VM storage.
From official requirements to the right setup
Virtual Machine Manager hardware planning starts with guest requirements and concurrency.
-
Official requirements
List every guest OS you expect to run at the same time and its minimum/practical vCPU, RAM and disk needs. Windows desktop/server guests usually need more resources than lightweight Linux appliances.
-
Confirm your needs
Reserve host headroom. Do not allocate 100% of physical RAM to guests; ZimaOS, libvirt/QEMU, filesystem cache and other applications still need memory.
-
Leave room to grow
Place active VM disks on SSD/NVMe. VM latency is often dominated by random disk I/O, and homelab troubleshooting repeatedly shows that slow VM storage can make a strong CPU feel weak.
-
Run it on ZimaOS
Open Virtual Machine Manager in ZimaOS, create one representative VM, measure host CPU/RAM/disk latency, then add guests incrementally instead of assuming a fixed VM-per-core ratio.
Check every playback client
- Guest operating systems
- Number of simultaneously running VMs
- Per-VM RAM
- Per-VM vCPU allocation
- SSD/NVMe VM-disk capacity
- Windows 11/TPM/UEFI needs
- USB/PCIe/GPU passthrough requirements
- Other ZimaOS apps running beside VMs
Official minimum requirements
virt-manager and libvirt do not publish a single host CPU/RAM minimum because virt-manager manages virtual hardware allocations; the guest workloads define the host capacity requirement.
Treat VMM as a control interface over KVM/QEMU/libvirt. Hardware acceleration and enough host resources for each guest are the real requirements; software emulation or severe RAM overcommit can make a VM technically start but practically unusable.
| Requirement | Official minimum | What this supports |
|---|---|---|
| VMM UI CPU/RAM | No universal numerical minimum | virt-manager is the management interface; guest QEMU/KVM workloads dominate resource use. |
| Hypervisor | Primarily KVM via libvirt on Linux | virt-manager also supports other libvirt-backed virtualization technologies. |
| Guest RAM | Allocated per VM | Total concurrently assigned/actively used guest memory plus host overhead determines host RAM needs. |
| Guest vCPU | Allocated per VM | vCPU overcommit is possible, but CPU-busy VMs still contend for physical cores. |
| VM storage | Workload-defined | Guest OS disks, snapshots and ISOs can consume much more space than the VMM application. |
| GPU | Not required for ordinary VM management | Passthrough is optional and must be validated separately. |
When to upgrade your hardware
Upgrade a VM host when guests compete for RAM, CPU time or storage latency.
Host RAM limits how many useful VMs can run together
Multiple CPU-busy guests contend on a 4-core host
VM disks become the responsiveness bottleneck
KVM can schedule many vCPUs on fewer physical cores, but overcommit does not create extra compute. Compile jobs, Windows updates and other sustained guest work can make a 4-core host feel congested.
Development labs and multi-VM test environments.Random I/O, snapshots and several guests hitting one slow drive can dominate perceived VM performance. Moving active VM disks to SSD/NVMe can be a larger upgrade than adding vCPUs.
Windows VMs, development desktops and multi-guest servers.Plan hardware growth with confidence
Scale virtualization by adding RAM and fast VM storage before buying GPU hardware.
Move from 8 GB to 16 GB for a serious compact VM host
8 GB can support one/light guests, but 16 GB provides far more useful room after reserving ZimaOS host memory.
ZimaBoard 2 1664 is the more sensible compact virtualization starting point.Use SSD/NVMe for active guest disks
QEMU virtual disks generate normal OS-style random reads/writes. Fast local SSD/NVMe improves boot, updates and application latency.
Keep large inactive images/backups on HDD if needed.Use Core-class CPU for more simultaneous active VMs
More/larger VMs create CPU scheduling pressure. ZimaCube 2 Pro's Core i5 provides a stronger virtualization CPU base than the 4-core N150.
Choose Pro when multiple guests will be active rather than mostly idle.Treat GPU passthrough as an advanced separate requirement
A GPU in the box does not guarantee successful passthrough. IOMMU, PCIe topology, device reset, drivers and host access all matter.
Creator Pack is conditional for large-memory labs or verified GPU-passthrough/AI VM workflows, not a default VMM recommendation.Can it run on ZimaOS?
ZimaOS currently lists Virtual Machine Manager as a GTK Broadway Web UI for libvirt and virt-manager; ZimaOS also includes its own ZVM virtualization support.
Use Virtual Machine Manager as a libvirt/virt-manager UI
The App Store description identifies this package as a web UI for libvirt and virt-manager, so guest hardware requirements remain QEMU/KVM/libvirt requirements.
Open Virtual Machine Manager in the ZimaOS App StoreRemember ZimaOS already has native ZVM support
ZimaOS 1.3 introduced one-click Windows/Linux ZVM virtual machines. Choose the manager/interface that fits the workflow rather than assuming the App Store UI is the hypervisor itself.
Read ZimaOS ZVM release notesValidate libvirt/QEMU capabilities before advanced passthrough
libvirt exposes host/domain capabilities for KVM, CPU modes and device assignment. Use those capabilities instead of assuming every PCIe/USB/GPU can be passed through.
Read libvirt QEMU/KVM driver documentationChoose Zima hardware for Virtual Machine Manager
Virtualization is one of the few workloads where system RAM, CPU cores and SSD capacity all scale directly with what you plan to run.
Are you running one/light lab VMs or multiple active Windows/Linux guests?
One or a few lightweight VMs
A compact 16 GB host provides useful guest memory while retaining ZimaOS headroom.
- Compact VM labZimaBoard 2 1664
Multiple active or heavier VMs
Use stronger CPU, 16 GB RAM and larger/faster VM storage.
- Stronger stock multi-VM hostZimaCube 2 Pro
No fixed number of VMs is guaranteed. Linux vs Windows, idle vs busy guests, memory ballooning/overcommit, disk workload, snapshots and passthrough can radically change host capacity.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 1664 | A compact homelab with one or a few lightweight Linux/Windows VMs. | 16 GB shared between ZimaOS and guest memory, with SATA/PCIe storage expansion. |
|
The 4-core N150 can become CPU-bound when several guests are simultaneously busy; use SSD/NVMe for guest disks. | Get Now |
| ZimaCube 2 Pro | A stronger stock Zima host for multiple active VMs. | Core i5 CPU, 16 GB RAM and integrated storage/10GbE options for a larger VM lab. |
|
16 GB RAM still limits total guest memory; large Windows labs may reach RAM before CPU. | Get Now |
| ZimaCube 2 Creator Pack | A conditional large-memory virtualization lab or VM workload that genuinely needs a dedicated GPU. | 64 GB host RAM allows substantially more guest-memory allocation; RTX hardware may be useful for verified passthrough/AI/creator VMs. |
|
Do not buy it solely for the virt-manager UI. GPU passthrough is not guaranteed and depends on IOMMU/device topology and ZimaOS/libvirt configuration. | Get Now |
What the Press Says
Highlights from trusted reviewers worldwide.
“ZimaCube 2: Not just another NAS, tested with 25TB storage, local AI agents, 4K transcoding, and real homelab workflows.”Read full review
“The ZimaBoard 2 is a compact x86 server board that can be turned into a mini NAS, home server, media box, or self-hosting hub.”Read full review
“ZimaCube 2: A modern, high-performance NAS with plenty of room to grow—built for users who want more than basic storage.”Read full review
“Coverage focused on ZimaCube 2's open hardware foundation, no monthly fee, and self-hosting flexibility.”Read full review
Loved by the Community
Stories and reviews from people who build with Zima every day.
★★★★★
Zima Blade Little yet Powerful
Maybe I am not digital natives but I live with PCs since 12 years old in 1984 when IBM PC clone come to my home. Many years have passed and many operating system I've tried. For me Zima blade and CasaOS was a quantum leap for home PC enthusiast and server lab machine to make me stay curious and relevant for this era.
★★★★★
Very good!!
I use ZimaCube Pro as 5th Proxmox cluster node. It runs several VMs and containers, including a VM with GPU passthrough to run a self-hosted LLM. A specific LXC container runs a Samba server for NAS capabilities using four of six RAID 6 SATA HDDs with ZFS.
★★★★★
Great innovation for mini server!
It is very useful and makes a powerful mini server for many purposes, including university and college students in engineering and electronics. Thank you so much for making this server.
★★★★★
Avaliação ZimaBoard 2
Construí um servidor de uso pessoal. O desempenho está muito bom e funciona perfeitamente onde quer que eu esteja. A surpresa é não dependermos de grandes estruturas para termos nosso próprio servidor de dados. Como iniciante, estou gostando bastante do ZimaOS, pois ele é simples e eficiente.
Frequently asked questions
FAQ topics follow query fan-out around VM count, host RAM, vCPU overcommit, SSD performance and passthrough. Homelab Reddit discussions are used to reflect real allocation questions, while virt-manager/libvirt/QEMU define the architecture.
How much RAM does Virtual Machine Manager itself need?
There is no useful fixed number. virt-manager is only the management UI. The real RAM requirement is ZimaOS/libvirt/QEMU overhead plus the memory assigned to every guest running at the same time.
How many VMs can a 4-core host run?
There is no fixed VM-per-core ratio. Several mostly idle Linux guests can coexist on four cores, while two or three CPU-heavy guests can already contend badly. Allocated vCPUs are not the same thing as extra physical compute.
Is 8 GB RAM enough for a VM host?
It can be enough for one light VM or a small lab, but the host OS must retain memory too. For a more useful ZimaOS virtualization host, 16 GB provides much better guest headroom.
Can I allocate more vCPUs than the host has physical cores?
Yes, CPU overcommit is normal in virtualization, but it does not create extra compute. If several overcommitted guests become busy together, latency and throughput suffer.
Why can a Windows VM feel slow even when CPU usage is low?
VM disk latency, insufficient guest RAM, storage contention and virtual-device configuration can dominate responsiveness. Homelab troubleshooting frequently finds SSD placement or storage configuration to be the real problem.
Should VM disks be on SSD or HDD?
Use SSD/NVMe for active interactive VM disks whenever possible. HDDs are better suited to large inactive images, backups or workloads that are not latency-sensitive.
Can ZimaBoard 2 1664 run Windows and Linux VMs?
Yes. Its 4-core N150, 16 GB RAM and storage expansion make it a useful compact lab host. The number and responsiveness of guests still depend on per-VM allocations and disk placement.
Do I need ZimaCube 2 Creator Pack for GPU passthrough?
Only if a guest genuinely needs a dedicated GPU or you need the 64 GB host RAM. The presence of an RTX GPU does not guarantee passthrough; IOMMU groups, PCIe topology, drivers and libvirt/ZimaOS configuration must all work.
What sources and further reading informed this Virtual Machine Manager hardware guide?
The ZimaOS App Store identifies the package as a GTK Broadway UI for libvirt/virt-manager, while virt-manager and libvirt establish that the application manages KVM/QEMU guest resources rather than defining a fixed host minimum. ZimaOS release notes document native ZVM support. Reddit homelab discussions were used for fan-out around 4-core/16-GB VM counts and resource overcommit, not as performance guarantees.
