← Back to blog

A lot of VMware exits stall on Windows. The Linux estate is easy to picture somewhere else. The domain controllers, the IIS sites, and the Windows desktops are why the renewal gets signed. kcore runs Windows Server and Windows desktop guests. That is a statement about guests, not a Microsoft certification claim.

What “runs” means

You create the VM through the controller API: kctl, a YAML manifest, or Terraform provider kcorehypervisor/kcore 0.5.0. The Windows disk is an image you supply. Two walkthroughs on this blog show the shape of the work: Windows Server 2022 with the default IIS page, and a Windows 10 Pro desktop reached through an SSH port forward. Follow those pages for the commands. This page is the buying question.

Hyper-V CPU enlightenments are part of the Server walkthrough. They are a performance detail, not a support contract with Microsoft.

GPU, and what is not included

One physical GPU can be assigned to one VM. NVIDIA vGPU, many VMs on one card, is not available. If the estate depends on shared vGPU, say so before you move that guest. A single passthrough card for one workstation VM is a different conversation.

What still sits outside the guest

Live migration of a Windows VM needs the same thing as any other guest: shared Ceph storage. Local filesystem, LVM, or ZFS disks do not move between hosts. A failed host update boots the previous generation of kcoreOS. That protects the host. It is not a Windows snapshot product. There is no integrated backup product yet. kctl backup copies the controller database. Guest backup stays with your existing tool, and you should confirm that tool supports the disk format you chose.

Who this is for

Download the evaluation ISO, build one Windows guest the way the walkthroughs describe, and only then talk about the rest of the estate.

Download the evaluation ISO See pricing Read the docs Book a migration assessment

Questions: team@tacconiconsulting.com.