<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by ZSvirt Community on Medium]]></title>
        <description><![CDATA[Stories by ZSvirt Community on Medium]]></description>
        <link>https://medium.com/@zsvirt?source=rss-16d9dff0f9c7------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*-M814mszohcHESnWD6aVSw.png</url>
            <title>Stories by ZSvirt Community on Medium</title>
            <link>https://medium.com/@zsvirt?source=rss-16d9dff0f9c7------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 20:44:19 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@zsvirt/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[ZSvirt vs Proxmox VE 9: A 2026 Comparison]]></title>
            <link>https://zsvirt.medium.com/zsvirt-vs-proxmox-ve-9-a-2026-comparison-579e552e6b93?source=rss-16d9dff0f9c7------2</link>
            <guid isPermaLink="false">https://medium.com/p/579e552e6b93</guid>
            <category><![CDATA[virtualization]]></category>
            <category><![CDATA[proxmox]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <dc:creator><![CDATA[ZSvirt Community]]></dc:creator>
            <pubDate>Thu, 15 Oct 2026 08:21:26 GMT</pubDate>
            <atom:updated>2026-10-15T08:21:26.110Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u2Xe088QWmM8XBar8zWhuw.png" /></figure><p>After Broadcom ended perpetual licensing for VMware vSphere at the end of 2023, many teams chose Proxmox VE (PVE for short). For the two years that followed, Proxmox became the mainstay of the free, KVM-based mid-market.</p><p>On 12 August 2026, ZSvirt — launched by infrastructure vendor ZStack — announced it was open-sourced under GPL 3.0. For a lot of teams, that adds another option among open-source virtualization platforms.</p><p>ZSvirt is an enterprise-focused open-source virtualization platform, and against Proxmox it differs in target users, use cases and development path.</p><p>Versions compared:</p><ul><li>ZSvirt 1.0.0 — released 2026–08–12</li><li>Proxmox VE 9.2 — x86–64 released 2026–05–21, arm64 released 2026–08–05</li></ul><blockquote><em>This article is published by the ZSvirt project, so read the ZSvirt claims accordingly. ZSvirt’s own capabilities are taken from its public documentation and its published comparison testing; Proxmox VE figures come from Proxmox’s official documentation. Vendor-run comparisons are a starting point, not independent verification — reproduce the ones that matter to you in your own lab. Every external figure carries an inline source.</em></blockquote><h3>1. What Are ZSvirt and Proxmox VE?</h3><p>Both are open-source virtual machine platforms built on KVM, each with built-in web management that lets any node manage the cluster without a separate management appliance to deploy. They come from opposite directions, which comes down to one line:</p><ul><li><strong>ZSvirt</strong>: starts from mature enterprise virtualization technology and reaches global users and use cases through open source.</li><li><strong>Proxmox VE</strong>: starts from the open-source community and homelabs, and works its way up to enterprise use through continuous iteration.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1019/1*WnZf5dL3Uc_oUswEYLfi_Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/799/0*i3UKAJAZ85-Aew0J.png" /></figure><p><em>Screenshot: the ZSvirt console overview, with the resource topology laid out as datacenter → cluster → host → virtual machine.</em></p><h3>2. What Do the Two Platforms Have in Common?</h3><p>Both ZSvirt and PVE are built on KVM, and both support the same baseline capabilities:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/846/1*ss1AXZTy_xSLtNX4Bx2aKg.png" /></figure><p>If a team’s needs stop at managing a few nodes, high availability, snapshots, backups and a web UI, both platforms deliver for free. The difference is in how each packages those capabilities into a product for the user’s scenario.</p><h3>3. How Do Day-to-Day VM Operations Differ?</h3><p>Day-to-day VM operations are the most basic and most visible difference between the two. Every feature below is based on ZSvirt/ZSphere and Proxmox VE public material and compared through side-by-side functional testing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/848/1*PKYy7EqnIPXdRBlTx7IAlA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/850/1*-efbKk4snQiVajmYfMoJGg.png" /></figure><p>Two things stand out for anyone evaluating these features.</p><ul><li>Several of ZSvirt’s advantages are about not having to use the command line: OVA export, OVF import, online IP changes, batch deployment from a template and a guided vNUMA workflow are all GUI operations on ZSvirt, where on PVE they need the CLI, manual configuration or a third-party tool.</li><li>PVE supports VM hibernate, for which ZSvirt has no equivalent.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*xh_y_lm2EoDcX87u.png" /></figure><p><em>Screenshot: ZSvirt’s template detail page, where a template can be converted back into a virtual machine — conversion between template and VM runs both ways.</em></p><h3>4. How Do They Scale, and How Does Scheduling Compare?</h3><p>Scale and scheduling are where the two platforms’ design philosophies are furthest apart, and where the choice matters most.</p><p>On scale, Proxmox VE uses corosync to keep cluster state consistent — a synchronous protocol every node participates in, and one that is highly sensitive to network latency. On cluster size, the <a href="https://pve.proxmox.com/pve-docs/chapter-pvecm.html">official documentation</a> states plainly, “There’s no explicit limit for the number of nodes in a cluster.” In practice, though, PVE clusters are normally kept under about 20 nodes, and a dedicated, isolated corosync network is required, because the more nodes there are, the more corosync’s latency sensitivity becomes a real problem. Past that, the standard approach is to run several small clusters and aggregate them with Proxmox Datacenter Manager, whose enterprise repository requires a Basic subscription or above.</p><p>ZSvirt’s design separates the management-node and compute-node roles. Management nodes can manage datacenters hierarchically, from cluster down to host, so a single control plane is specified to manage 10,000+ hosts. That is a cross-cluster management scale and a different dimension from PVE’s per-cluster practical limit, and it is why ZSvirt is better suited to enterprise datacenter management.</p><p>On scheduling, to match VMware’s DRS, Proxmox VE 9.2 added Cluster Resource Scheduling with escalating modes — Basic (the default, which counts guests rather than measuring load), Static Load (configured quotas) and Dynamic Load (live CPU and memory usage). In Dynamic mode, the approach is genuinely equivalent to a load-based scheduler like ZSvirt’s DRS. The caveats are what matter: balancing is opt-in, the dynamic mode acts on HA-managed guests, and the default mode is still count-based.</p><p>ZSvirt offers scheduling models for a range of scenarios, including VM scheduling groups, HA policies, VM startup policies and load-based DRS, and it balances on live CPU and memory thresholds across the cluster, with a recommendation history and configurable triggers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/854/1*Iu4jrQUiiMB3b67AJ6X3wg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*POPlSXRSH3hN2pq0.png" /></figure><p><em>Screenshot: a ZSvirt VM scheduling policy, where VMs are placed into a scheduling group with an associated policy.</em></p><p>In practice, ZSvirt’s scheduling is designed at cluster and datacenter granularity, with multiple policies for different scenarios, which suits batch and large-scale deployments; PVE splits into multiple clusters aggregated with PDM, and its scheduling policies are relatively limited.</p><h3>5. How Do You Migrate from VMware?</h3><p>Both platforms ship a migration path from VMware, and the difference is in how much of it is agentless and how much you have to drive by hand.</p><p>Proxmox VE has a built-in official ESXi import tool (added in 8.2), tested against ESXi 6.5–8.0, with live-import support. The <a href="https://pve.proxmox.com/wiki/Migrate_to_Proxmox_VE">official wiki</a> documents the boundaries: disks on vSAN are not supported, encrypted disks cannot be imported, vTPM state cannot be migrated (note this for Windows 11 VMs), imports of VMs with snapshots are markedly slower, and serial imports are recommended over parallel ones. The recurring pitfalls are elsewhere: Windows VMs boot only from IDE/SATA by default until VirtIO drivers are installed, VMware Tools must be uninstalled before the move rather than after, and mixed CPU instruction sets across hosts will break a migration if they are not checked first.</p><p>ZSvirt’s migration tool is ZMigrate (agentless), covering both online migration and offline import, with a documented workflow for each. The offline path has no scale limit; the online path does, so large estates are usually moved in waves.</p><p>As with any VMware migration, inventorying the hidden dependencies matters more than the cutover itself — backup scripts, monitoring probes, automation that calls vSphere APIs, uninstalling VMware Tools, and installing drivers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/849/1*yiUyOXGzPtnUAKl3KCUjJQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/799/0*c4bLxLa-xM3K8gBp.png" /></figure><p><em>Screenshot: the ZMigrate migration task list, showing each VM’s migration status and sync progress.</em></p><h3>6. How Do Automation, Security and Support Compare?</h3><p>On automation, ZSvirt exposes 2,000+ REST/OpenAPI endpoints with a native Terraform provider and Go, Python and Java SDKs, all in the Community Edition. PVE also provides a REST API and a well-known community Terraform provider, but no vendor-maintained Terraform provider of its own.</p><p>On security, ZSvirt ships Secure Boot, vTPM 2.0, VM encryption, security-group micro-segmentation and immutable audit logs in the Community Edition. PVE provides Secure Boot through OVMF, supports TPM state, and has a firewall that operates at the datacenter, node and VM levels; micro-segmentation and a broader security stack are things you assemble from its SDN and firewall features.</p><p>One practical difference from the functional testing is anti-spoofing: ZSvirt exposes it as a single toggle, while on PVE it requires enabling the firewall at datacenter, node and VM levels and opening the default DROP policy for corosync and management traffic first. ZSvirt ships its own backup module, with multiple backup and retention policies, whereas PVE needs Proxmox Backup Server layered on top to provide backup.</p><p>On support, PVE has a large community forum and a tiered subscription with tickets, currently on European business hours, moving to 24/7 for Standard and Premium during 2026.</p><p>ZSvirt’s community runs through GitHub and Discord, with a commercial edition for teams that need vendor support.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/850/1*Mi4JEgmKL4C9ChjCQHTzzw.png" /></figure><h3>7. How Do You Choose Between Them?</h3><p>Neither platform is a universal answer, and the right call depends on where you sit on scale, ecosystem and what you need from the feature set.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/850/1*SGu3NaqYLZSUZdKIrY8x4A.png" /></figure><p>Three judgments to close on:</p><ul><li><strong>Neither is a drop-in replacement for the other.</strong> Both are free, both run KVM, and both will run most VMware workloads after migration. Proxmox VE has a more complete community ecosystem, and much of its install base still comes from homelabs and enterprise test environments; ZSvirt builds in productized operations capabilities and focuses more on large-scale cluster management and enterprise scenarios.</li><li><strong>Both are mature products, but they took different routes.</strong> Proxmox VE follows an open-source community route, with a broad base of community enthusiasts and community support, and has been strengthening its enterprise product and service capabilities over the past two years. ZSvirt began on a commercial enterprise route and open-sourced in August 2026, opening up capabilities accumulated over ten years of production practice to lower the barrier to entry and offer more transparent technology and broader community collaboration, in order to grow its users and ecosystem.</li><li><strong>Both are cheap to test, so test.</strong> The cost of finding out whether either fits is close to zero. ZSvirt has a no-install <a href="https://demo.zsvirt.io/login">online demo</a>, a <a href="https://zsvirt.io/blog/zsvirt-quickstart-deploy-your-first-vm">step-by-step quick start</a>, and qcow2/OVA images that run on any machine supporting nested virtualization; Proxmox VE is a single ISO. Whether a platform fits is better settled by a test run than by any vendor’s comparison, this one included.</li></ul><h3>Frequently Asked Questions</h3><p><strong>Is ZSvirt free?</strong><br>Yes. The Community Edition is free for production use with no license fee, is licensed under GPL 3.0, and includes the full feature set — HA, DRS, snapshots, backup, templates and the REST API.</p><p><strong>Is Proxmox VE free?</strong><br>Yes. The free tier has the full feature set, and the ISO downloads directly from the Proxmox site. The <a href="https://www.proxmox.com/en/products/proxmox-virtual-environment/FAQ">official FAQ</a> confirms that features are not limited by subscription level.</p><p><strong>Does Proxmox VE have a DRS equivalent?</strong><br>Partly. Proxmox VE 9.2 introduced Cluster Resource Scheduling with dynamic load balancing, whose approach is genuinely equivalent to a load-based scheduler. But it is opt-in, it acts on HA-managed guests, and the default mode counts machines rather than measuring load. ZSvirt’s DRS ships in the Community Edition and balances on live CPU and memory thresholds.</p><p><strong>Can one tool manage both large ZSvirt and Proxmox VE estates?</strong><br>For ZSvirt, a single control plane is specified to manage 10,000+ hosts. Proxmox VE manages a single cluster, and multi-cluster management requires Proxmox Datacenter Manager, whose enterprise repository needs a Basic subscription or above.</p><p><strong>How do you migrate from VMware to ZSvirt?</strong><br>Through ZMigrate, which is agentless and supports online migration and offline import. Online migration has scale limits; offline import does not.</p><p><em>This article is written by the ZSvirt project. ZSvirt’s capabilities come from its public documentation and published comparison testing; Proxmox VE figures come from its official documentation and other public material. A comparison like this is a starting point — a real selection decision still calls for testing in your own environment.</em></p><h3>Sources</h3><ul><li><a href="https://zsvirt.io/blog/zsvirt-is-open-source">ZSvirt is open source — ZSvirt</a></li><li><a href="https://zsvirt.io/blog/zmigrate-workflow-walkthrough">ZMigrate workflow walkthrough — ZSvirt</a></li><li><a href="https://zsvirt.io/blog/zsvirt-quickstart-deploy-your-first-vm">ZSvirt quick start: deploy your first VM — ZSvirt</a></li><li><a href="https://docs.zsvirt.io/en/docs">ZSvirt documentation — docs.zsvirt.io</a></li><li><a href="https://github.com/zsvirt/zsvirt">ZSvirt source code — GitHub</a></li><li><a href="https://www.proxmox.com/en/products/proxmox-virtual-environment/FAQ">Proxmox Virtual Environment FAQ — Proxmox</a></li><li><a href="https://www.proxmox.com/en/about/company-details/press-releases/proxmox-virtual-environment-9-2">Proxmox Virtual Environment 9.2 released — Proxmox</a></li><li><a href="https://www.proxmox.com/en/about/company-details/press-releases/proxmox-virtual-environment-launches-official-arm64-support">Proxmox VE official ARM64 support — Proxmox</a></li><li><a href="https://pve.proxmox.com/pve-docs/chapter-pvecm.html">Cluster Manager (node limits and corosync requirements) — Proxmox VE documentation</a></li><li><a href="https://pve.proxmox.com/wiki/Migrate_to_Proxmox_VE">Migrate to Proxmox VE — Proxmox Wiki</a></li><li><a href="https://pve.proxmox.com/wiki/Proxmox_Datacenter_Manager_Roadmap">Proxmox Datacenter Manager roadmap — Proxmox Wiki</a></li><li><a href="https://pve.proxmox.com/pve-docs/qm.1.html">qm manual (suspend and hibernate) — Proxmox VE documentation</a></li><li><a href="https://github.com/bpg/terraform-provider-proxmox">Terraform provider for Proxmox VE — bpg (community)</a></li></ul><h3>Join the Community</h3><ul><li><strong>Issue reports</strong>: <a href="https://github.com/zsvirt/zsvirt/issues">GitHub Issues</a></li><li><strong>Community discussions</strong>: <a href="https://github.com/ZSvirt/zsvirt/discussions">GitHub Discussions</a></li><li><strong>Social media</strong>:</li><li>YouTube: <a href="https://youtube.com/@ZSvirt">https://youtube.com/@ZSvirt</a></li><li>LinkedIn: <a href="https://www.linkedin.com/in/zsvirt-community/">https://www.linkedin.com/in/zsvirt-community/</a></li><li>X/Twitter: <a href="https://x.com/ZSvirt">https://x.com/ZSvirt</a></li><li>Discord: <a href="https://discord.com/invite/KHsw63z9xA">https://discord.com/invite/KHsw63z9xA</a></li><li>Email: <a href="https://community@zsvirt.io/">community@zsvirt.io</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=579e552e6b93" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Virtualization Watch Issue 003: Citrix NetScaler Zero-Days Hit Over a Weekend; Sidero Builds a…]]></title>
            <link>https://zsvirt.medium.com/virtualization-watch-issue-003-citrix-netscaler-zero-days-hit-over-a-weekend-sidero-builds-a-06b6456aa706?source=rss-16d9dff0f9c7------2</link>
            <guid isPermaLink="false">https://medium.com/p/06b6456aa706</guid>
            <category><![CDATA[virtualization]]></category>
            <category><![CDATA[proxmox]]></category>
            <category><![CDATA[zsvirt]]></category>
            <dc:creator><![CDATA[ZSvirt Community]]></dc:creator>
            <pubDate>Wed, 30 Sep 2026 08:21:31 GMT</pubDate>
            <atom:updated>2026-09-30T08:21:31.513Z</atom:updated>
            <content:encoded><![CDATA[<h3>Virtualization Watch Issue 003: Citrix NetScaler Zero-Days Hit Over a Weekend; Sidero Builds a Hypervisor into Talos Linux</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uG6xNCY3F4xMobIDv_Gm5A.png" /></figure><p>September 28, 2026 · Biweekly · Coverage window: 9/14–9/27</p><h3>From the Editor</h3><p>This issue opens with a severe vulnerability chain disclosed over a weekend.</p><p>On Saturday (9/26), the security firm watchTowr issued a sudden public warning: two NetScaler remote code execution flaws with no patches yet were already being exploited in the wild. The Dutch national cyber security center (NCSC-NL) went further, privately telling some organizations to take their appliances offline. On Sunday (9/27), Citrix published advisory CTX697096, fixing eight CVEs at once — two of them zero-days rated CVSS v4 9.5. CISA added both to its Known Exploited Vulnerabilities catalog the same day, leaving federal agencies three days to patch.</p><p>The same week, Sidero Labs put a hypervisor directly into Talos Linux, managing containers and virtual machines through one operating system and one API. Incident response and the evolution of the hypervisor itself are this issue’s two threads.</p><h3>In This Issue</h3><h3>Citrix NetScaler: Two Zero-Days Land Over a Weekend, with a 3-Day KEV Deadline</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*Fqk3HpffzgxB49zM.png" /></figure><p>On September 27 (Sunday), Citrix published advisory <a href="https://support.citrix.com/article/CTX697096">CTX697096</a>, fixing eight vulnerabilities in NetScaler ADC and NetScaler Gateway. Two of them were confirmed to be exploited in the wild:</p><ul><li><strong>CVE-2026–88771</strong> (CVSS v4 9.5): improper input validation lets an unauthenticated attacker execute arbitrary commands. <strong>Every deployment model is affected, including default configurations</strong> — no optional feature has to be enabled.</li><li><strong>CVE-2026–88772</strong> (CVSS v4 9.5): memory overflow leading to remote code execution or denial of service. The trigger is DTLS, and <strong>DTLS is on by default for VPN virtual servers</strong>.</li></ul><p>The fixes are in 14.1–73.37 and later, or 13.1–64.23 and later; 13.0 and 12.1 are end-of-support and need to be migrated. The same advisory covers six further flaws (CVE-2026–88773 through 88778), including a request-smuggling issue rated 9.3.</p><p>On September 26, watchTowr issued its public warning (<a href="https://watchtowr.com/intelligence/citrix-netscaler-zero-day-vulnerabilities-faq/">official FAQ</a>), saying the vulnerabilities came out of a forensic investigation and that the information was credible. That same day, some administrators reported receiving “take the appliance offline” advice relayed by vendors and security teams, tracing back to an NCSC-NL private pre-notification. On September 27, the day the advisory landed, CISA added both CVEs to the KEV catalog, giving <strong>federal agencies until September 30 — three days</strong>.</p><p>For context, this is the third time NetScaler has entered the KEV catalog this year: CVE-2026–8452 in August, then CVE-2026–19490 on September 9. NetScaler appliances sit at the enterprise network edge, handling VPN, load balancing, and authentication — once compromised, they serve as a pivot into the internal network.</p><blockquote><em>Sources: </em><a href="https://thehackernews.com/2026/09/warning-two-unpatched-citrix-netscaler.html"><em>The Hacker News</em></a><em> (9/27), </em><a href="https://support.citrix.com/article/CTX697096"><em>Citrix CTX697096</em></a><em>, </em><a href="https://watchtowr.com/intelligence/citrix-netscaler-zero-day-vulnerabilities-faq/"><em>watchTowr FAQ</em></a></blockquote><h3>Sidero Ships Talos Hypervisor: a Hypervisor Built into the Kubernetes Operating System</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*qY6MJ_ykP1raRvax.png" /></figure><p>On September 14, Sidero Labs announced native hypervisor capability in Talos Linux (<a href="https://www.prnewswire.com/news-releases/talos-linux-adds-native-hypervisor-and-edge-container-support--see-it-live-at-taloscon-2026-302877040.html">official press release</a>): enterprises can manage containers and virtual machines with <strong>one operating system and one API</strong>, without running Kubernetes for one job and a virtualization stack for another, and without having to learn KubeVirt first to run VMs. The same release adds direct container scheduling without Kubernetes, aimed at single-node edge deployments.</p><p>The essentials:</p><ul><li><strong>Fully open source</strong>, still under MPL-2.0. The alpha and a public demo arrive at TalosCon 2026 (Amsterdam, October 15–16), with <strong>general availability targeted for December 2026</strong>.</li><li>A second announcement the same day explains where the resources come from: <strong>Sidero Labs is being acquired by Yardi</strong>, a real-estate software company (<a href="https://www.siderolabs.com/blog/sidero-labs-joins-yardi">official blog 9/14</a>). Yardi was already running Talos in production; the company says the team will keep operating independently and that the open-source roadmap is unchanged.</li><li>The next day (9/15), Sidero rolled out a commercial edition, <strong>Talos Enterprise Linux</strong>: 24/7 support SLAs, FIPS builds, SBOM/VEX artifacts, and CVE-response SLAs — covering what a compliance-driven buyer normally has to assemble from several vendors.</li></ul><p>Talos’s positioning is distinct: rather than building another vSphere, it makes the hypervisor a native capability of an immutable infrastructure operating system.</p><h3>ZSvirt Community News: First Open-Source Monthly Report and Roadmap</h3><blockquote><em>This publication is produced by the ZSvirt community. This section covers the publisher’s own news.</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*4XAukrtEbjANLNmZ.png" /></figure><p>On September 15, ZSvirt published the first issue of its open-source monthly report, <a href="https://zsvirt.io/blog/zsvirt-open-source-monthly-issue-1/">Around the World</a>). It looks back at the first month since the full open-source release on August 12 (GPL-3.0) and publishes the product roadmap for the first time.</p><h3>Second-Half 2026 Roadmap (First Public Release)</h3><p>On hardware and release process: <strong>aarch64 support is under evaluation, and GPU components are on the plan</strong>; a formal release process (GitHub releases and tags) will follow, making version history traceable. Product work spans five areas:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mUg5D1JGKEHvNN2Y-J6g9w.png" /></figure><p>AreaPlanned work<strong>Security</strong>VM disk encryption, VM migration encryption<strong>DRS and migration</strong>Data-disk-only migration; live and cold migration for SAN, cold migration for NFS<strong>ZMigrate 2.1</strong>Pre-migration checks to head off complex migration risk, with a simpler, smarter flow<strong>Operations</strong>New metrics: VM CPU ready time, disk read/write latency, network packet loss, host CPU ready time; finer-grained external syslog forwarding; NVMe and FC IOPS/latency monitoring; a bundled QXL driver in VMTools<strong>Inventory</strong>Storage and VM registration extended to same-site scenarios</p><p>A reminder: <strong>Storytellers Phase 1 (the YouTube challenge) closes tomorrow, 9/28</strong>. Creators interested in taking part should sign up at <a href="https://github.com/ZSvirt/zsvirt/discussions/8">GitHub Discussion #8</a> before the deadline.</p><blockquote><em>Sources: </em><a href="https://zsvirt.io/zh/blog/zsvirt-open-source-monthly-issue-1/"><em>ZSvirt open-source monthly report issue 1</em></a><em> (9/15), </em><a href="https://github.com/ZSvirt/zsvirt"><em>GitHub: ZSvirt/zsvirt</em></a></blockquote><h3>Product &amp; Version News</h3><h3>Incus 7.5 / 7.5.1: Eleven Security Fixes, OVN Child Networks, GPU P2P (September 25)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*a-J7JMmBangQaJ5q.png" /></figure><p><a href="https://discuss.linuxcontainers.org/t/incus-7-5-has-been-released/27273">Incus 7.5</a> landed on September 25 with a dense changelog:</p><ul><li><strong>Security</strong>: eleven fixes at once, including a serious btrfs path traversal (CVE-2026–85185 / CVE-2026–85526) and arbitrary writes through symlinks in the migration data stream. This was a coordinated disclosure with Canonical, whose LXD 5.21.8 / 5.0.10 / 4.0.14 shipped the matching fixes on September 23; the same fixes are in LXD 6.9.</li><li><strong>Networking</strong>: OVN child networks, for more flexible logical topologies.</li><li><strong>Operations</strong>: instances can move across projects, and live migration is stronger.</li><li><strong>GPU</strong>: NVIDIA GPUDirect P2P support (nvidia.clique 0–15), so multi-GPU passthrough no longer takes a detour.</li><li><strong>Platform</strong>: a new NetBSD guest agent.</li></ul><p>The 7.5.1 that followed is not a follow-up fix release — it is a re-release, after 7.5.0 failed to produce release artifacts.</p><h3>VirtualBox 7.2.18 → 7.2.20: Two Maintenance Updates in a Week (September 15, September 22)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*O4iRp4y-opjNbYk7.png" /></figure><p>Oracle shipped VirtualBox 7.2.18 on September 15 with eleven fixes: a blue screen after saving state on Windows 11 on ARM guests, VDI image corruption, and adaptation for the RHEL 10.3 kernel, among others. That month’s Oracle Critical Patch Update also fixed CVE-2026–87279. On September 22 came 7.2.20, an urgent release targeting a regression 7.2.18 introduced (GitHub issue gh-870, VERR_SUP_VP_FOUND_EXEC_MEMORY at startup). With two releases in one week, desktop virtualization users should go straight to 7.2.20. Source: <a href="https://www.virtualbox.org/wiki/News">VirtualBox News</a></p><h3>Kata Containers 4.2.0: 80-Plus Changes (September 15)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*n_zXd9Gz_sf66Dzo.png" /></figure><p><a href="https://github.com/kata-containers/kata-containers/releases/tag/4.2.0">Kata Containers 4.2.0</a> arrived on September 15 with more than 80 changes: the guest rootfs moves to Ubuntu 26.04; the toolchain moves to Go 1.26.7 / Rust 1.96; the Rust runtime (runtime-rs) gains fd-passing block-device and VFIO device support for QEMU; and the Dragonball sandbox gains virtio-rng. Worth a look for confidential-container and lightweight-sandbox users.</p><h3>Harvester v1.9.0: a Whole-Stack Upgrade (September 16)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*CK4HR9Kdo3D8RH4Q.png" /></figure><p>SUSE’s hyperconverged platform <a href="https://github.com/harvester/harvester/releases/tag/v1.9.0">Harvester v1.9.0</a> shipped on September 16: the foundation moves to RKE2 v1.36, Longhorn v1.12, Rancher v2.15, and Kube-OVN v1.16, on an SLE Micro 6.2 base, with a preview of the Longhorn v2 storage engine. Fix releases are moving fast — v1.9.1-rc1 on September 17 and rc2 on September 23 — so GA should not be far off.</p><h3>Cloud Vendors: AWS T8i and Google X5 Both Reach GA</h3><ul><li><strong>AWS EC2 T8i is generally available</strong> (9/17): the burstable line gets a generational refresh, with up to 1.25x the network bandwidth, up to 2.4x the EBS bandwidth, and up to 30 percent better price-performance than T3. It launches in 16 regions, in sizes from nano to medium. Sources: <a href="https://aws.amazon.com/about-aws/whats-new/2026/09/ec2-t8i-instances-ga/">AWS What’s New</a>, <a href="https://aws.amazon.com/blogs/aws/new-low-cost-burstable-amazon-ec2-t8i-instances-are-generally-available/">AWS blog</a></li><li><strong>Google Cloud X5 is generally available</strong> (9/25): per-instance memory rises from 32 TB on X4 to <strong>48 TB</strong>, aimed at very large-scale SAP HANA scale-up and RISE with SAP. Source: <a href="https://docs.cloud.google.com/compute/docs/release-notes">Compute Engine release notes</a></li></ul><h3>Gartner Publishes Its First Server Virtualization Platforms Magic Quadrant (9/14)</h3><p>On September 14, Gartner published the Magic Quadrant for Server Virtualization Platforms (analysts: Tony Harvey, Daniel Bowers, Paul Delory, Tony Iams, Owen Marino), evaluating 17 vendors on Ability to Execute and Completeness of Vision — the first industry-wide assessment since Broadcom acquired VMware and licensing models were upended. Per Virtualization Review’s reading of the report, Gartner holds that Broadcom’s acquisition of VMware has “reinvigorated” the server virtualization market (<a href="https://virtualizationreview.com/articles/2026/09/23/gartner-broadcoms-vmware-deal-has-reinvigorated-server-virtualization.aspx">Virtualization Review, 9/23</a>).</p><h3>Teasers and Snapshots</h3><ul><li><strong>QEMU 11.1.2</strong> entered freeze on September 26 with 92 patches queued; the release is planned for September 28, just past this window.</li><li><strong>OpenStack 2026.2 “Hibiscus”</strong> is on schedule for September 30.</li><li><strong>Linux 7.3-rc5</strong> shipped on September 27 with KVM fixes (rc4 was September 20).</li><li>An <strong>“Orphaned VMs” RFC</strong> from the KVM community (9/20, authored by Pasha Tatashin) would let virtual machines keep running while the host kernel is updated in place, pushing downtime toward zero.</li><li>KVM Forum 2026 is set for November 12–13 in Vancouver.</li></ul><h3>Community Buzz</h3><h3>HN: virtio-nvgpu Reaches 98–100 Percent of Native GPU Performance Inside a KVM Guest (154 points / 65 comments)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*i8xcaMokEO8889th.png" /></figure><p>Nestri Labs’ open-source virtio-nvgpu hit <a href="https://news.ycombinator.com/item?id=49824864">Hacker News</a> on September 24: a purpose-built virtio GPU protocol gives KVM guests close to native (98–100 percent) NVIDIA GPU performance, and <strong>a single GPU can be shared across multiple VMs</strong>. The trade-offs: isolation is weak (no IOMMU isolation, no seccomp), which suits single-tenant and gaming/streaming workloads but not multi-tenant production. The comment thread’s consensus: the direction is compelling, but it is still far from a vGPU replacement.</p><h3>Other High-Scoring HN Posts This Fortnight</h3><ul><li><strong>Cloudflare open-sources Quick Tunnels</strong> (844 points / 317 comments, 9/18)</li><li><strong>FEX-Emu, “The Scourge of x86 Emulation”</strong> (295 points / 100 comments, 9/18) — the memory-consistency argument behind running x86 programs on ARM64</li><li><strong>86Box: emulating a Pentium II on an M6 Mac</strong> (282 points / 121 comments, 9/25)</li><li><strong>Floci: a local AWS emulator</strong> (205 points / 47 comments, 9/26)</li><li><strong>Drop: a rootless container sandbox</strong> (193 points / 63 comments, 9/22)</li></ul><h3>Security Advisories</h3><h3>[Critical] Arista VeloCloud Orchestrator Zero-Day: CVSS 10.0, Already Exploited (September 22)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*fQbUe7Chv-Zv9JP5.png" /></figure><p>Arista published <a href="https://www.arista.com/en/support/advisories-notices/security-advisory/24765-security-advisory-0183">SA0183</a>: on-premises VeloCloud Orchestrator (VCO, formerly the VMware SD-WAN orchestrator) carries an improper input validation flaw, <strong>CVE-2026–93952</strong> (CVSS 3.1 <strong>10.0</strong> / 4.0 9.5), affecting versions 5.2.0–5.2.3.15, 6.1.0–6.1.3.7, 6.4.0–6.4.2.7, and 7.0.0–7.0.0.2. At disclosure there was <strong>active exploitation and published indicators of compromise</strong>; CISA added it to the KEV catalog the same day, giving federal agencies three days (until 9/25). The fixes are in 5.2.3.16+ and 6.4.2.8+, and <strong>the 6.1.x and 7.0.x trains had no patch on disclosure day</strong>. Arista’s guidance is to limit access to the VCO web interface to trusted administrative networks and to watch for unexpected outbound traffic and backdoor processes; note that exploitation requires certificate-based Edge-to-VCO authentication to be configured and network reachability to the web interface. Hosted instances have already been patched by Arista.</p><h3>QEMU 9pfs Guest Escape: CVE-2026–93834 (Disclosed September 22)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*hvBd1YuXUxWMj4Hi.png" /></figure><p>QEMU’s 9p filesystem (virtio-9p) has a use-after-free race, <a href="https://access.redhat.com/security/cve/CVE-2026-93834">CVE-2026–93834</a> (CVSS 8.8): a guest can race Tlcreate/Twalk messages to escape a shared directory and read, write, and execute on the host with the QEMU process’s privileges. A public proof of concept exists. <strong>Mitigation: disable 9pfs and use virtio-fs instead.</strong> Red Hat published its advisory page on September 25. Anyone using 9p shared directories for desktop virtualization or development environments should check their setup.</p><h3>Cloudflare Containers: Cross-Tenant Data Residue (Disclosed September 24)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*XK8RGC3ezVpyyyk4.png" /></figure><p>Cloudflare published a <a href="https://blog.cloudflare.com/containers-cross-tenant-vulnerability/">detailed technical post-mortem</a>: the shared storage pool behind its Containers and Sandboxes products had skip_block_zeroing enabled, so reclaimed 64 KiB disk blocks were handed to new tenants without being zeroed. Writing 4 KiB was enough to read 60 KiB of another tenant&#39;s leftover data (reproduced in 18 of 24 deployments and on 20 of 22 nodes). The researcher Oren Yomtov (Accomplish) reported it through HackerOne on September 4; the core fix was deployed on September 7, and cleanup of existing disks and image caches completed on September 19. Reviewing historical disk I/O telemetry, Cloudflare <strong>found no evidence of malicious exploitation</strong>, and because scheduling is automatic, an attacker could not target a specific victim. The root cause sits in the storage layer, not in container escape.</p><h3>vCenter CVE-2026–59310 Follow-Up: CISA Confirms Ransomware Gangs Are Using It (September 15)</h3><p>According to BleepingComputer, CISA has confirmed that ransomware gangs are exploiting the vCenter flaw CVE-2026–59310; Shadowserver data shows 450-plus vCenter instances still exposed to the internet, and the official FIRST EPSS score is 2.6 percent (84.5th percentile, data dated 2026–09–27). The federal patch deadline (8/21) has passed; unpatched instances are overdue.</p><h3>Other Security News</h3><ul><li>Three Linux kernel flaws entered the KEV catalog (9/18): CVE-2025–39682 (kTLS, 9.8), CVE-2026–53266 (8.8), and CVE-2025–39964 (7.8).</li><li>libvirt flaw CVE-2026–18917 (7.8), fixed by Red Hat in RHSA-2026:68510 (9/17).</li><li>No new VMware VMSA advisories were published within this window.</li></ul><h3>Tools &amp; Good Reads</h3><ul><li><strong>virtio-nvgpu</strong>: the headline HN post of this issue — near-native NVIDIA GPU performance in KVM guests, with one card shared across VMs (mind the weak-isolation caveat).</li><li><strong>pve-meta</strong>: declarative, YAML-based management of Proxmox cluster configuration; a well-received community project this fortnight.</li><li><strong>Drop</strong>: a rootless container sandbox, positioned against gVisor and sysbox but without requiring privileges.</li><li><strong>Floci / Fakecloud</strong>: new local AWS emulation options beyond LocalStack; both hit HN this fortnight.</li><li><strong>William Lam: “Multi-Tenant Model Sharing in VCF 9.1.1 GA”</strong> — essential reading for private-AI scenarios.</li><li><strong>A community-rewritten VCF 9.1.x deployment guide</strong>: a more down-to-earth companion to the official docs, full of field notes.</li></ul><h3>Number of the Week: 3 (days)</h3><p>CISA twice squeezed the federal patch deadline down to three days this fortnight: Arista VeloCloud (listed 9/22, due 9/25) and the Citrix NetScaler zero-days (listed 9/27, due 9/30).</p><p>The patch window for edge-device vulnerabilities has moved from weeks to days.</p><h3>Next Issue Preview</h3><ul><li>QEMU 11.1.2 stable release (frozen, 92 patches).</li><li>OpenStack 2026.2 “Hibiscus” (9/30).</li><li>VMware Explore on Tour: Mumbai (9/29–30) and Singapore (10/1–2); the Frankfurt stop (10/13–14) is expected to bring more detail on the returning vSphere Standard.</li><li>TalosCon 2026 (Amsterdam, 10/15–16): the public Talos Hypervisor alpha demo.</li><li>Harvester v1.9.1 GA.</li><li>Azure NVv4 series retirement (9/30).</li><li>KVM Forum 2026 (Vancouver, 11/12–13).</li></ul><p><strong>About this publication</strong>: Virtualization Watch (VirtWatch Weekly) is a biweekly virtualization industry publication produced by the ZSvirt community, covering product news, security advisories, and community discussion across VMware/Broadcom, Proxmox, KVM/QEMU, Hyper-V, KubeVirt, Nutanix, and more. It is compiled with AI-cluster assistance; every fact is linked to its source; we aim for balanced viewpoints and welcome corrections. All factual content in this issue was verified against primary sources (official press releases, official blogs, GitHub release pages, original HN posts, etc.), with key source pages captured by the editors. News window: September 14–27, 2026; editorial deadline: September 27, 2026. Visit <a href="https://zsvirt.io/">zsvirt.io</a> for past issues and the video edition.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=06b6456aa706" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[10 Reasons You Must Install ZSvirt VMTools]]></title>
            <link>https://zsvirt.medium.com/10-reasons-you-must-install-zsvirt-vmtools-2fb1f0b6b8f2?source=rss-16d9dff0f9c7------2</link>
            <guid isPermaLink="false">https://medium.com/p/2fb1f0b6b8f2</guid>
            <category><![CDATA[zsvirt]]></category>
            <category><![CDATA[virtualization]]></category>
            <category><![CDATA[vmware]]></category>
            <category><![CDATA[vmtools]]></category>
            <dc:creator><![CDATA[ZSvirt Community]]></dc:creator>
            <pubDate>Wed, 30 Sep 2026 08:18:09 GMT</pubDate>
            <atom:updated>2026-09-30T08:18:09.835Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wMnObL9O5wCsCsYAxIIrnA.png" /></figure><p><em>On both Windows and Linux, ZSvirt VMTools is not an optional utility. It is the link that brings a virtual machine into the platform’s management loop.</em></p><h3>10 Reasons You Must Install ZSvirt VMTools</h3><p>A virtual machine that boots and answers on the network is merely running. It becomes an operational resource only when the platform can see what is happening inside the guest, deliver management actions reliably, and keep that control through backups, migrations, and network failures.</p><p>VMTools is what makes that possible. Without it, the platform manages a black box that happens to consume CPU and memory.</p><h3>What VMTools Actually Consists Of</h3><p>ZSvirt VMTools bundles four components. It is worth knowing which is which, because some capabilities come from VMTools and others already ship with the operating system.</p><ul><li><strong>ZSvirt monitoring agent</strong> — collects runtime metrics from inside the guest and feeds the platform’s monitoring charts and alerts.</li><li><strong>QEMU Guest Agent (QGA)</strong> — establishes a management channel between the platform and the guest that does not depend on the VM’s business network.</li><li><strong>VirtIO drivers</strong> — provide virtual disk, network adapter, memory balloon, and guest-communication devices.</li><li><strong>Cloudbase-Init</strong> (cloud-init on Linux) — applies first-boot configuration: users, passwords, hostname, network, and User Data.</li></ul><blockquote><em>Mainstream Linux distributions include VirtIO drivers natively, so on Linux the driver component often needs no installation.</em></blockquote><p>Installing VMTools is not about displaying a few extra charts. It is what makes observability, control, recoverability, and automation work as one system.</p><h3>Ten Reasons VMTools Is Not Optional</h3><h3>01. See what is actually happening inside the VM</h3><p>An application starts slowing down while the host-level resource charts look perfectly normal. Allocation data alone cannot tell you whether the guest is short on memory, running out of disk space, or hitting an internal workload spike.</p><p>The ZSvirt monitoring agent collects CPU, memory, disk capacity, and other metrics from inside the guest and ships them to the management platform. That gives you both current diagnosis and historical trend: recurring peaks, capacity growth, and the evidence you need to resize a workload before it becomes an incident.</p><p><strong>Capability boundary:</strong> Host monitoring remains useful, but it cannot replace guest-level visibility.</p><h3>02. Quiesce the file system for consistent snapshots and backups</h3><p>Databases, file services, and applications write continuously. When the platform needs to create an online backup or snapshot, taking a raw point-in-time image of a disk that is still changing produces a crash-consistent result at best.</p><p>VMTools provides guest quiescing: before the snapshot forms, the file system is brought to a controlled, consistent state, and writes resume once it completes.</p><p><strong>On Windows</strong>, QGA coordinates through VSS — the backup requestor, application writers, and the snapshot provider. Applications commit transactions, roll logs, and flush caches; VSS briefly freezes write I/O; the platform captures the point-in-time snapshot; VSS then tells applications to resume. As long as the workload ships a functioning VSS writer, you get application-aware consistency rather than merely crash consistency.</p><p><strong>On Linux</strong>, QGA can run a pre-freeze hook, then syncs and freezes freezable local file systems. The kernel lets in-flight transactions complete, writes dirty data, metadata, and journal entries to disk, and blocks new modifications. After the snapshot, QGA thaws writes and can invoke a post-thaw hook. Network file systems are not frozen by default.</p><p><strong>Capability boundary:</strong> File-system consistency is guaranteed by default. Database-level consistency still requires a VSS writer, a freeze hook, or the database’s own backup tooling.</p><h3>03. Shut down and restart guests cleanly</h3><p>Before host maintenance, a cluster upgrade, or a power drill, you may need to shut down or restart VMs in bulk. Doing it by hand means logging into each one, and the maintenance window disappears into repetitive work. Cutting power instead risks data that never reached disk.</p><p>Through QGA, the platform can ask the guest operating system for a normal shutdown or restart: services stop in order, applications finish their work, and cached data is flushed. The platform then continues with migration or maintenance based on the VM’s actual state, which makes bulk power operations predictable.</p><p><strong>Capability boundary:</strong> If a guest is genuinely hung, the request can still fail. Plan for timeouts and a fallback.</p><h3>04. Get accurate IP, NIC, and guest information</h3><p>A VM changes its static IP, gains a NIC, adjusts routes, or grows a file system — and the platform still shows the old values. Remote connections, automated audits, and downstream deployment steps then target the wrong address, or flag a healthy VM as unreachable.</p><p>QGA queries NICs, IP addresses, hostname, and file systems from inside the guest, and the platform surfaces that data. Compared with inferring from DHCP, switch tables, or the host, what the guest reports directly reflects the operating system’s current state — a far more reliable input for automation.</p><p><strong>Without it:</strong> Guest information may be empty, stale, or inconsistent with reality.</p><h3>05. Do day-two operations without logging in</h3><p>VMs in production still need their login password reset, hostname changed, IP, DNS, or MTU adjusted — or the same inspection and remediation run across a batch. Logging into each one is slow and easy to get subtly wrong.</p><p>QGA provides a runtime channel from the platform into the guest operating system. Within what the current version supports, the platform can push configuration, execute commands or scripts, and read or write files. Routine changes and bulk remediation become platform-initiated actions rather than a queue of individual sessions.</p><p><strong>Capability boundary:</strong> Reason 05 covers runtime operations. Reason 10 covers first-boot deployment.</p><h3>06. Keep a rescue path when the network fails</h3><p>A single bad IP, route, firewall rule, or NIC configuration can cut off remote access and business traffic at the same time. Every conventional way into the guest is now gone, and a small misconfiguration becomes an extended outage.</p><p>QGA typically communicates over a virtio-serial channel that does not depend on the VM’s business IP. Within the platform’s supported scope, operators can still read guest information, push a corrected configuration, or run a repair script — turning what would have been a console session or a disk-attach-and-repair into an online fix.</p><p><strong>Capability boundary:</strong> This is not hardware-level out-of-band management. The guest kernel, QGA, and the communication device all have to be working.</p><h3>07. Keep guest and host time in sync</h3><p>After a long pause, a save-state restore, or a migration, a VM can drift noticeably in time. A few minutes of skew is enough to break domain authentication, fail certificate validation, miss scheduled jobs, and scramble the ordering of logs across systems.</p><p>QGA exposes interfaces for reading and setting guest time, so the platform can correct drift after exactly these lifecycle events. Continuous day-to-day synchronization stays with the guest’s native time service — a combination of “correct quickly after an event, stay synced while running.”</p><p><strong>Implementation note:</strong> Standardize on one time source and one sync strategy. Multiple continuous correction mechanisms can fight each other.</p><h3>08. Unlock the performance of virtual devices</h3><p>Databases push heavy disk I/O. Application servers need network throughput. Resource pools need to reclaim and rebalance VM memory dynamically. Generic emulated devices may work, but they add overhead and cannot expose the platform’s full set of virtualization features.</p><p>VirtIO uses a paravirtualized device model designed for virtual environments, providing efficient paths for virtual disks, network adapters, balloon memory, and guest communication. Correct drivers shorten the data path and underpin both QGA communication and dynamic memory adjustment — performance and management capability arriving together.</p><p><strong>Risk note:</strong> These drivers sit on the boot disk and the network path. Validate version compatibility and a rollback procedure before upgrading them.</p><h3>09. Personalize VMs created from a template</h3><p>A standard template has to produce many VMs, each with its own hostname, network configuration, and system identity. If an administrator still logs in to change those by hand, the template has copied a disk without delivering an automated service.</p><p>When creating VMs from a template, a Customization Spec passes structured system configuration into the guest, and Cloudbase-Init — cloud-init on Linux — applies it at first boot. QGA then reports the runtime IP and guest state back to the platform, closing the loop from template to configured instance.</p><p><strong>Implementation note:</strong> What you can actually configure depends on the fields the current Customization Spec exposes and on the guest version. Check both.</p><h3>10. Close the last mile of VM delivery</h3><p>You create a VM in ZSvirt, the operating system is ready — and then someone still has to install software, write application configuration, and register the instance with existing management systems. If that means logging in and running scripts, your automation stopped at VM creation.</p><p>User Data lets a new VM receive declarative configuration or a startup script and execute it during first boot. One base image stays generic while each instance gets its own deployment logic. Typical uses:</p><ul><li>Install and start a web server, runtime, database client, or container component</li><li>Write package repository, NTP, DNS, application parameter, and environment variable settings</li><li>Create users and directories, inject SSH public keys, mount data disks, or expand file systems</li><li>Download an application, start its services, and register the instance with configuration or asset management systems</li></ul><p><strong>Implementation note:</strong> Scripts should be idempotent, and should handle network dependencies, retries, and the protection of sensitive data.</p><h3>Operations Checklist</h3><p>For every ZSvirt VM, verify at least these four things:</p><ul><li>Check the VMTools packages you installed against the component boundaries above — some capabilities come from VMTools, others from the OS.</li><li>Confirm advanced monitoring, guest information, time synchronization, and agent health alerts are all working.</li><li>Test shutdown, guest customization, configuration delivery, and network-loss recovery in a non-production environment.</li><li>Validate backups by proving applications and data can actually be restored — not merely that the job reported success.</li></ul><h3>What You Are Actually Installing</h3><p>ZSvirt VMTools installs more than a monitoring agent, a communication channel, and a set of drivers. It installs the complete management capability that every virtual machine needs — the difference between a VM that runs and a VM you can operate.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2fb1f0b6b8f2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Open Source, Month One: 106 Countries & Regions Downloaded]]></title>
            <link>https://zsvirt.medium.com/open-source-month-one-106-countries-regions-downloaded-d0ac1d3c794e?source=rss-16d9dff0f9c7------2</link>
            <guid isPermaLink="false">https://medium.com/p/d0ac1d3c794e</guid>
            <category><![CDATA[virtualization]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[vmware-vsphere]]></category>
            <dc:creator><![CDATA[ZSvirt Community]]></dc:creator>
            <pubDate>Fri, 18 Sep 2026 06:09:54 GMT</pubDate>
            <atom:updated>2026-09-18T06:10:09.768Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UxBu4bGW7ry6EfKeP_QJoQ.png" /></figure><p>Data as of 2026–09–11<br>Coverage window: 2026–08–12–2026–09–11 (first month of open source)</p><p>One month ago, we open-sourced ZSvirt.</p><p>Over the past month we kept building, kept learning, and kept connecting with people around the world. The first month brought new users, new ideas, new content, and plenty of moments worth sharing.</p><p>This is the first issue of ZSvirt Open Source Monthly. Let’s look back at ZSvirt’s first month — what happened around the world, and where we go from here.</p><h3>01 — Product &amp; Releases</h3><h3>ZSvirt Goes Open Source Worldwide</h3><p>On 2026–08–14 we open-sourced ZSvirt’s core IaaS engine under GPL-3.0. A month later, that code has reached <strong>106 countries and regions</strong> (unique downloads, counted by ISO 3166) — further than we expected for an engine that has been public for a single month.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*7FvGkhLK5AkiSx9o.png" /></figure><p>Open-sourcing also meant more than publishing code. In the same month we kept lowering the barrier to running ZSvirt: new OVA and QCOW2 images, an open-source MCP Server, and fuller documentation, so it can be brought up on VMware, VirtualBox, KVM, or any cloud host.</p><h3>OVA &amp; QCOW2 Packages</h3><p>We added OVA and QCOW2 images for more flexible installation across different environments, further lowering the barrier to deploying ZSvirt. Importing an OVA or QCOW2 image into an existing vSphere or KVM environment brings up a complete ZSvirt environment in about five minutes.</p><p>The download center now offers four package types — ISO (5.41 GB), OVA (17.02 GB), QCOW2 (24.02 GB), and ZMigrate — each with a SHA256 checksum.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/799/0*IsGbZ4tDumxCkKqL.png" /></figure><ul><li><a href="https://zsvirt.io/blog/nested-virtualization-management-node">Deploy ZSvirt Without Physical Hardware: qcow2 and OVA Images Are Here</a></li><li><a href="https://zsvirt.io/download">ZSvirt Download Center</a></li></ul><h3>MCP Server Open-Sourced</h3><p>We open-sourced the companion <a href="https://github.com/ZSvirt/zsvirt-mcp-server">ZSvirt MCP Server</a>, letting AI assistants dynamically discover and call ZSvirt’s 2,000+ OpenAPI endpoints. Only read-only APIs are exposed by default, supporting AI-driven interaction with and monitoring of virtualized environments. Install it from PyPI: pip install zsvirt-mcp-server.</p><h3>Project Data</h3><ul><li><strong>GitHub</strong>: <a href="https://github.com/ZSvirt/zsvirt">ZSvirt/zsvirt</a> — <strong>1,664 stars / 303 forks</strong> (as of 2026–09–11)</li><li><strong>Trendshift</strong>: reached <strong>#1 Java Repository of the Day</strong> (2026–08–16, #21 across all languages) and <strong>#2 Java Repository of the Week</strong> for week 34</li><li><strong>Media coverage</strong>: <a href="https://www.opensourceforu.com/2026/08/zstack-open-sources-zsvirt-virtualisation-platform/">Open Source For You</a>, GlobeNewswire, and others</li><li><strong>Download reach</strong>: 106 countries and regions, counted by ISO 3166</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/799/0*FTz9VG3jlyLT-653.png" /></figure><h3>02 — Official Content</h3><p>Over the past month we published a run of practical content covering installation, deployment, migration, and real-world use cases.</p><h3>Best Practices</h3><ul><li>★ <a href="https://zsvirt.io/blog/evaluate-zsvirt-as-a-vmware-alternative">Evaluating ZSvirt as a VMware Alternative: A PoC Guide from Deployment to Migration (2026–08–27)</a> — a complete evaluation guide: how to deploy ZSvirt, verify key capabilities, and plan a migration path away from VMware.</li><li>★ <a href="https://zsvirt.io/blog/zmigrate-workflow-walkthrough">ZSvirt Migration in Practice: Three Ways to Migrate VMs from VMware (2026–08–19)</a> — ZMigrate live migration (about five minutes per VM switch, up to 50 concurrent), OVF import, and VMDK upload — three approaches for different migration scenarios.</li><li>★ <a href="https://zsvirt.io/blog/zsvirt-architecture">ZSvirt Architecture Explained: How a Production-Proven Virtualization Engine Is Built (2026–08–17)</a> — a breakdown of ZSvirt’s architecture: one control plane supporting 10,000+ hosts, 768 vCPUs per VM, and the engineering trade-offs behind it.</li><li><a href="https://zsvirt.io/blog/zsvirt-quickstart-deploy-your-first-vm">ZSvirt Quick Start: From ISO to Your First VM, Step by Step</a> — deploy in 30–40 minutes with All-in-One mode and create your first VM.</li></ul><p>★ marks this month’s editor’s picks.</p><h3>Official Videos</h3><p>As of 2026–09–11, the <a href="https://www.youtube.com/@ZSvirt">official ZSvirt YouTube channel</a> has published <strong>10 videos</strong>:</p><p>TypeCountContentLaunch video1ZSvirt goes open sourceHands-on tutorials2Installing from scratch, migrating from VMwareVirtWatch Weekly1Episode 1ZSvirt Episode feature tutorials6Datacenter/cluster/hosts, data storage, distributed switches and port groups, VMTools, and more</p><h3>03 — Community &amp; Creators</h3><h3>ZSvirt Community Discord</h3><p>The ZSvirt Community Discord is now open — a place for users and community members to talk, ask questions, share experience, and help each other out.</p><p><a href="https://discord.gg/KHsw63z9xA">Join ZSvirt Community →</a></p><p>You can also find us on <a href="https://github.com/ZSvirt/zsvirt/discussions">GitHub Discussions</a>, LinkedIn (<a href="https://www.linkedin.com/in/zsvirt-community/">ZSvirt Community</a>), and X (<a href="https://x.com/ZSvirt">@ZSvirt</a>) — or email us at <a href="/service/mailto:community@zsvirt.io">community@zsvirt.io</a>.</p><h3>ZSvirt Storytellers — Phase 1: YouTube Challenge</h3><p>We launched <strong>ZSvirt Storytellers</strong>, inviting creators and community members to share their stories, hands-on experience, and perspectives on ZSvirt.</p><p>The challenge is still running. As of 2026–09–11, <strong>3 participants have submitted videos and 5 more are in progress</strong>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/630/0*LFCDJdFakMKC0qvR.png" /></figure><p><strong>#01 vikas9452-git (India)</strong> — the first participant from India, publishing <a href="https://www.youtube.com/watch?v=GIGsCokaF9s">ZSvirt vs VMware vs Proxmox</a> on the Labs Hands On channel (72.2k subscribers), with 10k views.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/630/0*W0kM3VSsxsQ-KRk7.png" /></figure><p><strong>#02 Profe Carlos Leal (Nicaragua)</strong> — the first participant from Nicaragua, publishing the Spanish-language <a href="https://www.youtube.com/watch?v=mHlj0U2PQjI">ZSvirt: ¿Rival de Proxmox VE y sucesor de VMware?</a>, with 19k views.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/630/0*CLtlpD3eiDPWWuqi.png" /></figure><p><strong>#03 sriramya11 (India)</strong> — published <a href="https://youtu.be/9qC6cKzFTGw">What is ZSvirt? VMware Alternative?</a> on 2026–09–07.</p><p><a href="https://github.com/ZSvirt/zsvirt/discussions/8">ZSvirt Storytellers Phase 1: YouTube Challenge (GitHub Discussion #8)</a></p><h3>Third-Party Creators</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/630/0*r3kuSArbM-xwe0YZ.png" /></figure><p>★ <strong>Byron Xie</strong> — a ZSvirt comparison series (including <a href="https://www.youtube.com/watch?v=azYlFPKz1fA">ZSvirt vs Proxmox</a> and three more videos), with hands-on benchmarks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/630/0*X83rmD_3vk3Cl3d-.png" /></figure><p>★ <strong>SoftsWeb</strong> — <a href="https://www.youtube.com/watch?v=eptOKZXWSts">ZSvirt: The Best VMware Alternative You Need to Try</a>, 43k views — among the most-watched third-party ZSvirt videos to date.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/630/0*eRXx7_2jElHZigkB.png" /></figure><p>★ <strong>Libre-Data</strong> — <a href="https://www.youtube.com/watch?v=4ucRaGLX3m8">I Tested This New Platform for Virtual Machines</a>, a test on real hardware with 10k views.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/630/0*iUGjeltS6-NuhIQf.png" /></figure><p><strong>AskGuru</strong> — a <a href="https://www.youtube.com/watch?v=eXBujaKHDv4">44-minute uncut installation walkthrough</a> from a blank machine to a working platform, nothing trimmed and nothing skipped.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/630/0*5tK2oG6PaJUMbYMa.png" /></figure><p><strong>hairong lu</strong> — a <a href="https://www.youtube.com/watch?v=T7AeL0fRb7M">full feature walkthrough of ZSvirt</a>, stepping through the platform feature by feature.</p><p>★ marks this month’s editor’s picks.</p><h3>Community Discussion</h3><ul><li><strong>Hacker News</strong> — <a href="https://news.ycombinator.com/item?id=49536562">Show HN: ZSvirt — A lightweight, scalable open source virtualization platform</a> picked up 72 points and 14 comments, sparking discussion about open-source virtualization and vendor lock-in.</li><li><strong>GitHub Discussions</strong> — installation and usage Q&amp;A stayed busy: an installation thread (11 replies), a ZMigrate deployment discussion (9 replies), an aarch64 image question, a QCOW2 installation issue, and more. Thanks to everyone who asked and answered.</li></ul><h3>04 — Contributors</h3><p>The progress of our first month came from everyone who submitted code, reported issues, translated docs, disclosed security findings, and took part in Q&amp;A.</p><h3>Thanks to Our Community</h3><p>Thanks to the community members who contributed code, reported issues, and joined the discussion this month (in no particular order):</p><p><strong>tllovesxs</strong>, <strong>chayu163</strong>, <strong>Jorge Perez</strong>, <strong>libre-data</strong>, <strong>shuchaoma</strong>, <strong>fankejing-just</strong>, <strong>techknight2020</strong>, <strong>dawnorigin</strong></p><h3>Security Disclosure</h3><p>Thanks to the following two community members, who reported security-related findings to <a href="/service/mailto:security@zsvirt.io">security@zsvirt.io</a>. We’re glad to credit them publicly:</p><ul><li><strong>Svector Anu</strong></li><li><strong>Jorge Perez</strong></li></ul><p>If you find a potential security issue in ZSvirt, we’d welcome a note at <a href="/service/mailto:security@zsvirt.io">security@zsvirt.io</a> as well.</p><h3>05 — What’s Next</h3><p>The first month is only the beginning. From here we’ll keep pushing on two fronts: product and community.</p><h3>Product</h3><p>Next up is continued work on hardware compatibility and product capabilities: aarch64 support is under evaluation and GPU components are on the roadmap. We’ll also establish a formal release process (GitHub Release / Tag) so that version evolution is clearer and traceable.</p><p>For the rest of 2026 H2, the roadmap centers on five areas:</p><ul><li><strong>Security</strong> — add disk encryption and live-migration encryption for virtual machines.</li><li><strong>DRS &amp; VM migration</strong> — more flexible migration options: data-disk-only migration; hot and cold migration for SAN scenarios, and cold migration for NFS.</li><li><strong>ZMigrate</strong> — ZMigrate 2.1 adds pre-checks that mitigate risk in complex migrations, alongside simpler and smarter migration workflows.</li><li><strong>Operations</strong> — more monitoring metrics (VM CPU ready time, VM disk read/write latency, network packet drop rate, host CPU ready time); finer-grained log levels for external syslog forwarding; NVMe and FC device monitoring including IOPS and latency; and built-in QXL drivers in VMTools for better VM console display and resolution.</li><li><strong>Inventory management</strong> — extend storage and VM registration to cover same-site registration.</li></ul><h3>Community</h3><ul><li><strong>VirtWatch Weekly</strong> — our virtualization and open-source infrastructure weekly will keep publishing (Episode 1 is on <a href="https://www.youtube.com/watch?v=9oO7FAFX9Jw">YouTube</a>).</li><li><strong>Storytellers Phase 1 and later phases</strong> — Phase 1 closes on 2026–09–28, and further phases are in planning. More creators are welcome to join.</li></ul><h3>06 — Get Involved</h3><p><strong>Source </strong><a href="https://github.com/ZSvirt/zsvirt">github.com/ZSvirt/zsvirt</a></p><p><strong>Download </strong><a href="https://zsvirt.io/download">zsvirt.io/download</a></p><p><strong>Docs </strong><a href="https://docs.zsvirt.io/en/docs">docs.zsvirt.io/en/docs</a></p><p><strong>Community </strong><a href="https://discord.gg/KHsw63z9xA">Discord</a> · <a href="https://github.com/ZSvirt/zsvirt/discussions">GitHub Discussions</a> · <a href="https://www.linkedin.com/in/zsvirt-community/">LinkedIn</a> · <a href="https://x.com/ZSvirt">X @ZSvirt</a></p><p><strong>Contact </strong><a href="/service/mailto:community@zsvirt.io">community@zsvirt.io</a></p><p>Thank you for every download, every install, every video, and every piece of feedback.</p><p>One month. One world. More to come.</p><p>— ZSvirt Team</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d0ac1d3c794e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Deploy ZSvirt Without Physical Hardware: qcow2 and OVA Images Are Here]]></title>
            <link>https://zsvirt.medium.com/deploy-zsvirt-without-physical-hardware-qcow2-and-ova-images-are-here-56f8f215d95a?source=rss-16d9dff0f9c7------2</link>
            <guid isPermaLink="false">https://medium.com/p/56f8f215d95a</guid>
            <dc:creator><![CDATA[ZSvirt Community]]></dc:creator>
            <pubDate>Tue, 15 Sep 2026 09:54:39 GMT</pubDate>
            <atom:updated>2026-09-15T09:54:39.283Z</atom:updated>
            <content:encoded><![CDATA[<p>Over the past few weeks, we’ve covered everything from the open-source announcement to evaluating, deploying, and migrating. Today, we want to share a change that makes evaluating ZSvirt faster: <strong>the download center now offers qcow2 and OVA images</strong>.</p><p>Trying ZSvirt used to mean either provisioning a physical server or mounting the ISO inside a VM and walking through a full installation. For teams that just want to see whether it works, that’s a real barrier to entry.</p><p>Not anymore. Download a qcow2 or OVA file, create a VM on your VMware, VirtualBox, KVM, or cloud host, boot it, set an IP — and the ZSvirt management node is ready. No physical hardware required.</p><p>Head to the <a href="https://zsvirt.io/download/">download center</a> to see the newly added packages:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*DulFxM1zizCYDKrb.png" /></figure><h3>Why qcow2 and OVA</h3><p>The ISO targets a from-scratch install: an installer guides you through selecting the system disk, configuring the network, and setting the root password. qcow2 and OVA are prepackaged VM images — <strong>the OS and management-node services are already baked in, so they boot straight into a working state</strong> and skip the entire installer interaction.</p><p>The two formats complement each other for different runtime environments:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bCVCj3XT8dOlqCnx8SuUGg.png" /></figure><blockquote><em>The ISO installer still fits production rollouts and brand-new hardware. qcow2/OVA are the lighter path for evaluation, PoC, and lab environments.</em></blockquote><h3>Before You Start: What You’ll Need</h3><p>The bar is low — a single VM can act as the management node. Create it with these settings:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1006/1*hoL0xNHCahiXk34DpBzdWA.png" /></figure><p>One easy pitfall to avoid: <strong>running virtualization inside a VM requires nested virtualization support from the hypervisor.</strong> On VMware, when creating or importing the VM, check <em>Expose hardware assisted virtualization to the guest OS</em> in the processor settings. VirtualBox, KVM, and cloud hosts each have their own toggle, covered in the scenarios below.</p><h3>Scenario 1: VMware with OVA</h3><p>OVA is the most natural format for the VMware ecosystem.</p><ol><li>Download the .ova file from the <a href="https://zsvirt.io/download/">download center</a>;</li><li>In VMware Workstation, choose <strong>File → Open</strong> and select the downloaded OVA to import it;</li><li>Edit the VM settings and confirm CPU and memory meet the requirements (the OVA ships with <strong>16 vCPUs / 16 GiB</strong> by default; keep or adjust as needed);</li><li>Under <strong>Processors</strong>, check <strong>Virtualize Intel VT-x/EPT or AMD-V/RVI</strong> (the equivalent ESXi option is <em>Expose hardware assisted virtualization to the guest OS</em>);</li><li>Power on, open the console, and proceed to initialization below.</li></ol><h3>Scenario 2: KVM/QEMU with qcow2</h3><p>qcow2 is the native KVM/QEMU format — attach it directly as a disk.</p><p>When creating a VM in virt-manager, choose <strong>Import existing disk image</strong>, point to the downloaded qcow2 file, allocate 8 vCPUs / 8 GiB, and boot. The same works from the command line with virt-install:</p><pre>virt-install \<br>  --name zsvirt-mn \<br>  --vcpus 8 \<br>  --memory 8192 \<br>  --disk path=/var/lib/libvirt/images/ZSvirt-x86_64-&lt;version&gt;-h84r.qcow2,format=qcow2,device=disk \<br>  --network network=default \<br>  --import</pre><p>If virtualization doesn’t work inside the guest, first confirm nested virtualization is enabled on the host:</p><pre>cat /sys/module/kvm_intel/parameters/nested   # Intel<br>cat /sys/module/kvm_amd/parameters/nested     # AMD</pre><p>An output of 1 or Y means it&#39;s enabled; otherwise, add nested=1 to the KVM kernel module and reload it.</p><h3>Scenario 3: VirtualBox and Cloud Hosts</h3><p><strong>VirtualBox</strong>: the easiest path is OVA — <strong>File → Import Appliance</strong>, then select the downloaded OVA. After importing, enable <strong>Nested VT-x/AMD-V</strong> under <strong>System → Processor</strong>.</p><p><strong>Cloud hosts</strong>: pick an <strong>instance type that supports nested virtualization</strong> (offerings vary by provider — typically bare-metal or specific performance instance families). Create a cloud host from the qcow2 as its system disk, or upload it to the image service first and create an instance from it.</p><h3>First Boot and Initialization</h3><p>Whatever the environment, initialization after first boot is the same.</p><p><strong>Step 1: Log in and change the password.</strong> Press Ctrl+Alt+F2 in the console to switch to the login terminal and sign in as root. The default password is zsvirt.123 — run passwd right after logging in and change it. That&#39;s a habit worth keeping in any environment.</p><p><strong>Step 2: Configure the network and start the services.</strong> Two cases:</p><p><strong>When the management network has DHCP</strong>, first check the address the NIC picked up:</p><pre>ip addr</pre><p>Write the address into the management-node config and start the services:</p><pre>zstack-ctl change_ip --ip &lt;management-node-ip&gt;<br>zstack-ctl start</pre><p><strong>Without DHCP</strong>, create a bond and assign a static address manually:</p><pre># Create bond0<br>zs-bond-ab -c bond0</pre><pre># Add the management NIC to bond0<br>zs-nic-to-bond -a bond0</pre><pre># Assign a static address to bond0 (IP, netmask, gateway, in that order)<br>zs-network-setting -i bond0 &lt;management-node-ip&gt; &lt;netmask&gt; &lt;gateway&gt;</pre><p>Once networking is ready, run zstack-ctl change_ip --ip &lt;management-node-ip&gt; and zstack-ctl start to finish initialization.</p><p><strong>Step 3: Open the web UI.</strong> Point your browser at https://&lt;management-node-ip&gt; and follow the wizard to initialize the platform, then add hosts, storage, and networks and create your first VM. For the full flow, follow the <a href="https://zsvirt.io/blog/zsvirt-quickstart-deploy-your-first-vm">quick-start tutorial</a>.</p><h3>Going Further: The Same Image Can Act as a Compute Node</h3><p>If you only need this node as a compute node joining an existing cluster, you can skip the zstack-ctl change_ip and zstack-ctl start steps — the image supports that use case too. A management node, by contrast, runs the full control-plane services.</p><h3>Troubleshooting Cheat Sheet</h3><p>SymptomCheck firstUI won’t loadIs the VM running? Is the management NIC attached to the right network?Wrong IP / netmask / gatewayWas zstack-ctl change_ip --ip &lt;management-node-ip&gt; run with the correct value?Services not startedWas zstack-ctl start run, and did you wait for startup to finish?No external accessCan a workstation or another host reach the management-node IP? Is port 443 open in the firewall?Virtualization unavailableIs nested virtualization enabled on the hypervisor? (see scenarios above)</p><p>More detailed troubleshooting is in the docs: <a href="https://docs.zsvirt.io/en/docs/quick-start/nested-virtualization-management-node">Nested Virtualization Management Node</a>.</p><h3>What’s Next</h3><ul><li><a href="https://zsvirt.io/download/">Download the qcow2 / OVA images</a></li><li>Follow the <a href="https://zsvirt.io/blog/zsvirt-quickstart-deploy-your-first-vm">quick-start tutorial</a> to create your first VM</li><li>Migrating from VMware? Read <a href="https://zsvirt.io/blog/zmigrate-workflow-walkthrough">ZSvirt Migration in Practice: Three Ways to Migrate VMs</a></li><li>For a systematic evaluation, work through the <a href="https://zsvirt.io/blog/evaluate-zsvirt-as-a-vmware-alternative">PoC guide</a></li></ul><p>We’ve always believed a good evaluation should start at the lowest possible cost. Now, a single VM is enough.</p><h3>Join the Community</h3><ul><li><strong>Issue tracker</strong>: <a href="https://github.com/zsvirt/zsvirt/issues">GitHub Issues</a></li><li><strong>Community discussions</strong>: <a href="https://github.com/ZSvirt/zsvirt/discussions">GitHub Discussions</a></li><li><strong>Social media</strong>:</li><li>YouTube: <a href="https://youtube.com/@ZSvirt">https://youtube.com/@ZSvirt</a></li><li>LinkedIn: <a href="https://www.linkedin.com/in/zsvirt-community/">https://www.linkedin.com/in/zsvirt-community/</a></li><li>X/Twitter: <a href="https://x.com/ZSvirt">https://x.com/ZSvirt</a></li><li>Discord: <a href="https://discord.com/invite/KHsw63z9xA">https://discord.com/invite/KHsw63z9xA</a></li><li>Email: <a href="https://community@zsvirt.io/">community@zsvirt.io</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=56f8f215d95a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Virtualization Watch Issue 002: VMware Explore 2026, Proxmox 24/7 Support]]></title>
            <link>https://zsvirt.medium.com/virtualization-watch-issue-002-vmware-explore-2026-proxmox-24-7-support-70e9ebaef760?source=rss-16d9dff0f9c7------2</link>
            <guid isPermaLink="false">https://medium.com/p/70e9ebaef760</guid>
            <category><![CDATA[vmware]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[virtualization]]></category>
            <category><![CDATA[proxmox]]></category>
            <dc:creator><![CDATA[ZSvirt Community]]></dc:creator>
            <pubDate>Tue, 15 Sep 2026 09:23:45 GMT</pubDate>
            <atom:updated>2026-09-15T09:23:45.932Z</atom:updated>
            <content:encoded><![CDATA[<p>September 14, 2026 · Biweekly · Coverage window: 9/1–9/13</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wH30jbu8N8sQxZf7GyeUXw.png" /></figure><h3>From the Editor</h3><p>Hello, readers — welcome to Issue 002 of Virtualization Watch.</p><p>The past two weeks were the densest fourteen days of the quarter for virtualization: VMware Explore 2026 opened in Las Vegas on August 31 and wrapped on September 3, with Broadcom pushing “Private AI Cloud” to the very front of the private-cloud narrative; in the same week, Proxmox announced 24/7 enterprise support and a North American subsidiary back to back, then earned Omnissa Horizon certification — the open-source camp’s commercialization is visibly accelerating. The security side was heavier: a CVSS 9.3 VM-escape vulnerability hit Workstation/Fusion, and Microsoft’s September Patch Tuesday set an all-time record with 974 fixes, five of them in Hyper-V alone.</p><p>As AI workloads become the centerpiece of every roadmap, hypervisor competition is shifting from “running VMs” to “running models well on GPUs.” Let’s begin.</p><h3>In This Issue: VMware Explore 2026 — AI Factory Debuts, vSphere 9.1 Earns NVIDIA Certification</h3><p>VMware Explore 2026 ran August 31 — September 3 at The Venetian Convention and Expo Center in Las Vegas (<a href="https://www.vmware.com/explore/us">VMware event page</a>). Our news window covers every official announcement from the show; the two weightiest are <strong>VMware AI Factory</strong> and <strong>NVIDIA certification for vSphere 9.1</strong> (<a href="https://blogs.vmware.com/cloud-foundation/2026/09/03/explore-2026-vmware-ai-factory-and-other-new-ai-innovations-in-vcf/">VMware official blog, September 3, 2026</a>).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*P4FcnC8bUlTld-p7.png" /></figure><p>Key points:</p><ul><li><strong>VMware AI Factory</strong>: positioned as the software-defined foundation of the “VMware Private AI Cloud,” aiming to compress the time from bare-metal servers to a first production AI model “from weeks to hours,” spanning hardware provisioning, software-stack enablement, and full lifecycle management.</li><li><strong>Ecosystem and hardware</strong>: works with Dell PowerEdge certified servers and VCF AI ReadyNodes from Cisco, Lenovo, Supermicro, and others; a partnership with AMD delivers zero-touch provisioning of Instinct GPUs with the open ROCm stack; a separate partnership with <strong>MetalSoft</strong> integrates heterogeneous bare-metal automation directly into the VCF management console.</li><li><strong>Model runtime</strong>: vLLM is the default model runtime, with 150+ open models; models officially named as tested on VCF include NVIDIA Nemotron 3, Google Gemma 4, NEC cotomi, Alibaba Qwen3.8–27B, and Zhipu GLM 5.2.</li><li><strong>NVIDIA certification</strong>: NVIDIA recently launched the NVIDIA-Certified Hypervisors program, and <strong>vSphere 9.1 (and all subsequent vSphere 9 releases) are among the first certified</strong>, with official claims of “near bare-metal” performance for AI/HPC workloads on VCF.</li><li><strong>Private AI services ecosystem additions</strong>: Appian, ClearML, Eve Security, Solo.io, and TrueFoundry.</li></ul><p><strong>Editor’s take</strong>: this year’s Explore barely discussed “virtualization” itself — every announcement targeted the private cloud in the Agentic AI era. Broadcom’s logic is straightforward: GPUs are expensive, token costs are spiraling, and data must stay on-premises — all three are the private cloud’s home turf. For enterprise users, what truly needs evaluation is not the AI Factory concept, but whether the GPU supply chain works smoothly after upgrading an existing VCF environment to 9.1.</p><h3>Product &amp; Version News</h3><h3>VMware Cloud Foundation 9.1.1 Reaches GA (September 3)</h3><p>Timed with Explore 2026, Broadcom announced the <strong>general availability of VCF 9.1.1</strong> (<a href="https://blogs.vmware.com/cloud-foundation/2026/09/03/announcing-general-availability-of-vmware-cloud-foundation-9-1-1/">official blog</a>) — the first maintenance release of VCF 9.1 (released in May). Highlights:</p><ul><li><strong>Multi-tenant model sharing</strong>: AI models can be securely shared across tenants/business units, while training data and access controls remain tenant-isolated, cutting duplicate deployment costs;</li><li><strong>AI Assistant for VCF</strong>: AI-assisted diagnostics (e.g., ESX CPU/memory contention, locating batch vMotion errors) and management-pack building;</li><li><strong>vSAN Object Storage</strong> (tech preview) and cumulative security fixes.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*t0At3NuDa6pl6Ifs.png" /></figure><p>Note the upgrade-order constraints: William Lam’s blog post (<a href="https://williamlam.com/2026/09/10-exciting-enhancements-in-vmware-cloud-foundation-9-1-1.html">analysis published September 10</a>) reminds readers that Fleet LCM must be upgraded to 9.1.1 before all other components, VCFMS must go before Identity Broker and Salt Master/RaaS, and VCF Automation before VCD Migrator (the corresponding pre-checks are built into the release).</p><h3>VMware Workstation / Fusion 26H1u1 (September 3)</h3><p>The desktop hypervisor line shipped 26H1u1, whose core purpose is fixing the two vulnerabilities in VMSA-2026–0007 (see “Security Advisories”), while also introducing <strong>automated Secure Boot platform key (PK) remediation</strong> to address the Microsoft Secure Boot certificate expiration (<a href="https://techdocs.broadcom.com/us/en/vmware-cis/desktop-hypervisors/fusion-pro/26H1/release-notes/vmware-fusion-26h1u1-release-notes.html">Fusion 26H1u1 release notes, Broadcom TechDocs</a>).</p><h3>Proxmox: Two Announcements in One Week — 24/7 Support + North America Subsidiary (September 2), Omnissa Certification (September 4)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*tsRJGhtHW4VnxoE_.png" /></figure><p>On September 2, Proxmox Server Solutions announced (<a href="https://www.proxmox.com/en/about/company-details/press-releases/proxmox-24-7-support-and-proxmox-north-america">official press release</a>):</p><ul><li>Enterprise support expands to <strong>24/7</strong>, effective October 19, 2026, covering the PVE, PBS, and PDM product lines; the Premium tier includes 24/7 from day one (unlimited tickets, 2-hour response for critical issues), the Standard tier opens in Q4 2026, and the Basic tier’s SLA is unchanged though the global team’s cross-timezone shifts will shorten real-world response times;</li><li>A new subsidiary, <strong>Proxmox North America Inc.</strong>, headquartered in Kingston, Ontario, Canada, led by CEO Bill Hughes, handling sales, contracts, and business-hours technical support across North American time zones;</li><li>Operating figures disclosed alongside: over <strong>2.3 million</strong> active PVE servers worldwide, 60,000+ enterprise customers with paid support, and roughly 3,000 integration partners.</li></ul><p>On September 4, Proxmox announced (<a href="https://www.proxmox.com/en/about/company-details/press-releases/proxmox-ve-omnissa-horizon-ready">official press release</a>) that <strong>Proxmox VE has officially passed Omnissa Horizon Ready Hypervisor certification</strong>: interoperating with Omnissa Horizon in Manual Provisioning Mode, enterprises can centrally deliver virtual desktops and applications on existing PVE infrastructure; PVE also appears on the <strong>NVIDIA vGPU</strong> support list as a certified third-party hypervisor. Verified configurations are in the <a href="https://interopmatrix.omnissa.com/Compatibility/hypervisors/">Omnissa interoperability matrix</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*XK_mX_uLQuQyOlRm.png" /></figure><p><strong>Editor’s take</strong>: from official Arm64 support on August 5, to this issue’s 24/7 support and VDI ecosystem certification, Proxmox’s “catch the spillover” playbook under Broadcom’s licensing squeeze is becoming systematic — first it caught the migrations, then the services, and now even the VDI desktop cloud.</p><h3>Nutanix Lands in Two Gartner Magic Quadrants in a Fortnight (September 8 / September 10)</h3><p>Per the Nutanix newsroom (<a href="https://www.nutanix.com/newsroom">official Newsroom</a>): on September 10, Nutanix was named a <strong>Leader in the 2026 Gartner Magic Quadrant for Distributed Hybrid Infrastructure</strong> (on both Ability to Execute and Completeness of Vision); on September 8, it appeared for the second consecutive year in the <strong>Gartner Magic Quadrant for Container Management</strong> (the official blog headline positions it as a “Challenger”).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*KIDlrzTV3Cz70MO3.png" /></figure><h3>KubeVirt v1.10.0-alpha.0 Released (September 4)</h3><p>The KubeVirt community published <strong>v1.10.0-alpha.0</strong> on GitHub (<a href="https://github.com/kubevirt/kubevirt/releases/tag/v1.10.0-alpha.0">release page</a>): about five weeks after v1.9.0 (July 30), this cycle accumulated 824 changes from 72 contributors. Notable changes: the KubevirtSeccompProfile feature gate graduates to GA and is installed by default; ExternalNetResourceInjection graduates to GA, and virt-controller no longer queries NetworkAttachmentDefinition directly; SR-IOV interfaces can no longer be mixed with DRA networking.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*IehanVBmLBJYtADn.png" /></figure><h3>Release Footnotes from Outside the Window</h3><ul><li>No new VirtualBox release this issue; the latest remains 7.2.16 from August 18 (<a href="https://www.virtualbox.org/wiki/News">VirtualBox official News</a>);</li><li>QEMU 11.1 shipped on August 11 (UFS 4.1 emulation, RISC-V big-endian support) — before this window, for reference.</li></ul><h3>Community Buzz</h3><h3><a href="https://zsvirt.io/">ZSvirt</a> on Show HN: Lightweight Open-Source Virtualization Platform Draws 72 Points (September 2)</h3><blockquote><em>Editor’s disclosure: this newsletter is produced by the ZSvirt team; this item is related-party content and is disclosed as such. All figures below come from live captures of public pages.</em></blockquote><p>On September 2, the open-source virtualization platform <a href="https://github.com/zsvirt/zsvirt">ZSvirt</a> appeared on Hacker News’ Show HN: “Show HN: ZSvirt — A lightweight, scalable open source virtualization platform” (<a href="https://news.ycombinator.com/item?id=49536562">original HN post</a>). As of our September 13 capture, it had <strong>72 points and 14 comments</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*F1voy2O6A5PDygQf.png" /></figure><p>The comment section’s questions were strikingly focused, outlining the four things the community cares most about in an emerging virtualization platform:</p><ul><li><strong>Performance benchmarks</strong>: multiple users asked for benchmarks against Proxmox, standalone KVM, and OpenStack — VM boot time, migration speed, and control-plane overhead;</li><li><strong>VMware migration</strong>: the VMDK/OVF compatibility experience, and the networking/storage pitfalls when migrating from vSphere, were asked repeatedly;</li><li><strong>Networking capabilities</strong>: how hard VLAN and NAT configuration is compared with Proxmox;</li><li><strong>Lab barrier to entry</strong>: the minimum memory for running the OVA image under nested virtualization on a single node, plus the maturity of multi-tenant management and the API ecosystem.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*0Cs5rzWk-0hJ-GL4.png" /></figure><p>On the repository side (<a href="https://github.com/ZSvirt/zsvirt">GitHub: ZSvirt/zsvirt</a>): positioned as a “core IaaS engine and cloud infrastructure foundation,” built on KVM, written mainly in Java (78.2%), GPL-3.0 licensed, with <strong>1.7k stars and 306 forks</strong> as of our September 13 capture. Ready-made qcow2 and OVA images can be tried via nested virtualization on VMware, VirtualBox, KVM, or cloud hosts, and there is an online demo (demo.zsvirt.io). The repository has no formal release yet — worth tracking.</p><h3>vphone-cli Heats Up Again: iOS 27 RC in the Catalog, HN Post at 421 Points</h3><p>The open-source project <strong>vphone-cli</strong> (which boots a “virtual iPhone” on Apple Silicon Macs using Apple’s Virtualization.framework and the PCC research-VM infrastructure) saw a second wave of attention in this window:</p><ul><li>The Hacker News front-page thread from late August, “Boot a Virtual iPhone via Apple’s Virtualization.framework,” now sits at <strong>421 points and 113 comments</strong> (<a href="https://news.ycombinator.com/item?id=49485267">original HN post</a>), with comments still growing inside our window; the community consensus is that “this isn’t Corellium-style emulation — it’s real virtualization,” alongside a warning not to select Japan or the EU region during initialization (the VM cannot pass third-party app-store compliance checks);</li><li>On September 10, a repository commit added the <strong>iOS 26.6.2 + iOS 27.0 RC (cloudOS 26.4) pairing</strong>, with v1.0.14 released the same day; InfoQ covered the project’s full iOS 27 virtualization support on September 12, driving a fresh round of discussion;</li><li>As of our September 13 capture, the repository had <strong>11.8k stars and 1.5k forks</strong>, primarily Swift (58.6%).</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*-oQ2nCg9Hm9LZuU1.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*hxKiOLMRA_39o2bb.png" /></figure><p>The community’s main concerns are worth recording too: Apple does not officially support this usage, and future PCC images may remove necessary components; the host also requires loosening SIP/AMFI security policies — use a dedicated research machine.</p><h3>Proxmox VE 8 Officially EOL; the Upgrade Wave Continues</h3><p>Security support for Proxmox VE 8 ended on <strong>August 31</strong> (<a href="https://endoflife.date/proxmox-ve">endoflife.date</a>) — one day before this window — and community discussion of the 8-to-9 upgrade kept simmering throughout: the kernel jumps from 6.8 to 7.x, NICs may be renamed, LVM auto-activation defaults change, and PCI passthrough needs re-checking. Readers still on VE 8 can consult VirtualizationHowto’s <a href="https://www.virtualizationhowto.com/2026/08/still-running-proxmox-ve-8-heres-what-you-need-to-do-before-end-of-life/">upgrade checklist</a> — run pve8to9 --full first, pin NIC names, and have out-of-band console access ready.</p><h3>VMSA-2026–0007 Becomes the Fortnight’s Must-Do for Desktop Virtualization Users</h3><p>In the VirtualizationHowto community, the VMSA-2026–0007 <a href="https://www.virtualizationhowto.com/community/cybersecurity-forum/critical-vmware-workstation-and-fusion-vulnerability-vmsa-2026-0007-allows-vm-escape-code-execution/">discussion thread</a> is among the hottest: VMXNET3 is the default virtual NIC for most users, and “first inventory which dev and test machines have Workstation/Fusion installed” became the thread’s consensus — desktop hypervisors are rarely in the enterprise asset inventory, which is exactly what makes this vulnerability tricky in practice.</p><h3>Security Advisories</h3><h3>[Critical] VMSA-2026–0007: Workstation / Fusion VM Escape (September 3)</h3><p>Broadcom published VMSA-2026–0007 (<a href="https://blogs.vmware.com/security/">VMware Security Blog</a> | <a href="https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/38288">Broadcom official advisory</a>), affecting <strong>VMware Workstation 25H2/26H1 and Fusion 25H2/26H1 (macOS)</strong>; ESXi and vCenter are not affected:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*NRMfmTRvB2k3uA2-.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Sc2uPGbYqQM_FDQ7sDQtQw.png" /></figure><ul><li><strong>Fixed in</strong>: 26H1u1 (same version number for Workstation and Fusion); <strong>no workarounds</strong> — upgrading is the only option;</li><li>Both vulnerabilities were reported privately, and Broadcom is not aware of in-the-wild exploitation; reporters include h4urek of secsys lab, Y² and Stan S via Trend Micro ZDI, and Yeonghyeon Choi and Tianchu Chen of Tencent Xuanwu Lab;</li><li>CERT-FR issued a corresponding advisory on September 4;</li><li>A side note: 26H1u1 also introduces automated Secure Boot platform-key remediation — before upgrading, make sure guests have the July 2026-or-later Windows cumulative update installed (in combination with VMware Tools 13.1.5).</li></ul><p><strong>Recommended action</strong>: users who frequently run third-party images, analyze samples, or execute untrusted workloads on their machines should upgrade first. If you cannot upgrade immediately, disabling HGFS shared folders and tightening in-VM administrator privileges will shrink the attack surface (unofficial mitigation — reduces risk only).</p><h3>[Largest Ever] Microsoft September Patch Tuesday: 974 Vulnerabilities, Five in Hyper-V (September 8)</h3><p>Microsoft’s September 2026 Patch Tuesday fixed <strong>974 vulnerabilities</strong> (113 Critical, 860 Important), which Qualys calls “Microsoft’s largest security update ever” (<a href="https://blog.qualys.com/vulnerabilities-threat-research/2026/09/08/microsoft-patch-tuesday-september-2026-security-update-review">Qualys analysis, September 9</a>); two additional vulnerabilities are already being exploited in the wild.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*3bRX__IT8f_-1J_P.png" /></figure><p>Directly virtualization-relevant: <strong>five Hyper-V vulnerabilities</strong> (<a href="https://www.lansweeper.com/blog/patch-tuesday/microsoft-patch-tuesday-september-2026/">Lansweeper roundup</a>):</p><ul><li><strong>CVE-2026–80083</strong>: Hyper-V remote code execution (untrusted pointer dereference), Critical;</li><li><strong>CVE-2026–69603</strong>: Hyper-V remote code execution (heap buffer overflow), Critical;</li><li><strong>CVE-2026–69910</strong>: Hyper-V remote code execution, Critical;</li><li><strong>CVE-2026–72961</strong>: Hyper-V elevation of privilege (out-of-bounds read);</li><li><strong>CVE-2026–69553</strong>: Hyper-V elevation of privilege.</li></ul><p>Splashtop’s <a href="https://www.splashtop.com/blog/patch-tuesday-september-2026">patch-priority analysis</a> (September 9) places Hyper-V, Failover Clustering, and Windows Deployment Services in the “patch within 72 hours” tier — once a host is compromised, every guest workload on it is exposed. A VHD Miniport driver denial-of-service flaw (CVE-2026–69384) was fixed alongside; include it in your host patching window.</p><h3>Tools &amp; Good Reads</h3><ul><li><strong>vphone-cli</strong> (<a href="https://github.com/Lakr233/vphone-cli">GitHub</a>, MIT license): a single command runs the whole pipeline — download firmware → patch → DFU restore → install the customized firmware → first boot — with SSH/VNC access and five security-bypass variants (from patchless to full jailbreak); the companion <strong>vphone-mcp</strong> wraps the control socket as an MCP service, letting AI agents take screenshots, drive touch input, and automate UI testing. Once again: SIP/AMFI must be loosened — dedicated research machines only.</li><li><strong>“10 Exciting Enhancements in VMware Cloud Foundation 9.1.1”</strong> (<a href="https://williamlam.com/2026/09/10-exciting-enhancements-in-vmware-cloud-foundation-9-1-1.html">William Lam, September 10</a>): ten detailed enhancements in VCF 9.1.1 plus upgrade-order caveats, written on-site at Explore by a Broadcom frontline engineer.</li><li><strong>“Still Running Proxmox VE 8?”</strong> (<a href="https://www.virtualizationhowto.com/2026/08/still-running-proxmox-ve-8-heres-what-you-need-to-do-before-end-of-life/">VirtualizationHowto, August 19</a>): the pre-EOL upgrade checklist and version support matrix — read together with this issue’s “Community Buzz.”</li><li><strong>“Microsoft and Adobe Patch Tuesday, September 2026 Security Update Review”</strong> (<a href="https://blog.qualys.com/vulnerabilities-threat-research/2026/09/08/microsoft-patch-tuesday-september-2026-security-update-review">Qualys, September 9</a>): a panoramic breakdown of the 974 vulnerabilities with tiered patching advice.</li><li><strong>Broadcom TechDocs: Workstation / Fusion 26H1u1 release notes</strong> (<a href="https://techdocs.broadcom.com/us/en/vmware-cis/desktop-hypervisors/fusion-pro/26H1/release-notes/vmware-fusion-26h1u1-release-notes.html">link</a>): official details on the CVE fixes and Secure Boot PK remediation.</li></ul><h3>Number of the Week: 974</h3><p>The total number of vulnerabilities fixed in Microsoft’s September 2026 Patch Tuesday — 113 Critical, 860 Important, plus two zero-days exploited in the wild. Qualys confirms it is Microsoft’s largest single-month security update ever (July had 570, August 400). Six are virtualization-related: five in Hyper-V (three Critical RCEs + two elevation-of-privilege) and one in the VHD Miniport driver.</p><h3>Next Issue Preview</h3><ul><li><strong>October 19</strong>: Proxmox 24/7 enterprise support goes live — we’ll watch the Standard tier’s rollout pace and how the SLA lands in practice;</li><li><strong>KubeVirt v1.10 stable</strong>: alpha.0 froze 824 changes; the stable release is expected to follow the Kubernetes 1.37 cadence — we will keep tracking;</li><li><strong>October Patch Tuesday (October 13)</strong>: will the 974 record be broken? Hyper-V and the VHD components deserve continued attention;</li><li>Once VMware AI Factory’s follow-up technical documentation and MetalSoft integration details are released, we will publish a hands-on analysis.</li></ul><p><strong>About this publication</strong>: Virtualization Watch (VirtWatch Weekly) is a biweekly virtualization industry publication produced by the ZSvirt community, covering product news, security advisories, and community discussion across VMware/Broadcom, Proxmox, KVM/QEMU, Hyper-V, KubeVirt, Nutanix, and more. It is compiled with AI-cluster assistance; every fact is linked to its source; we aim for balanced viewpoints and welcome corrections. All factual content in this issue was verified against primary sources (official press releases, official blogs, GitHub release pages, original HN posts, etc.), with key source pages captured by the editors. News window: September 1–13, 2026; editorial deadline: September 13, 2026. Visit <a href="https://zsvirt.io/">zsvirt.io</a> for past issues and the video edition.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=70e9ebaef760" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Evaluating ZSvirt as a VMware Alternative: A PoC Guide from Deployment to Migration]]></title>
            <link>https://zsvirt.medium.com/evaluating-zsvirt-as-a-vmware-alternative-a-poc-guide-from-deployment-to-migration-d6e7f8773e3b?source=rss-16d9dff0f9c7------2</link>
            <guid isPermaLink="false">https://medium.com/p/d6e7f8773e3b</guid>
            <category><![CDATA[virtualization]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <dc:creator><![CDATA[ZSvirt Community]]></dc:creator>
            <pubDate>Wed, 09 Sep 2026 14:06:00 GMT</pubDate>
            <atom:updated>2026-09-09T14:06:00.973Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6i_SVYX0USC-Cgusd3ZN9Q.png" /></figure><p><em>Over the past few weeks, we announced </em><a href="https://github.com/zsvirt/zsvirt/"><em>ZSvirt</em></a><em>’s open-source release, shared the reasoning behind it, walked you through creating your first VM, broke down the architecture of the production-proven engine, and covered the full workflow of migrating VMs from VMware. Today, we zoom back out to the evaluation itself: when you’re seriously considering </em><a href="https://zsvort.io/"><em>ZSvirt</em></a><em> as a replacement for your current virtualization environment, where should you start validating?</em></p><p>When you’re looking for a VMware alternative, creating and booting a single VM only verifies the most basic compute path.</p><p>A complete evaluation also needs to cover the operations ecosystem that wraps around VMs: how hosts and clusters are managed, how storage and networking are attached, how permissions are assigned, how failed tasks are recovered, and how existing VMware workloads get migrated.</p><p>This post lays out a PoC path that you can actually execute in your environment. When you’re done, you should be able to answer one specific question:</p><blockquote><em>Can ZSvirt take over our current virtualization environment given our hardware, network, storage, and workloads?</em></blockquote><h3>Before You Start: Define What You’re Replacing</h3><p>“Replacing VMware” involves a whole set of infrastructure capabilities.</p><p>For teams running only a handful of VMs, the evaluation may center on the Linux and Windows workloads on their existing servers. For larger infrastructure teams, it also means cluster management, shared storage, distributed networking, access control, automation interfaces, high availability, and migration flows.</p><p>So a PoC can start by documenting your current environment.</p><p>At minimum, gather the following:</p><ul><li>The number of vCenters, clusters, hosts, and VMs;</li><li>CPU architecture, generations, and your hardware retention plan;</li><li>Virtual disk sizes, snapshots, and sustained write patterns;</li><li>VLANs, address allocation, security policies, and external network dependencies;</li><li>Linux, Windows, and special OS versions;</li><li>How backup, monitoring, audit, and automation systems connect;</li><li>Workloads that can tolerate downtime, and those that need a shorter cutover window.</li></ul><p>This checklist will determine the scope of everything that follows. Every VMware environment has a different resource structure and set of business dependencies, so the migration decision has to be made in the context of your actual situation.</p><h3>Step 1: Stand Up the Minimal Resource Path</h3><p>The most direct way to start evaluating ZSvirt is to stand up a minimal environment by following the <a href="https://zsvirt.io/blog/zsvirt-quickstart-deploy-your-first-vm">first-VM deployment guide</a>.</p><p>For testing, a single server can act as both the management node and a compute node. After the ISO install, create a datacenter and cluster in sequence, add hosts, data storage, image storage, a distributed switch and port groups, and finally create your first VM.</p><p>Once the VM is “Running”, keep checking that all the pieces cooperate:</p><ol><li>Can the host stay connected to the management node?</li><li>Can images be uploaded and used to create VMs?</li><li>Can virtual disks be created, attached, and deleted?</li><li>Does the VM get the expected address?</li><li>Are the gateway, external address, and DNS resolution working?</li><li>Does the console open?</li><li>Do shutdown, start, reboot, and delete operations leave clear task records?</li></ol><p>Only after you confirm that the compute, storage, network, image, and VM paths all work should you move on to cluster and migration tests. That way, when something goes wrong later, you can tell faster whether the problem is platform configuration, infrastructure conditions, or the migration process.</p><h3>Step 2: Verify Day-to-Day Operations</h3><p>The long-term experience of a virtualization platform shows up in the day-to-day changes you make over years.</p><p>In your PoC environment, keep doing the following:</p><ul><li>Expand a virtual disk;</li><li>Add and remove data disks;</li><li>Create, restore, and delete snapshots;</li><li>Modify a VM’s compute spec;</li><li>Adjust network configuration;</li><li>Migrate a VM to another host;</li><li>Simulate an operation failing halfway through;</li><li>Inspect the rollback and error messages of a failed task.</li></ul><p>ZSvirt handles long-running operations with async tasks, stateless services, and a workflow engine. Take creating a VM: underneath, it may involve scheduling a compute node, preparing an image, creating disks, configuring networking, and generating the VM config. If any step fails, it can leave behind resources that were created but are no longer needed.</p><p>The workflow engine breaks such operations into executable, rollback-able steps. For more on these mechanisms, see <a href="https://zsvirt.io/blog/zsvirt-architecture">ZSvirt Architecture</a> Explained and the <a href="https://zsvirt.io/blog/workflow-engine">workflow engine design</a>.</p><p>In your PoC, deliberately cause a controlled failure — for example, an unavailable storage path or wrong network parameters — and observe:</p><ul><li>Which step the task stops at;</li><li>What error the UI and API return;</li><li>Whether completed steps are cleaned up;</li><li>Whether orphaned disks or leftover config are produced;</li><li>Whether you can re-run after fixing the issue.</li></ul><p>This test shows you directly how the platform handles and recovers from abnormal situations.</p><h3>Step 3: Validate Storage and Networking Separately</h3><p>In a virtualization replacement project, storage and networking often decide the final stability and operational complexity.</p><h3>Storage Validation</h3><p>Seeing a storage type in the config page only means the platform offers that integration entry. Real validation should also include:</p><ul><li>mporting images and creating VMs from them;</li><li>Creating and attaching system and data disks;</li><li>Snapshots and recovery;</li><li>Cross-host migration on shared storage;</li><li>State after a host or storage path failure;</li><li>Latency and throughput under typical workload;</li><li>Time required for backup and recovery.</li></ul><p>If your production environment uses SAN, NFS, Ceph, or another storage system, test with the devices you plan to keep. Local disks are fine for standing up a minimal environment, but results there don’t directly represent how shared storage will behave.</p><h3>Networking Validation</h3><p>Pick a VLAN and address range close to production and verify:</p><ul><li>Distributed switch and port group configuration;</li><li>DHCP or static address allocation;</li><li>Whether VLAN and physical switch config match;</li><li>Network connectivity after a VM migrates across hosts;</li><li>Where security rules apply and their effective scope;</li><li>The traffic path after a host or network component state change.</li></ul><p>When a network fault occurs, administrators should be able to answer three questions: where traffic enters, where rules are enforced, and which layer to start troubleshooting from.</p><p>If the traffic path and rule locations are still unclear, the validation isn’t done yet.</p><h3>Step 4: Verify Permissions, Auditing, and Automation</h3><p>For environments managed by multiple people, in addition to the Web UI experience, verify permission boundaries, audit records, and automation APIs.</p><p>Create at least two kinds of test accounts:</p><ul><li>A day-to-day operator with basic VM permissions;</li><li>An administrator who can manage hosts, storage, networking, and accounts.</li></ul><p>Check what each account type can view and execute in both the UI and API, and confirm that denied operations leave a record.</p><p>Then run a minimal automation path through the API:</p><ol><li>Query hosts, storage, networking, and images;</li><li>Create a VM;</li><li>Query the async task status;</li><li>Tag a resource;</li><li>Read operation results and audit records;</li><li>Deliberately submit a bad parameter and check the response.</li></ol><p>ZSvirt provides RESTful/OpenAPI endpoints plus a Terraform provider and Go, Python, and Java SDKs. Your PoC should confirm that existing portals, scripts, ITSM, monitoring, or asset systems can reliably call these interfaces. For the capabilities and open-source scope, see <a href="https://zsvirt.io/blog/why-we-open-sourced-zsvirt">Why We Open Sourced ZSvirt</a>.</p><h3>Step 5: Start Migration with a Single Non-Critical VM</h3><p>Once the base platform validation is done, start testing VMware migration.</p><p>ZSvirt currently offers three common migration paths:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1020/1*C2AHBRBcSGVQ2AzYFskkJA.png" /></figure><p>For the full procedures, see <a href="https://zsvirt.io/blog/zmigrate-workflow-walkthrough">ZSvirt Migration in Practice: Three Ways to Migrate VMs from VMware</a>.</p><p>For the first test, avoid critical production systems — but also avoid a completely idle demo VM. A better candidate is a Linux or Windows VM that runs real services, has sustained disk writes, and can be rolled back.</p><p>A complete migration should at least record:</p><ul><li>Initial data volume and sync duration;</li><li>Source VM load during incremental sync;</li><li>The final cutover window;</li><li>Target VM first boot time;</li><li>Whether IP, routing, and security policies are correct;</li><li>Application services, file system, and database consistency;</li><li>Retry and rollback options after a failed migration;</li><li>Final confirmation from the application owner.</li></ul><p>Even after a migration task hits 100%, you still need to validate the business on the target platform and confirm your team can roll back in an abnormal situation.</p><h3>A Suggested PoC Checklist</h3><p>Before discussing production replacement, complete at least these ten tests:</p><ol><li>Deploy the ZSvirt management node from the ISO;</li><li>Create a datacenter and cluster, and add hosts;</li><li>Configure images, data storage, and virtual networking;</li><li>Create and run both Linux and Windows VMs;</li><li>Verify the console, address allocation, and external networking;</li><li>Test disk attach, expansion, snapshots, and recovery;</li><li>Migrate a VM across hosts on shared storage;</li><li>Verify role permissions, operation records, and audit logs;</li><li>Create a VM via the API and track the async task;</li><li>Use ZMigrate to sync, validate, cut over, and rehearse rollback for one VMware VM. Every item should have a clear expected result, actual result, and owner. For failed items, also record where the logs are, how to recover, and whether the item blocks production migration.</li></ol><h3>How to Judge Your PoC Results</h3><p>Different virtualization scenarios place different demands on a platform.</p><p>If you only need to manage one server and a few experimental VMs, a full cluster control plane may be more than you need. If your team already runs a Kubernetes-native infrastructure model, you may also want to compare Kubernetes-based virtualization options. If your environment depends on specific VMware plugins or proprietary integrations, you’ll need to validate the replacement path separately.</p><p>ZSvirt is for teams that want to keep an operations model centered on clusters, hosts, VMs, storage, and networking, while also needing open source, an open API, and a path to migrate from VMware.</p><p>After the PoC, form an internal conclusion around these questions:</p><ul><li>Can the existing hardware keep being used;</li><li>Can critical workloads run stably;</li><li>Can operators understand and troubleshoot the platform’s behavior;</li><li>Can automation and external systems integrate;</li><li>Do the migration windows and rollback flows meet business requirements.</li></ul><p>Once these validations are done, your team has a migration conclusion it can review internally, reproduce, and keep moving forward with.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d6e7f8773e3b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Virtualization Watch Issue 001: ZSvirt Core IaaS Engine Goes Open Source, VMware Explore 2026 Kicks…]]></title>
            <link>https://zsvirt.medium.com/virtualization-watch-issue-001-zsvirt-core-iaas-engine-goes-open-source-vmware-explore-2026-kicks-1b4fe5ad8649?source=rss-16d9dff0f9c7------2</link>
            <guid isPermaLink="false">https://medium.com/p/1b4fe5ad8649</guid>
            <category><![CDATA[proxmox]]></category>
            <category><![CDATA[virtual-machine]]></category>
            <category><![CDATA[virtualization]]></category>
            <category><![CDATA[nutanix]]></category>
            <category><![CDATA[vmware]]></category>
            <dc:creator><![CDATA[ZSvirt Community]]></dc:creator>
            <pubDate>Wed, 02 Sep 2026 06:27:58 GMT</pubDate>
            <atom:updated>2026-09-02T06:27:58.194Z</atom:updated>
            <content:encoded><![CDATA[<h3>Virtualization Watch Issue 001: ZSvirt Core IaaS Engine Goes Open Source, VMware Explore 2026 Kicks Off, Proxmox VE 8 Reaches EOL</h3><p>August 31, 2026 · Weekly · Coverage window: 8/26–8/31 (with August backfill)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oJ2anu6ejQ8VeSn6Y6IkFg.png" /></figure><h3>From the Editor</h3><p>The day Issue 001 goes to print lands squarely on the junction of several timelines: two weeks ago (August 14), this publication’s producer ZSvirt fully open-sourced its core IaaS engine, and this week it launched the Storytellers program aimed at creators — a “house matter” we’d like to explain to readers first; today (August 31), VMware Explore 2026 opens in Las Vegas, where Broadcom-era VMware will tell the “private AI cloud” story for another year; on the same day, Proxmox VE 8 officially reaches end of life, closing the book on one of the most widely deployed generations in the open-source camp. The enterprise giant’s annual show and the community distribution’s version hand-off each turn a new page on the same Monday.</p><p>Over the past two weeks, vCenter’s CVE-2026–59310 escalated from a “just-patched” advisory into an in-the-wild attack campaign spanning 47 countries — a reminder that security debt on the management plane always gets collected at the least convenient moment. Meanwhile in the community, vphone-cli — a tool that boots a virtual iPhone with a single command — hit the Hacker News front page, as virtualization keeps breaking out in small, elegant ways.</p><p>This week we chase no hype, only verified facts and sources. On to the stories.</p><h3>In This Issue</h3><h3>ZSvirt’s Core IaaS Engine Goes Open Source (GPL-3.0)</h3><p>On August 14, ZSvirt imported the full source code of its main repository to GitHub (ZSvirt/zsvirt) and open-sourced it under the GPL-3.0 license. It’s a “core IaaS engine and cloud infrastructure foundation”: the repo includes complete modules for compute, storage, network, identity, image, console, and portal; the primary languages are Java (78.2%) and Groovy (19.4%); and the repository topic tags span KVM, Proxmox, VMware/vSphere and more — positioning it directly against mainstream virtualization management stacks.</p><p>A little over two weeks after open-sourcing, the repository has gained <strong>1.5k Stars, 290 Forks, and 103 Watches</strong>. There is no formal Release yet — it’s in the “full code public, release cadence yet to start” phase, suitable for readers who want to follow the architecture and source code early by subscribing with a Watch.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*anOjt6J19G8JV3yYaru2FQ.png" /></figure><p>Alongside the open-source release, the community operations side has kicked off the <strong>“ZSvirt Storytellers — Phase 1: YouTube Challenge”</strong> (published August 28 in GitHub Discussion <a href="https://github.com/ZSvirt/zsvirt/discussions/8">#8</a>): record one ZSvirt-themed YouTube video and earn rewards tiered by views — $100 for ≥500 views, $150 for ≥1,000 views, $200 for ≥2,000 views, plus a +$20 bonus for the first creator from each region; limited to 20 participants, with submissions due September 28 and settlement on September 30. The baseline requirement is to fully demonstrate “from ISO install to dashboard up and running”; there are three optional advanced directions: comparison with Proxmox/VMware, migrating existing VMs from VMware/Proxmox, and a snapshot create-break-restore drill. One video per person; view-inflation disqualifies. Interested readers can sign up directly at Discussion #8.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eE8rRXn-H_pLjIRo7NOZ0w.png" /></figure><p>Sources: <a href="https://github.com/ZSvirt/zsvirt">GitHub: ZSvirt/zsvirt</a> · <a href="https://github.com/ZSvirt/zsvirt/discussions/8">Discussion #8: ZSvirt Storytellers — Phase 1: YouTube Challenge</a></p><h3>VMware Explore 2026 Opens Today in Las Vegas (8/31–9/3)</h3><p>VMware’s annual conference, Explore 2026, opens today at the Venetian in Las Vegas for a four-day run. Based on Broadcom’s official disclosure and VMware’s pre-show blog posts:</p><ul><li><strong>Scale</strong>: more than 400 breakout sessions, plus Hands-on Labs and certification courses;</li><li><strong>Keynote</strong>: the opening keynote is “Shaping the Future of Private AI Cloud and Agentic Innovation” (session PLE1837LV, 4:00 PM Pacific on 8/31), led by Ram Velaga, president of Broadcom’s Infrastructure Software Group, joined by Paul Turner, VP of Products for the VCF division, and Purnima Padmanabhan, GM of the Tanzu division — private AI cloud and agentic applications are the definitive through-line of this show. The general session is open only to Full Event Pass holders on a first-come, first-served basis, with overflow simulcasts at The Hub and Bellini 2103;</li><li><strong>Certification incentive</strong>: the Full Event Pass includes a VCAP exam voucher — a real subsidy for anyone pursuing certifications;</li><li><strong>Global tour</strong>: after Las Vegas, Explore on Tour heads to Mumbai (9/29–30), Singapore (10/1–2), Frankfurt (10/13–14), Tokyo (10/20–21), London (11/18–19), and Washington (12/8), wrapping up in Sydney on March 3–4, 2027.</li></ul><p>We will keep tracking VCF (VMware Cloud Foundation) releases and product announcements during the show and consolidate them in the next issue.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NNe4LFlqmGoccaUo9UeSgg.png" /></figure><p>Sources: <a href="https://investors.broadcom.com/news-releases/news-release-details/vmware-explore-2026-brings-technical-sessions-labs-and-certs-it">Broadcom IR: VMware Explore 2026 press release</a> · <a href="https://www.vmware.com/explore">VMware Explore 2026 official site</a></p><h3>Proxmox VE 8 Reaches End of Life Today</h3><p>Also on August 31, Proxmox VE 8 reaches the end of its official lifecycle. This generation, based on Debian 12 (Bookworm), was released in June 2023 and has been the workhorse platform for countless home labs and SMBs. Per Proxmox’s official support matrix, VE 8 support ends in August 2026 — today. Nodes still running 8.x should already be seeing the EOL banner in their web management UI.</p><p>The upgrade path isn’t complicated, but both official and community guidance stress “check first, then act”:</p><ol><li>Confirm backups are in place (PBS or offline copies);</li><li>Run the pve8to9 checker on every 8.x node, clearing blocking items one by one;</li><li>Follow the official upgrade documentation to roll each node up to VE 9 (based on Debian 13) — for clusters, upgrade standby nodes first, migrate workloads, then upgrade primary nodes.</li></ol><p>Virtualization Howto’s Brandon Lee reminded readers in his August 19 guide: don’t treat EOL as a countdown to immediate downtime, but don’t keep putting it off either — after EOL there are no more security updates, and the exposure surface only grows over time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LrMzX-DM0-QjptxCAgiUSQ.png" /></figure><p>Sources: <a href="https://www.virtualizationhowto.com/2026/08/still-running-proxmox-ve-8-heres-what-you-need-to-do-before-end-of-life/">Virtualization Howto upgrade guide</a> · <a href="https://pve.proxmox.com/wiki/FAQ">Proxmox VE lifecycle</a></p><h3>Product &amp; Version News</h3><h3>QEMU 11.1.1 / 11.0.4 / 10.0.13 Released on Three Lines in Sync (8/26)</h3><p>On August 26, QEMU shipped maintenance releases for three stable branches in sync: 11.1.1, 11.0.4, and 10.0.13 — all fix-oriented point releases, with source packages up on qemu.org signed with GPG. Shipping three lines on the same day is uncommon in QEMU’s release history; distributions and cloud platforms running multiple concurrent versions should check their changelogs and assess whether to track the updates.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8scXf20MuVqQKMIoNbEdJg.png" /></figure><p>Source: <a href="https://www.qemu.org/download/">QEMU official download page</a></p><h3>Nutanix FY2026 Q4 Earnings: ARR $2.55B, Up 16% YoY (8/26)</h3><p>Nutanix reported its fiscal Q4 (quarter ended July 31) and full-year FY2026 results: Q4 ARR of $2.55 billion (+16% YoY), quarterly revenue of $757.1 million (+16%), non-GAAP operating margin of 26.2% (up 790 basis points YoY), and free cash flow of $277.6 million; more than 3,000 net-new customers added during the year. CEO Rajiv Ramaswami called out new or deepened partnerships with AMD, Lenovo, NetApp, and NVIDIA, with AI and external storage support as key platform investment areas. With Broadcom’s channel policy tightening, Nutanix’s report is one of the most direct footnotes to the “VMware replacement” narrative.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*992mAlqlKV0lroPBac_2gw.png" /></figure><p>Source: <a href="https://ir.nutanix.com/news-releases/news-release-details/nutanix-reports-fourth-quarter-and-fiscal-2026-financial-results/">Nutanix IR press release</a></p><h3>Backfill</h3><ul><li><strong>Proxmox VE 9.2 brings first official Arm64 support (8/5)</strong>: in early August, Proxmox announced PVE officially landing on 64-bit ARM, delivered on VE 9.2, bringing ARM servers and edge devices into the official support matrix. The announcement was still pinned on r/Proxmox this week.</li><li><strong>VirtualBox 7.2.16 (mid-August)</strong>: Oracle shipped a 7.2-series maintenance update fixing multiple guest and network-stack issues.</li><li><strong>VMware Workstation 26H1 / Fusion 26H1 GA</strong>: r/vmware’s pinned announcement this week shows both desktop virtualization products reached GA with the 26H1 releases.</li></ul><p>Sources: <a href="https://www.proxmox.com/en/about/company-details/press-releases">Proxmox press release list</a> · <a href="https://www.reddit.com/r/vmware/top/?t=week">r/vmware pinned announcement</a></p><h3>Community Buzz</h3><h3>HN Front Page: Boot a Virtual iPhone with One Command (vphone-cli, 406 points / 111 comments)</h3><p>This week’s hottest virtualization-related post on Hacker News is “Boot a Virtual iPhone via Apple’s Virtualization.framework”: the open-source project vphone-cli uses the iOS kernel Apple ships in PCC (Private Cloud Compute)/cloudOS images, combined with the iOS userland and patches, to boot a “virtual iPhone” on Apple Silicon Macs via direct virtualization. The technical consensus in the HN thread: this isn’t a Corellium-style emulator — it’s real virtualization, and apps can easily tell it apart from a real device. Commenters also remind: don’t pick Japan or the EU region during setup (the VM can’t pass third-party app-store compliance checks). The repo has reached 9.7k Stars and 1.3k Forks, primarily in Swift.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7iBjt9C0tppkQp_CyMcMVA.png" /></figure><p>Sources: <a href="https://news.ycombinator.com/item?id=49485267">Hacker News discussion</a> · <a href="https://github.com/Lakr233/vphone-cli">GitHub: Lakr233/vphone-cli</a></p><h3>Reddit This Week</h3><ul><li><strong>r/Proxmox</strong>: the pinned post is indeed “Proxmox VE now available for 64-bit ARM (arm64)!” (551 votes / 119 comments) — community enthusiasm for ARM support exceeded expectations, with discussion focused on ARM server form factors beyond the Raspberry Pi and how to obtain images;</li><li><strong>r/vmware</strong>: the VMSA-2026–0006 patch discussion thread (88 votes / 148 comments) has effectively become the “patch exchange center,” with upgrade ordering and VCF-environment considerations as the main topics; two hands-on threads also ranked high — 100 GbE NIC tuning (a ConnectX-6 Dx only reaching 43 Gbit/s) and vCPU:pCPU oversubscription ratios.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BYPWKAk4NwSAsZafQZVc7w.png" /></figure><p>Sources: <a href="https://www.reddit.com/r/Proxmox/top/?t=week">r/Proxmox weekly top</a> · <a href="https://www.reddit.com/r/vmware/top/?t=week">r/vmware weekly top</a></p><h3>Security Advisories</h3><h3>Tracking VMSA-2026–0006: Timeline of CVE-2026–59310 Exploitation</h3><p>On July 29, Broadcom published VMSA-2026–0006 (updated to .2 on August 19), fixing five vulnerabilities across ESX / vCenter / Workstation / Fusion. Two of the vCenter flaws are both CVSS 9.8:</p><ul><li><strong>CVE-2026–59310</strong>: a directory-traversal vulnerability in the vCenter Syslog service that can be used for unauthenticated remote code execution;</li><li><strong>CVE-2026–59309</strong>: an authentication-bypass vulnerability in VMware Directory Service.</li></ul><p><strong>In-the-wild exploitation</strong>: German incident-response firm QUIRSO confirmed the attacks began on August 3 — just five days after disclosure. As of its August 10 report, 361 distinct victim IPs had been recorded across 47 countries, with Germany (55), the United States (41), Turkey (38), Iran (26), and France (25) accounting for about half. The attack chain: directory traversal to write and execute arbitrary code → plant cron jobs → launch the open-source reverse-shell framework reverse_ssh to establish outbound C2, bypassing defenses focused on inbound detection. The Cloud Security Alliance’s analysis note points out that because vCenter is the control plane of the entire virtualization environment, compromise means control over all managed hosts, VMs, and snapshots.</p><p><strong>Ransomware follow-up</strong>: The Hacker News reports that some attackers deployed Babuk-derived ransomware (.babyk) on compromised vCenters. QUIRSO attributes the campaign to Chinese-language-context attackers with “medium confidence” (based on Chinese traces in scripts, tool reuse, and UTC+8 operating rhythms). We’d note: attribution carries uncertainty, and 361 victim IPs do not equal 361 organizations.</p><p><strong>Remediation advice</strong>: the CVE has been added to CISA’s KEV catalog. Broadcom confirms there is no workaround — the only effective option is to upgrade to fixed versions: vCenter 9.1.0.0300, 9.0.2.0100, or 8.0 U3k/U2f. Security teams can prioritize hunting for: anomalous cron jobs, outbound reverse_ssh connections, and abnormal Syslog-service writes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bwS4-qQ7yhyeB99XGBw_EQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hvYeWLbeH0MzDF8WIf2qXQ.png" /></figure><p>Sources: <a href="https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/38017">Broadcom VMSA-2026–0006</a> · <a href="https://thehackernews.com/2026/08/suspected-china-nexus-actor-exploits.html">The Hacker News</a> · <a href="https://labs.cloudsecurityalliance.org/research/csa-research-note-vmware-vcenter-cve-2026-59310-exploitation/">CSA research note</a></p><h3>Tools &amp; Good Reads</h3><ul><li><strong>vphone-cli</strong>: boot iOS on Apple Silicon via virtualization with one command — this week’s most talked-about open-source project (see Community Buzz);</li><li><strong>ixui</strong>: a pre-alpha Incus web UI — “Proxmox’s skin, ESXi’s bones,” with hand-written React components, a cluster-aware instance tree, and a working SPICE console; fine for tinkering, not for production;</li><li><strong>Virtualization Howto’s PVE 8 EOL guide</strong>: the pre-EOL checklist and pve8to9 usage essentials;</li><li><strong>LWN: multikernel patch series</strong>: a proposal to run multiple Linux kernels simultaneously on one bare-metal machine hit the HN hot list, adding a new variable to the old “kernel-level isolation vs. virtualization” debate.</li></ul><p>Sources: <a href="https://github.com/Lakr233/vphone-cli">GitHub: vphone-cli</a> · <a href="https://github.com/xlmnxp/ixui">GitHub: ixui</a> · <a href="https://www.virtualizationhowto.com/2026/08/still-running-proxmox-ve-8-heres-what-you-need-to-do-before-end-of-life/">Virtualization Howto</a></p><h3>Number of the Week</h3><p><strong>47</strong> — the number of countries hit by the in-the-wild exploitation of CVE-2026–59310 (per QUIRSO’s August 10 report, 361 victim IPs). Only five days separated patch release from weaponization: the management-plane patch window is narrowing to days.</p><h3>Next Issue Preview</h3><p>A recap of announcements from VMware Explore 2026 (VCF version developments, private-AI-cloud products), feedback on Proxmox VE 9 upgrades, and more voices from the community frontline. See you next issue.</p><p><strong>About this publication</strong>: Virtualization Watch (VirtWatch Weekly) is a virtualization industry weekly produced by the ZSvirt community, published every Sunday, covering product news, security advisories, and community discussion across global virtualization and cloud infrastructure. It is compiled with AI-cluster assistance; every fact is linked to its source; we aim for balanced viewpoints and welcome corrections. Visit <a href="https://zsvirt.io/">zsvirt.io</a> for past issues and the video edition.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1b4fe5ad8649" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ZSvirt Migration in Practice: Three Ways to Migrate VMs from VMware]]></title>
            <link>https://zsvirt.medium.com/zsvirt-migration-in-practice-three-ways-to-migrate-vms-from-vmware-b3109fdc659e?source=rss-16d9dff0f9c7------2</link>
            <guid isPermaLink="false">https://medium.com/p/b3109fdc659e</guid>
            <category><![CDATA[vmware]]></category>
            <category><![CDATA[virtual-machine]]></category>
            <category><![CDATA[zsvirt]]></category>
            <category><![CDATA[virtualization]]></category>
            <dc:creator><![CDATA[ZSvirt Community]]></dc:creator>
            <pubDate>Thu, 27 Aug 2026 14:51:01 GMT</pubDate>
            <atom:updated>2026-08-27T14:51:01.085Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Over the past few days, we announced ZSvirt’s open-source release, shared the reasoning behind that decision, walked you through creating your first VM, and broke down the architecture of the production-proven engine. In this final post of the series, we turn our attention to migration — how to move your existing VMware VMs into ZSvirt smoothly.</em></p><p>VM migration is an unavoidable part of building or replacing a virtualization platform. ZSvirt offers a complete migration capability matrix, with three ways to migrate depending on your migration scale, business continuity requirements, and data shape:</p><ul><li><strong>ZMigrate migration service</strong>: an online migration option. Deploy the migration service and a data gateway to connect directly to source platforms such as VMware vSphere, fully syncing each VM’s OS and data to the target platform. It supports incremental sync, test-VM verification, and smooth cutover — a good fit for batch migration and scenarios with high business-continuity requirements.</li><li><strong>Import a VM</strong>: an offline import option. Export the source VM as an OVF template (OVF, VMDK, and MF files), then on the target platform use “New VM &gt; Import VM” to upload the template files and complete the import. Suited to a small number of VMs where a brief outage for export is acceptable.</li><li><strong>Upload a VMDK image</strong>: a disk-level migration option. Simply upload the VM’s VMDK disk file as a platform image (automatically converted to qcow2/raw), then create a VM from that image. It’s the lightest option, suited to scenarios that only need the disk data migrated.</li></ul><p>To help you choose, here’s a quick comparison:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/980/1*Q9V3VBR4wo_sLDVjjoBrOg.png" /></figure><p>Let’s walk through each of the three approaches below.</p><h3>1. ZMigrate Migration Service</h3><p>ZMigrate is ZSvirt’s online migration service. Its core idea is “sync first, cut over later”: while a migration task runs, the source VM keeps serving traffic as usual and its data is continuously synced to the target platform, until a cutover window switches the business over and downtime is compressed to the absolute minimum.</p><p>Before you can use ZMigrate, you first need to install the migration service. Go to “Operations &gt; Migration Service” to see the full workflow guide plus the basic and configuration info. The whole migration workflow can be summarized in six steps: <strong>download the installer from the official website → deploy ZMigrate → upload VDDK → add a data gateway → create the source platform → create the migration task</strong>, followed by the data sync and cutover stages.</p><h3>1.1 Download the Installer from the Official Website</h3><p>The migration journey starts on the official website. Go to the ZSvirt Resource Center, find ZMigrate for ZSvirt under the “Migration Tools” category, and download the installer for the version you need. The open-source version requires no license — download and go. Just confirm that the platform already has image storage configured, and that the image store has enough free space.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*MPnrcTsVO-KKiyYf.png" /></figure><p>Once the installer is downloaded, you can start deploying it in the platform.</p><h3>1.2 Deploy ZMigrate</h3><p>Deploying the migration service takes two steps: upload the installer package, then install.</p><p><strong>Upload the package</strong>: On the migration service page, click “Upload”. Both URL and local upload are supported, and you need to specify a storage path for the package and its extracted files. Make sure this directory has enough free space, and avoid system directories such as /, /dev, /proc, /sys, /usr/bin, /bin, and /opt — otherwise the install may fail or the server may behave abnormally.</p><p><strong>Install</strong>: After the upload finishes, click “Install” and choose an appropriate spec based on your needs. Key configuration items include:</p><ul><li><strong>Datacenter / Running location</strong>: ZMigrate is deployed as a VM-based data gateway; choose its datacenter and running location;</li><li><strong>CPU / Memory</strong>: 8 vCPU / 8 GB by default; the number of CPUs directly affects migration concurrency;</li><li><strong>Storage location / Disk</strong>: 100 GB system disk by default; specify a storage pool when the storage location is distributed storage;</li><li><strong>Migration network / IPv4 address</strong>: specify a distributed port group as the migration network; it must be reachable from both the source and target platform networks. When DHCP is enabled on the network, an IP is assigned automatically; otherwise specify one manually.</li></ul><p>Confirm and click OK; deployment of the migration service begins.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/799/0*Z5lKDLDGiXJj-KAn.png" /></figure><p>Deployment takes about 5–10 minutes. The page shows a “Deploying” status, so just wait.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*mIqyTg8pGbVgDWu4.png" /></figure><h3>1.3 Upload VDDK</h3><p>If the source platform is VMware, you also need to upload the VDDK (Virtual Disk Development Kit) package. ZMigrate reads disk data from VMware source VMs through the VDDK interface — an essential part of the VMware migration path. Click “Upload” on the migration service page and upload your prepared VDDK archive; the system loads it automatically once the upload succeeds.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*-X7SPvLbRrlcWpoA.png" /></figure><h3>1.4 Add a Data Gateway</h3><p>A data gateway is the relay between the source and target platforms and plays the key role in data transfer. It usually runs as a VM in the platform to provide gateway services, and you need to make sure it has network connectivity to the source platform, the target platform, and the migration service.</p><p>When you deploy ZMigrate, the platform creates a default data gateway. If you need to migrate VMs in batches, you can create additional data gateways to increase migration concurrency.</p><p>In the navigation bar, go to “Operations &gt; Migration Resources &gt; Data Gateways” and click “Add Data Gateway”. There are two ways to add one:</p><ul><li><strong>Create a new VM</strong>: the platform creates a VM to act as the data gateway. Key settings include:</li><li><strong>Datacenter / Running location</strong>: choose the datacenter and running location for the VM;</li><li><strong>CPU / Memory</strong>: 8 vCPU / 8 GB by default; adjust based on migration concurrency needs;</li><li><strong>Storage location / Disk</strong>: 100 GB system disk by default;</li><li><strong>Network / IPv4 address</strong>: specify a distributed port group; it must be reachable from the source and target platform networks. When DHCP is enabled, an IP is assigned automatically; otherwise specify one manually. When IP address management is enabled, a manually specified address must be within the selected network segment.</li><li><strong>Existing IP</strong>: if you already have a gateway VM, just enter its IP address. Once connected, the system automatically fetches the host name; click “Test” to check reachability.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*2-WucS7QXy-IWcRB.png" /></figure><p>Confirm and click OK; the data gateway is created.</p><h3>1.5 Create the Source Platform</h3><p>The source platform is the business platform to be migrated. When adding it, configure the following:</p><ul><li><strong>Name</strong>: set a name for the source platform;</li><li><strong>Data gateway</strong>: select a created data gateway, or directly enter a new gateway IP address;</li><li><strong>Platform type</strong>: VMware;</li><li><strong>vCenter/ESXi address</strong>: enter the VMware environment address;</li><li><strong>Username / Password</strong>: enter login credentials.</li></ul><p>After filling these in, click “Test” to run a connectivity check. Once the source platform and data gateway are both ready, you can start creating a migration task.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*8t73wkVSD7r3zwrB.png" /></figure><p>After creation, the source platform list shows the platform type, vCenter/ESXi address, associated data gateway, and connection status. A “Connected” status means the source platform is successfully integrated.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*cqlNmiI-qIXm7Nre.png" /></figure><h3>1.6 Create a Migration Task</h3><p>Creating a migration task has two steps:</p><ul><li><strong>Step 1</strong>: select the source platform and tick the source VMs you want to migrate.</li><li><strong>Step 2</strong>: configure the parameters of the migrated VMs — target datacenter, cluster, host, storage location, bus type, CPU mode, target network port group, and more — then fill in the cutover settings.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*_rJVI1oqvy0voCxQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*0InUk4yneJLnpfSo.png" /></figure><p>Cutover is the key step in the whole migration flow — once data sync completes, it stops the business on the old platform and smoothly switches it over to the new one. The cutover settings offer several practical options:</p><ul><li><strong>Cut over immediately</strong>: automatically cut over once the initial data sync completes;</li><li><strong>Create a rollback snapshot</strong>: create a snapshot of the target VM before cutover so you can roll back if anything goes wrong;</li><li><strong>Power off the source VM automatically</strong>: shut down the source VM before cutover to avoid IP conflicts;</li><li><strong>Install VMTools automatically</strong>: install VMTools automatically after the OS conversion completes.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*SZL7CQxsRONsiqn0.png" /></figure><p>Confirm and click OK; the migration task is created and its status enters “Syncing”.</p><h3>1.7 Sync and Cutover</h3><p>After the task is created, the system automatically syncs the source VM’s data to the target platform. You can see the task status “Syncing” in the task list.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*Tspphj2lLVjaxVTR.png" /></figure><p>When the status changes to “Ready for cutover”, the data sync phase is complete and the flow enters the final cutover stage.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*73wJ0KZVzavSE4O-.png" /></figure><p>Click “Cut Over”, read and confirm the risk notice, and the cutover begins, switching the VM’s business to the target platform.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*gv0zw27ZdpMgqv2s.png" /></figure><p>After a successful cutover, you can see that the VM from the original VMware platform has been migrated to this platform.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*rC05LJjUP3rh7_Qd.png" /></figure><h3>2. Importing a VM (OVF)</h3><p>If you only have a few VMs to migrate and the business can tolerate a short outage for export, you can skip ZMigrate and migrate by importing an OVF template instead. The overall idea: export the VM as an OVF template on the source platform, then upload and import it on the target platform.</p><p><strong>Step 1: Export the OVF template</strong>. On the source platform (such as VMware vSphere), shut down the target VM and export it as an OVF template. You usually end up with three kinds of files:</p><ul><li><strong>OVF file</strong>: the VM’s descriptor file that defines its hardware configuration;</li><li><strong>VMDK file</strong>: the VM’s disk data file;</li><li><strong>MF file</strong>: the manifest file used to verify file integrity.</li></ul><p><strong>Step 2: Import on the target platform</strong>. In the navigation bar, right-click the target cluster, host, or image, click “New VM”, and choose “Import VM” as the creation method:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*NfvER6CSJHXq8Y2G.png" /></figure><p>Then complete two parts of the configuration:</p><ul><li><strong>Upload info</strong>: choose an image store (used to temporarily hold the uploaded template files and deleted automatically once the VM is created), set the template type to OVF, and upload the OVF, VMDK, and MF files in order. Note that the VMDK file must match the configuration defined in the OVF file, including the number and content of the files.</li><li><strong>Basic info</strong>: set the VM name, group, running location (host or cluster), and storage location (auto-allocated if not set); optionally configure high availability, VM/disk encryption, and whether to power on the VM automatically after import.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*K0uSN_oRQdM3_nth.png" /></figure><p>Confirm and click OK; the VM import completes. After import, it’s recommended to install VMTools so some of the VM’s configurations take effect.</p><h3>3. Uploading a VMDK Image</h3><p>Besides OVF template import, there’s an even more direct approach: upload only the VM’s disk files. If you already have the VM’s VMDK disk file (for example, exported from VMware), you can upload it as an image to the image server, and the platform handles the format conversion automatically — uploaded to an ImageStore server, it’s converted to qcow2; uploaded to a Ceph server, it’s converted to raw. Then create a VM from that image and the migration is done.</p><p>The steps are:</p><ol><li>In the main menu, go to “Resource Center &gt; Cloud Resource Pools &gt; Compute Configuration &gt; Images”, open the image page, and click “Add Image”.</li><li>Configure it with these points in mind:</li></ol><ul><li><strong>Image type</strong>: choose system image;</li><li><strong>Image format</strong>: choose vmdk;</li><li><strong>Platform / VirtIO</strong>: choose the platform type based on the OS inside the image, and decide whether to enable VirtIO (when enabled, the guest OS loads VirtIO disk and NIC drivers for better performance; for a few older OSes that don’t support VirtIO, you can leave it disabled);</li><li><strong>OS / CPU architecture / BIOS mode</strong>: choose settings that match the image; the BIOS mode must match how the image was packaged (Legacy or UEFI), otherwise the VM may not work properly;</li><li><strong>Image server</strong>: choose a created image server;</li><li><strong>Image path</strong>: supports URL (HTTP/HTTPS, FTP, SFTP) or local file upload; ImageStore servers support resumable uploads.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*gYxU1O8zzW3aCBZi.png" /></figure><ol><li>Confirm and click OK; wait for the image upload and format conversion to complete.</li></ol><p>After the upload, you can open the image details page and check the image’s MD5 value to verify integrity (note: VMDK uploads go through format conversion, so the MD5 value can’t be used as an integrity check afterward). Then use the image to “Create VM”, configuring CPU, memory, network, and other parameters as needed — once the VM is created, the migration is complete. Installing VMTools is recommended here as well.</p><h3>In Conclusion</h3><p>There’s no absolute winner among the three migration methods — it all depends on your scenario: batch migration where business can’t stop, choose ZMigrate; a few VMs that can tolerate a brief outage for export, choose OVF import; only disk files and you want to recover data quickly, choose VMDK image upload.</p><p>If you’re planning a migration from VMware to ZSvirt, we suggest running through the full flow with one or two non-critical VMs first, getting familiar with the rhythm of sync, testing, and cutover, and then rolling out in batches. If you run into issues during migration, feel free to reach out to the ZSvirt open-source community for more details.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*eZAYwU2KWvAyaTUi.png" /></figure><h3>Join the Community</h3><ul><li><strong>Issue reports</strong>: <a href="https://github.com/zsvirt/zsvirt/issues">GitHub Issues</a></li><li><strong>Community discussions</strong>: <a href="https://github.com/ZSvirt/zsvirt/discussions">GitHub Discussions</a></li><li><strong>Social media</strong>:</li><li>YouTube: <a href="https://youtube.com/@ZSvirt">https://youtube.com/@ZSvirt</a></li><li>LinkedIn: <a href="https://www.linkedin.com/in/zsvirt-community/">https://www.linkedin.com/in/zsvirt-community/</a></li><li>X/Twitter: <a href="https://x.com/ZSvirt">https://x.com/ZSvirt</a></li><li>Email: <a href="https://community@zsvirt.io/">community@zsvirt.io</a></li><li>Discord: <a href="https://discord.gg/KHsw63z9xA">https://discord.gg/KHsw63z9xA</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b3109fdc659e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ZSvirt Architecture Explained: How a Production-Proven Virtualization Engine Is Built]]></title>
            <link>https://zsvirt.medium.com/zsvirt-architecture-explained-how-a-production-proven-virtualization-engine-is-built-8e81b1fa3bc4?source=rss-16d9dff0f9c7------2</link>
            <guid isPermaLink="false">https://medium.com/p/8e81b1fa3bc4</guid>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[virtualization]]></category>
            <category><![CDATA[open-source]]></category>
            <dc:creator><![CDATA[ZSvirt Community]]></dc:creator>
            <pubDate>Thu, 20 Aug 2026 14:21:01 GMT</pubDate>
            <atom:updated>2026-08-20T14:21:01.147Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/680/1*jHSFNKBwY2TltrAxD9WNJg.png" /></figure><p><em>Over the past three days, we announced ZSvirt’s open-source release, shared the reasoning behind that decision, and walked you through creating your first VM. Today, we’re zooming in on the engine itself — not a blueprint for a new project, but a real architecture that has been running in production for years.</em></p><p>In an enterprise virtualization environment, the real challenge has never been just “can you create a VM.” A mature virtualization engine has to face far more complex production problems: how to manage large numbers of physical servers uniformly, how to coordinate compute, storage, and network resources, how to recover automatically when a task fails, how to keep scaling as demand grows, and how to let different kinds of infrastructure capabilities plug in.</p><p>ZSvirt is built on the open-source ZSphere architecture. Its core value isn’t just offering VM lifecycle management — it inherits a virtualization control architecture that has been validated in production. It lowers complexity through unified resource abstraction, ensures reliable task execution through async mechanisms and workflows, supports growth in resource scale through a message bus and modular design, and adapts to different infrastructure environments through a plugin architecture.</p><p>From an architectural standpoint, ZSvirt can be summed up in three keywords: ease of use, stability and performance, and extensibility and openness.</p><h3>1. Ease of Use: Unified Abstraction That Hides Underlying Complexity</h3><p>The underlying resources in a virtualization environment are highly complex. Compute nodes, storage pools, image repositories, physical networks, virtual switching, VMs, virtual disks, and snapshots — there are many dependencies between all of them. If you exposed that complexity directly to users and operators, the system would become hard to manage and hard to maintain over the long term.</p><p>The first thing ZSvirt’s architecture solves is resource abstraction. It unifies the underlying infrastructure into standard resource objects — compute resources, storage resources, network resources, image resources, and VM resources. What users see in the UI or API is a clean resource model, not a scattering of low-level commands, config files, and host states.</p><p>Take creating a VM as an example. On the surface it looks like a single operation, but underneath it involves many steps: choosing an appropriate compute node, checking CPU and memory resources, preparing an image, creating a virtual disk, connecting to a virtual network, generating the VM configuration, and finally launching the instance on the target compute node. ZSvirt wraps all of these steps into a unified backend flow. Users don’t need to care about each step — they just operate on the VM as a resource object.</p><p>This unified abstraction also makes operations simpler. Onboarding resources, syncing node state, querying VM state, mounting storage, configuring networks, and deploying and upgrading agents can all be done through a single management entry point. For users, ZSvirt is not a collection of scattered tools but a complete virtualization control engine — one that converges complex infrastructure relationships into a unified model, wraps multi-step resource operations into standard flows, and hides underlying differences behind a consistent management interface.</p><h3>2. Stability and Performance: An Async, Stateless, and Lock-Free Architecture for Production-Grade Operation</h3><p>Many operations in a virtualization system are long-running tasks. Creating a VM, migrating a VM, taking a snapshot, attaching a disk, expanding storage, and configuring networks can all involve multiple components and long execution times. If the management node handled these tasks in a synchronous, blocking way, a single slow operation could easily drag down the responsiveness of the whole system.</p><p>ZSvirt is designed to be fully async. Services inside the management node collaborate through asynchronous messages, tasks within a service are organized through async methods, and the management node communicates with compute, storage, and network components asynchronously as well. As a result, a long-running virtualization task never blocks the entire management process, and the system can handle a large number of resource operations at the same time. The async mechanism not only improves throughput, but also gives task execution more room for fault tolerance.</p><p>Another key design for stability is stateless services. Management services avoid relying on local state wherever possible, keeping critical state in the database, task contexts, and resource state records instead. That way, when a management node restarts, fails over, or scales out, the system won’t become unrecoverable because some node’s local state was lost. This matters a lot in production, because maintenance, upgrades, and crash recovery of the management service all need to minimize impact on business VMs.</p><p>Behind stateless services lies routing design such as a consistent hash ring. The system routes requests to a relatively fixed processing path based on the resource identifier, so that related operations on the same resource are dispatched and handled stably. For example, start, stop, migrate, and reboot operations on the same VM need to be ordered, while operations on different VMs can run in parallel. This reduces the need for shared state between management nodes and lowers the risk of concurrency conflicts.</p><p>For service organization, ZSvirt follows an in-process microservice approach. VM management, storage management, network management, image management, identity and authentication, and other capabilities are split into separate service modules, but they run inside a single unified management process and collaborate through a message mechanism. This keeps module boundaries clear without mixing all the logic together, while avoiding the heavy complexity of multi-process deployment. For a virtualization management system, that’s a design that balances stability and engineering efficiency.</p><p>The workflow engine solves the problem of reliable execution of complex tasks. Virtualization operations are rarely done in one step — they’re made up of many stages. For example, when creating a VM, the virtual disk may already have been created when the network configuration step fails. Without workflows and rollback, the system could be left with orphaned disks, inconsistent configs, or half-finished states. ZSvirt uses workflows to break complex operations into executable steps, each with clear execution logic and failure-handling logic. When a step fails, the system can roll back or clean up along the flow, reducing leftover inconsistent state.</p><p>From a performance perspective, the fully async architecture, stateless services, and lock-free design are the three defining traits of ZSvirt. The system doesn’t rely on a sea of locks for safety — it manages concurrency through message routing, resource ownership, and task queues. Operations on the same resource are processed in order; operations on different resources run in parallel whenever possible. This raises overall throughput and keeps behavior more predictable under large-scale concurrency.</p><h3>3. Extensibility and Openness: A Message Bus and Plugins That Adapt to Scale and Difference</h3><p>As virtualization scale grows, the number of resources the system manages increases quickly: more compute nodes, more VMs, more virtual disks, more network configurations, and more concurrent tasks. At the same time, different enterprises have very different infrastructure environments — some use local storage, others shared or distributed storage; some networks are VLAN-based, others need more complex virtual network models; and different customers have different requirements for security, monitoring, backup, and image management.</p><p>ZSvirt’s extensibility starts with the message bus. Management services communicate through a message bus instead of calling each other directly. This decouples the services, keeping VM management, storage management, network management, image management, and identity and authentication logically independent. Each service focuses on its own resource domain and collaborates with others through messaging.</p><p>ZSvirt also offers extensibility through a plugin architecture. Compute, storage, network, security, and monitoring capabilities can be extended as modules or plugins. The upper layer keeps a unified resource model and operation interface, while the lower layer can adapt to different implementations. For example, storage appears to the upper layer as virtual disks and storage pools, but underneath it can connect to different kinds of storage systems; networking appears as virtual networks and address configuration, but underneath it can adapt to different network schemes based on the environment.</p><p>The value of the plugin architecture is that it keeps the core system stable while allowing peripheral capabilities to evolve continuously. That matters especially for a virtualization engine like ZSvirt, because infrastructure environments keep changing — new hardware, new storage solutions, new networking modes, and new security capabilities keep appearing. Only an architecture that is open enough can keep adapting to different production environments.</p><p>Openness is also reflected at the API layer. Through standardized interfaces, ZSvirt can integrate with monitoring systems, operations tools, resource management systems, and automation tooling. So ZSvirt isn’t just a standalone virtualization management product — it can also serve as the virtualization capability foundation within an enterprise’s broader infrastructure.</p><h3>4. In Conclusion</h3><p>This architecture is not a blueprint drawn up for a new project — it’s the result of the same engine running for years across more than 1,000 production environments. Today it’s fully open as ZSvirt. Every mechanism described above — the message bus, the async framework, the workflow engine, consistent hashing, the agent layer — you can find the corresponding implementation in the repository.</p><h3>Join the Community</h3><ul><li><strong>Issue reports</strong>: <a href="https://github.com/zsvirt/zsvirt/issues">GitHub Issues</a></li><li><strong>Community discussions</strong>: <a href="https://github.com/ZSvirt/zsvirt/discussions">GitHub Discussions</a></li><li><strong>Social media</strong>:</li><li>YouTube: <a href="https://youtube.com/@ZSvirt">https://youtube.com/@ZSvirt</a></li><li>LinkedIn: <a href="https://www.linkedin.com/in/zsvirt-community/">https://www.linkedin.com/in/zsvirt-community/</a></li><li>X/Twitter: <a href="https://x.com/ZSvirt">https://x.com/ZSvirt</a></li><li>Email: <a href="/service/mailto:community@zsvirt.io">community@zsvirt.io</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8e81b1fa3bc4" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>