Customer had data corruption after attaching the same disk to multiple VMs by mistake.
The product is missing guardrails to protect from this.

This property below exists, but the controller has no checks during VMI creation if there is already another VM up with the same PVC/DV attached and without this property set. It should check this to prevent data corruption scenarios.

# oc explain vm.spec.template.spec.domain.devices.disks.shareable
GROUP:      kubevirt.io
KIND:       VirtualMachine
VERSION:    v1

FIELD: shareable <boolean>


DESCRIPTION:
    If specified the disk is made sharable and multiple write from different VMs
    are permitted
    

4.19.10

Always

1. Create an RWX DV
2. Attach it to 2 VMs (don't set as shareable)
3. Start both VMs

Both VMs are up, Data Corruption

Check and block VMI creation of the subsequent VMs using the same disk, unless its set to shareable.