No. You have to do qcow2 for KVM and VHD for XenServer as it is now, by the way. But if we allowes multiple types I think we'd want to convert to a single 'preferred' format for each primary storage, rather than messing with all different support between primary storage, image formats, and their respective support for snapshots, etc. So a file-based primary storage would always copy the template as qcow2 (from vmdk, vdi, raw, whaterver), and a raw based primary storage (like LVM or RBD) would always convert to raw (as it already does), when copying template to primary storage.
On Mon, Dec 16, 2013 at 5:44 PM, Nux! <n...@li.nux.ro> wrote: > On 16.12.2013 05:05, Marcus Sorensen wrote: >> >> Actually, I'm wrong. It used to qemu-img convert qcow2 to qcow2, but >> not any more. Qemu is actually just using vmdk natively. > > > Disappointment. I was going to build some "hv agnostic" templates, but I > really don't want my KVM to run vmdk files etc. > To clarify, if I add a raw template to CS, will it do any conversion to VHD > if it's a Xenserver or to Qcow2 if it's KVM? > > Lucian > > -- > Sent from the Delta quadrant using Borg technology! > > Nux! > www.nux.ro
