I've been using the systemvm VHD to test that format on my KVM template patch, launching it as a user vm. I guess this means we may be able to get away with not generating the qcow2 template anymore if we wish. I haven't tested the system vm install script against it yet, though.
On Tue, Dec 17, 2013 at 10:31 AM, Alex Huang <alex.hu...@citrix.com> wrote: > It makes sense to. I think we started with vmdk and is now using ova. If > so, whoever did the change just didn't rename the file. Would have been > better to just add a new processor when that change was done... > > --Alex > >> -----Original Message----- >> From: Marcus Sorensen [mailto:shadow...@gmail.com] >> Sent: Tuesday, December 17, 2013 8:06 AM >> To: dev@cloudstack.apache.org >> Subject: Re: kvm - why just qcow2 >> >> 1) Would it be OK to move VmdkProcessor to OVAProcessor, so we can use >> VmdkProcessor for native .vmdk files? >> >> 2) I also noticed in my testing that .ova is the one format so far that >> doesn't >> work out of the box with minor code changes for KVM, and it seems to be >> due to the fact that VmdkProcessor untars the .ova to get the .vmdk and .ovf >> files, but then registers the .ova file as the template file, not the .vmdk. >> It >> would be nice to be able to use the same template for both vmware and kvm. >> >> I don't have a vmware setup to test any of this with. I can verify that the >> OVAProcessor rename has the same results when registering a template, but >> I wouldn't be able to do anything with #2. >> >> On Mon, Dec 16, 2013 at 6:55 PM, Marcus Sorensen <shadow...@gmail.com> >> wrote: >> > 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
