Hi, Just wondering why the qcow2 transfer drivers [1] didn't worked for you.
Currently, creating qcow2 images is not supported. Adding this is fairly simple, just edit scripts_common.sh (both $ONE_LOCATION/lib/sh/ and $ONE_LOCATION/var/remotes/) and add another case in the mkfs_command function. Something like ... "qcow2") echo "qemu-img create -f qcow2 $DST $SIZE" return 0 ;; Then, use FSTYPE="qcow2" in your image templates. Let us know if you need further help modifying this file. I've just filled an issue [2] to include this for the next release. Thanks for your feedback. Ruben [1] http://www.opennebula.org/documentation:rel3.6:fs_ds#using_the_qcow2_transfer_driver [2] http://dev.opennebula.org/issues/1365 On Sat, Jul 14, 2012 at 10:23 PM, Ricardo Duarte <[email protected]> wrote: > Hi there, > > Currently I'm using KVM with OpenNebula, and already made some changes to > the tm to support qcow2 linked clones. It is working fine. > What I'm missing is how to make SunStone and the one cli to create new > disks as qcow2. > Currently they are setup as raw, even if I set target to qcow2 on both > template and datablock/os disk. That takes a lot of space (especially swap > disks), and also makes my tm fail. > Can somebody provide me some guidance on how to setup OpenNebula so that > all the disks, created with SunStone or the one cli, are created as qcow2? > > Thanks > > _______________________________________________ > Users mailing list > [email protected] > http://lists.opennebula.org/listinfo.cgi/users-opennebula.org > > -- Ruben S. Montero, PhD Project co-Lead and Chief Architect OpenNebula - The Open Source Solution for Data Center Virtualization www.OpenNebula.org | [email protected] | @OpenNebula
_______________________________________________ Users mailing list [email protected] http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
