@bvitnik It's specific to XCP-ng.
Team - Storage
Private
Posts
-
RE: How to reliably determine VDI format (vhd, qcow2, raw) via XAPI across versions
@bvitnik Hello,
sm-config:vdi_typeis the pre-existing one so we are still writing it for compatibility reasons.
But you might notice thatvdi_typeis only written for LVM-based SRs.
Whileimage-formatis always written in XCP-ng with the QCOW2 feature.So it might be safe to just look at
image-formatif it exist and if it's not, it's likely a VHD.
On LVMSR, you can fallback onvdi_type(and it should work for XS too).Indeed, ISO SRs do not advertise a VDI format. Technically, ISOs could be considered to be
raw.It should also be noted that our implementation of QCOW2 is very different from GFS2 QCOW2 of XenServer.
Our implementation uses the existing SR types to allow VHD and QCOW2 to co-exist. -
RE: XCP-ng 8.3 updates announcements and testing
@probain Hello,
It's likely linked to the
List index out of rangebug.
That bug was linked to the SR scan failing to introduceCBT_metatadataVDI in the XAPI database, could you try to launch axe sr-scan uuid=<SR UUID>and try again to disable CBT?
If it does not work, could you share the/var/log/SMlogof around the time you are trying to disable CBT?
