Description of problem: This bug is a special case of BZ #1101003 (see description) A "Crossed domain template"(not a real term just to simplify the explanation) is a template that was created from a vm which had a raw sparse disk (nfs thin disk for example) and then was copied to a Block domain. Creating vm from a "crossed domain template" Menu has redundant option. choosing create vm as clone on block domain should give us just one choice (preallocated). Version-Release number of selected component (if applicable): alpha2 build How reproducible: 100% Steps to Reproduce: 1.create vm+thin file disk 2.create template from this vm 3.copy template to block domain 4.add a new vm from template,choose the "crossed domain template" 5.browse to Resource Allocation,choose the options:block domain,clone Actual results: Two options to create are displayed,thin and preallocate Expected results: Should be only one,preallocate Additional info:
The logic is when you choose to create thin provision disk in a block device, it will be created as cow sparse even if it was copied from a file domain's raw sparse disk, for preallocated it will be created as raw preallocated thus both options are legal