Virtuozzo Hybrid Server 7.5 Update 7 Hotfix 1 (7.5.7-151)¶
Issue date: 2024-12-12
Applies to: Virtuozzo Hybrid Server 7.5
Virtuozzo Advisory ID: VZA-2024-052
1. Overview¶
The Hotfix 1 for Virtuozzo Hybrid Server 7.5 Update 7 provides new features, as well as stability and usability bug fixes.
2. New Features¶
The ‘c2v-convert’ tool now collects anonymous statistics about conversion attempts if the host where the tool is used participates in the Customer Experience Program (CEP). It helps Virtuozzo proactively identify issues in the tool’s operation. If the host with the tool used on it does not participate in CEP, no statistics will be gathered. For more information on the data we collect, refer to Usage Data Collection. (PSBM-159598)
SUSE Linux Enterprise Server 15 SP6 is now a supported guest OS for virtual machines. (PSBM-159377)
3. Bug Fixes¶
Fixed an issue with the ‘c2v-convert’ tool failing while creating a filesystem for a virtual machine’s disk. (PSBM-159866)
The warning message ‘LC_CTYPE: cannot change locale (UTF-8)’ could appear after logging in to Virtuozzo Hybrid Server via SSH. (PSBM-159824)
Fixed an issue with the ‘c2v-convert’ tool getting stuck when trying to install ‘kernel’ and ‘grub.’ (PSBM-159603)
4. Known Issues and Limitations¶
The cloud-init package must be installed before changing a password in stopped SUSE Linux Enterprise Server 15 SP6 virtual machines.
The first automatic installation of Virtuozzo guest tools to a running SUSE Linux Enterprise Server/Desktop 15 SP6 virtual machine with the ‘vz-guest-tools-updater’ tool requires stopping the VM. If you prefer the first-time installation of the guest tools without downtime, install them manually from our system ISO after ensuring the previously mounted ISO is ejected. With the Virtuozzo guest tools set up, the subsequent run of ‘vz-guest-tools-updater’ for the running VM will update the guest tools online (without downtime) to the latest version.
A cloned SUSE Linux Enterprise Server 15 SP6 virtual machine gets a NIC name with an index increased by one. For example, if an original NIC name is ‘eth0’, it will acquire +1 to its existing name. Thus, the name will change to ‘eth1’. The subsequent clone operation from the cloned VM will cause the same changes to the NIC name of a newly cloned VM, i.e., ‘eth2’, ‘eth3’, etc.