So I created a CentOS atomic image by downloading the qcow2 image and using it as the disk for the VM. After creating the VM I detached the disk, replaced the qcow2 of the disk with the atomic image and then reattached the disk. After reattaching the disk it shows up in the VM's config as 10GB but the qcow2 image is approximately 1.4GB.
If I then clone this VM and specify a different Storage backend on another NFS server or do a full clone the qcow2 image is then copied and now show up as 10GB. Not sure what is going on other then maybe a sparse image is being copied to an full image, but I am not sure about that. Is there any way to prevent this from happening?
If I then clone this VM and specify a different Storage backend on another NFS server or do a full clone the qcow2 image is then copied and now show up as 10GB. Not sure what is going on other then maybe a sparse image is being copied to an full image, but I am not sure about that. Is there any way to prevent this from happening?