Importing drive silently overwrites existing drive the same name

[adrusi]

When importing a drive image, UTM copies it into ~/Library/Containers/com.utmapp.UTM/Data/Documents/$VM.utm/Images/ without checking if a file of the same name exists.

Steps to reproduce:

1. Have two images in different directories with the same file name: dir1/image.qcow2, dir2/image.qcow2
2. Create a VM, importing dir1/image.qcow2 as the boot drive
3. Use the VM, then shut down
4. Edit the VM, adding a second drive by importing dir2/image.qcow2

After following this procedure, booting the VM shows two connected drives, e.g. /dev/vd{a,b}, but qemu is using the same image for both. They have the same UUIDs and the same contents. Deleting either of the drives from the UTM configuration appear successful, but results in this error when booting:

qemu-aarch64-softmmu: -drive if=none,media=disk,id=drive0,file=/Users/$USER/Library/Containers/com.utmapp.UTM/Data/Documents/$VM.utm/Images/image.qcow2,cache=writethrough: Could not open '/Users/$USER/Library/Containers/com.utmapp.UTM/Data/Documents/$VM.utm/Images/image.qcow2': No such file or directory

Configuration

• UTM Version: 3.1.5 (53)
• OS Version: 12.3