ZStack Cloud 5.5.30 optimizes Windows nested virtualization and lets you enable or disable it globally or for an individual VM instance. Nested virtualization is disabled by default to improve the compatibility and runtime stability of newer workloads such as Windows Server 2025 and reduce risks such as blue screens. You can enable it as needed.

Starting with ZStack Cloud 5.5.30, you can assign IPv6 addresses to the Management Network and deploy and operate the platform in IPv6 environments, meeting evolving network requirements.

Starting with ZStack Cloud 5.5.30, you can configure volume multi-queue globally or at the cluster, VM instance, or volume level. You can also enable a dedicated I/O thread for an individual volume on ZBS Primary Storage as needed. These enhancements optimize the volume I/O path and performance and improve storage access efficiency in I/O-intensive scenarios.

Starting with ZStack Cloud 5.5.30, a single cluster can attach either Ceph, SharedBlock, and ZBS (CBD protocol) Primary Storage or Ceph and Vhost (XINFINI) Primary Storage, providing greater flexibility in resource planning and workload deployment.

Starting with ZStack Cloud 5.5.30, you can configure VM scheduling policies for clusters attached to Vhost (XINFINI) Primary Storage, providing greater resource scheduling flexibility in Vhost (XINFINI) storage environments.

Starting with ZStack Cloud 5.5.30, you can use host-local I/O cache. Host-local I/O cache uses high-performance local disks, such as SSDs or NVMe drives, on a host as cache media and organizes them into cache pools to accelerate volumes on ZBS (CBD protocol), Ceph, or Local Storage. Volume data remains persistently stored on the corresponding primary storage. This feature applies to workloads that are sensitive to I/O performance and access latency, such as databases and high-performance computing. Administrators can manage cache pool capacity, health, and lifecycle at the host level and enable local I/O cache for volumes as needed. This improves storage access efficiency for frequent reads and writes.

Starting with ZStack Cloud 5.5.30, ZBS is integrated into the cloud platform as a unified Primary Storage type. The capabilities of the former CBD Primary Storage remain available under the CBD protocol of ZBS Primary Storage. ZBS Primary Storage also adds a Vhost protocol path. You can connect storage resources through the unified ZBS Primary Storage entry and select the storage protocol appropriate for your workload when creating a VM instance or volume.

Note: Currently, when you create a VM instance on ZBS Primary Storage over the Vhost protocol, only images whose BIOS mode is UEFI are supported.

This capability enables ZBS Primary Storage to support VM instance and volume scenarios over different I/O paths, providing more flexible performance and compatibility options in a unified storage resource pool. The platform also provides a connectivity view between ZBS Primary Storage and hosts, helping administrators inspect protocol link status and quickly locate storage access issues.

Starting with ZStack Cloud 5.5.30, the dashboard displays resource utilization statistics so that you can view the real-time usage of key resources at a glance. Currently, the dashboard supports VM memory utilization (internal monitoring) and VM memory utilization (external monitoring). To view internal monitoring data, install GuestTools on the VM instance first.

ZStack Cloud 5.5.30 optimizes the resource alarm recovery mechanism. You can set recovery conditions based on a duration and the percentage of normal monitoring points. The system collects monitoring data at fixed intervals and calculates the percentage of monitoring points that do not meet the alarm condition within the specified duration. When this percentage reaches the specified threshold, the resource is considered recovered from the alarm state. This mechanism reduces misleading results caused by metric fluctuations and improves the accuracy of recovery assessment.

You can also select Alarm Messages > Set Silence Period to suppress alarm and recovery notifications triggered by an individual resource for a specified period. This operation does not affect other resources monitored by the same alarm, improving O&M flexibility without creating monitoring blind spots.

Starting with ZStack Cloud 5.5.30, you can view the alarm trigger status of each resource monitored by an alarm on the alarm details page, providing a more granular view for monitoring and troubleshooting.

Starting with ZStack Cloud 5.5.30, the x86 edition of Alibaba Cloud Linux 4 ISO supports GreatDB, and the ARM edition supports GreatDB and MySQL.

Starting with ZStack Cloud 5.5.30, you can add multiple project members and assign roles in a single operation. This reduces permission configuration costs in multi-user environments and improves permission management and team collaboration efficiency.

Starting with ZStack Cloud 5.5.30, the platform identifies and deduplicates multiple console tabs for the same VM instance, ensuring that at most one console tab is displayed per VM instance for a clear and easy-to-use tab view.

ZStack Cloud 5.5.30 fixes security vulnerabilities related to OpenSSH, Python, Curl, and HAProxy, and further improves the protection of sensitive information and user logins.

Jira: ZSTAC-85902/ZSTAC-81047/ZSTAC-85009/ZSTAC-85743/ZSTAC-85787/ZSTAC-84651/ZSTAC-72939

Note: Bug fix entries include the original Jira ticket numbers for issue tracking and traceability. Some tickets are private and do not provide viewable links.