Feature fixes, security and maintenance update candidates for you to test! We are continuing to refine the next batch of update with planned fixes. This release batch contains fixes on the major storage feature previously announced, read the RC2 announcement for QCOW2 image format support for 2TiB+ images. What changed Storage QCOW2 image format support is the major feature of this release batch, check related announcement in forum. Some fixes have been applied to fix issues found during the testing phase. sm: 3.2.12-17.6 Limit QCOW2 VDI max size to be 16TiB with metadata to allow compatibility with EXTSR (EXTSR is limited to 16TiB unique file size) If a full QCOW2 VDI is allocated, XCP-ng would not be able to migrate it to an EXTSR with this limitation. In the future, while EXTSR will remain limited to this maximum size, other SR types will evolve towards higher limits. For this, we'll have to work on the existing assumption that all SR which support the QCOW2 image-format share the same maximum size limit for VDIs, and to catch migration attempts towards SRs whic cannot receive disks bigger than their maximum limit. blktap: 3.55.5-6.6 Update the package's license. Versions: blktap: 3.55.5-6.5.xcpng8.3 -> 3.55.5-6.6.xcpng8.3 sm: 3.2.12-17.5.xcpng8.3 -> 3.2.12-17.6.xcpng8.3 Test on XCP-ng 8.3 If you are using XOSTOR, please refer to our documentation for the update method. yum clean metadata --enablerepo=xcp-ng-testing,xcp-ng-candidates yum update --enablerepo=xcp-ng-testing,xcp-ng-candidates reboot The usual update rules apply: pool coordinator first, etc. What to test The most important change is related to storage: adding QCOW2 support also affects the codebase managing VHD disks. What matters here is, above all, to detect any regression on VHD support (we tested it deeply, but on this matter there's no such thing as too much testing). Of course, you are also welcome to test the QCOW2 image format support. See the dedicated thread for more information. And, as usual, normal use and anything else you want to test. Test window before official release of the updates ~3 days We would like to thank users who reported feedback since our last call for testing, in less than 24h: @acebmxer, @Andrew, @MajorP93.