Virtualization Station 4.1.1.117 released

Virtualization Station 4.1.1.117 2026/05/12

[Important Notes]

  • Before updating to Virtualization Station 4.0, review application compatibility and other important information. For details, see this FAQ: What are the recommended considerations before updating to Virtualization Station 4.0?
  • Virtualization Station now prevents application removal from App Center when an active VMHA pair exists. To remove Virtualization Station, please unpair the HA pair first.

[New Features]

  • Added PCIe passthrough support for the QAI-1290FX expansion card.
  • Added support for Oracle Linux and Rocky Linux. Expanded support for additional versions of Ubuntu, RHEL, Debian, Fedora, and Windows Server. For the full list, see this FAQ: What operating system can I deploy in Virtualization Station?
  • Added the Intel Broadwell (noTSX) CPU emulation model. This enables support for newer operating systems such as RHEL 10 and Windows Server 2025.

[Enhancements]

  • Enhanced application security and stability through core component upgrades.
  • VMHA now displays a warning when the total virtual machine network adapter bandwidth exceeds the available link bandwidth, helping prevent network performance issues during failover.

[Fixed Issues]

  • Resolved an issue where virtual machines displayed a black screen when opening via QVM (direct display output) after upgrading the firmware from QuTS hero 5.2.4 to QuTS hero 5.3.0.
  • Resolved an issue where live migration of virtual machines between two NAS devices failed to complete successfully.
  • Fixed an issue where creating an HA plan failed with an error when a virtual machine was configured with two network adapters, and the adapter with the lower index was removed.

[Compatibility]

  • Before updating to Virtualization Station 4.0, we recommend verifying the compatibility of your existing applications and data with the new version. For details, see What are the recommended considerations before updating to Virtualization Station 4.0?

Just tried it, still causes (like the last pulled release) windows 11 VM’s to max out memory after a short time, this doesnt show in console it only shows in the VM itself, makes them run slow (cos of swapping I guess). Uninstalled and reinstalled .338 and all is fine again. Dont think I’ll bother with any future updates for now.

What is a short time ?

My Win11-VM hasn’t that problem.After 7 hours there is no problem with the RAM

Well I dont know then, it does it on the 3 VM’s I run, one runs Blue Iris, QNAP is a tvs-h1288x with 96Gb ram, after say an hour or so, I try remote desktop to it and its unusable as its filled the 16Gb ive assigned and is swapping disk/memory constantly - went back to .338 and same VM’s run totally fine.

@rolandrat

Did you turn on dynamic memory allocation on the VM? If you turned on that, the host can take away memory from VM, and you’ll see the memory consumption increases inside the guest. You may need to turn off that feature or make the VM has higher weight.

That feature was broken in the earlier version.

I do have that on, ill turn it off and try update again, thanks for the clue! Ill report back in a few hours.

I have tested this version with a Ubuntu 24.04 guest. My dynamic memory allocation and memory sharing is on, and I can see the total memory shown in guest htop decreases when the host is having memory pressure.

And your QuTShero / QTS version is ?

Its latest official quts version, but thats irrelevant anyway, as it does appear to be fixed by turning off the Dynamic memory allocation.

I think that’s just how dynamic memory allocation works. For Windows guest, the memory reclaimed by host shows as consumed memory. For Linux guest, it shows as reduced total memory.