Virtual machines with multiple disks that are migrated from VMware behave differently during snapshot restore compared to virtual machines originally created on OpenShift Virtualization. 

For virtual machines created natively on OpenShift Virtualization[with single disk or multiple disks], restoring a snapshot replaces the existing PVC with the restored PVC (renamed with a restore-<uuid> suffix), and no additional PVCs are created. 

However, for virtual machines migrated from VMware[with multiple-disks], restoring a snapshot creates additional PVCs instead of replacing the existing ones. After the snapshot is deleted, these extra PVCs remain present and require manual cleanup.

I have tested this in following cases:
VM created on OpenShift:
- with single disk
- with multiple disks

VM migrated from VMware:
- with single disk
- with multiple disks <---- affects here
 

Everytime

Scenario 1: VM created on OpenShift Virtualization 
1. Create and start a VM created natively on OpenShift Virtualization. 
2. Create a snapshot of the VM. 
3. Stop the VM. 
4. Restore the VM from the snapshot. 
5. Observe that the existing PVC is renamed with restore-<uuid> and no extra PVCs are created.
Scenario 2: VM migrated from VMware - [having multiple-disks before migration or adding additional disk after migration]
1. Create or import a VM migrated from VMware. 
2. Create a snapshot of the VM. 
3. Stop the VM. 
4. Restore the VM from the snapshot. 
5. Observe that additional PVCs with restore-<uuid> are created, resulting in extra PVCs per disk.
Example: There's now two extra PVCs

60 GiB restore-<> 
60 GiB xx-<>. <-- original 
50 GiB restore-<> 
50 GiB yy-<> <-- original
  

Extra PVC with restore-<xx> getting created 

The existing PVC should get renamed restore-xxx as seen in other scenarios