VOL with no virtualization layer · physical-machine performance · image and configuration separated · native Linux support
Third-generation IDV (IDV3) runs the desktop locally on the endpoint with central management; vDisk goes further, removing the virtualization layer for physical-machine performance, separating image and configuration so one image manages multi-brand mixed endpoints, and supporting Linux natively. It's the upgrade to IDV3.
IDV3 already delivers "local compute + central management." vDisk keeps those strengths while fixing third-generation IDV's common weaknesses: performance overhead, mixed endpoints, Linux support, and mobile operations.
| Dimension | IDV3 (third-generation IDV) | vDisk (the next generation surpassing IDV3) |
|---|---|---|
| Local computing / network offline | Desktop runs locally on the endpoint | Same local computing power,Works Offline |
| Performance | The endpoint still has virtualization layer overhead, struggling with large software. | VOL removes the virtualization layer, performance equals that of a physical machine |
| Image / endpoint | Heavy reliance on the same model image makes it difficult to unify heterogeneous endpoints | Image-Config Separation, single image manages multiple brands such as Dell, Lenovo, and HP |
| Linux | Depends on product compatibility | ARM64 × Linux image packaging, native Linux |
| Data / Restore | Restore capability depends on plan | Three-tier Storage + One-Click Restore, student data is retained independently |
| Operations & Maintenance | Console-oriented | Console + Mobile O&M via WeChat Mini Program |
| Legacy Devices | View endpoint requirements | Can reuse old PCs, extending service life and cutting costs |
Eliminates hypervisor overhead; the operating system runs directly on the physical hardware of the endpoint. Even large software like 3D modeling and video editing can be handled, with performance equivalent to a physical machine.
Base image is read-only and shared, configurations are independently distributed; a single master image is compatible with multi-brand heterogeneous endpoints, with automatic driver matching and BIOS/UEFI dual boot support.
Image packaging for ARM64 and LoongArch CPUs with Linux, for a smooth replacement of existing Windows labs.
Three-layer storage architecture: restart restores the base image, student changes or malware infections leave no trace, personal data is independently retained in the user data layer.
Console + WeChat mini-program, over 90% of operations such as endpoint monitoring, remote restart, system push can be done on the fly, one person manages the entire school/department.
No need to replace all machines. Reuse existing endpoints for cloud desktop delivery, extending device lifespan and reducing procurement budgets, with lower TCO over three years.
IDV3 (third-generation IDV) runs the desktop locally on the endpoint with central management; vDisk builds on that with the VOL architecture without a virtualization layer for physical-machine performance, supports multi-brand mixed endpoints through image/configuration separation, and supports Linux natively. It's the upgrade to IDV3.
Yes. Existing endpoints (including old PCs) can be reused, going live in four steps: server setup → image preparation → endpoint registration → distribution, with ARM64/Linux image packaging supported.
Yes. Image packaging for ARM64 and LoongArch CPUs with Linux, for moving labs to Linux.
Yes. The desktop runs locally on the endpoint, available even without network, and unaffected by central server failures.
Fill in the information. The presales team will provide a one-on-one upgrade plan and free trial based on your computer lab scale and current status, and send the software acquisition method. Self-service QR code registration, renewable three times, no limit on endpoints.