Is there any way currently of specifying that new virtual guests created with koan/cobbler should use the qcow2 disk format, instead of raw images?
Adam
On Fri, Oct 7, 2011 at 9:03 AM, Adam Huffman adam.huffman@gmail.com wrote:
Is there any way currently of specifying that new virtual guests created with koan/cobbler should use the qcow2 disk format, instead of raw images?
I don't think so currently, unfortunately. Expanding the list of options available to koan via libvirtd is a big item on my todo list.
On Fri, Oct 7, 2011 at 11:16 PM, James Cammarata jimi@sngx.net wrote:
On Fri, Oct 7, 2011 at 9:03 AM, Adam Huffman adam.huffman@gmail.com wrote:
Is there any way currently of specifying that new virtual guests created with koan/cobbler should use the qcow2 disk format, instead of raw images?
I don't think so currently, unfortunately. Expanding the list of options available to koan via libvirtd is a big item on my todo list.
Looking through the python-virtinst source it looks like qcow2 isn't a supported option yet, unless I just have an out of date version (running on F15). Are they just lagging behind libvirt? Adding support for qcow/raw/aio doesn't look like it'd be too much of an issue.
On Sat, Oct 8, 2011 at 3:17 PM, James Cammarata jimi@sngx.net wrote:
On Fri, Oct 7, 2011 at 11:16 PM, James Cammarata jimi@sngx.net wrote:
On Fri, Oct 7, 2011 at 9:03 AM, Adam Huffman adam.huffman@gmail.com wrote:
Is there any way currently of specifying that new virtual guests created with koan/cobbler should use the qcow2 disk format, instead of raw images?
I don't think so currently, unfortunately. Expanding the list of options available to koan via libvirtd is a big item on my todo list.
Looking through the python-virtinst source it looks like qcow2 isn't a supported option yet, unless I just have an out of date version (running on F15). Are they just lagging behind libvirt? Adding support for qcow/raw/aio doesn't look like it'd be too much of an issue. _______________________________________________ cobbler mailing list cobbler@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
Doesn't this imply that other image formats are supported?:
http://pkgs.fedoraproject.org/gitweb/?p=python-virtinst.git;a=commit;h=1045f...
Doesn't this imply that other image formats are supported?:
http://pkgs.fedoraproject.org/gitweb/?p=python-virtinst.git;a=commit;h=1045f...
I actually got this done over the weekend, I just have pushed it up to the master branch. Part of the issue I found, was that when I set the disk to qcow the VM wouldn't boot, and when I set it to qcow2 virtinst ignored it and defaulted it back to raw (I assume because it's not one of the listed TAP drivers).
So, I can push this up, but YMMV in actually trying to use it. For the record, the #kvm guys did say that raw was the best/fastest option, but this functionality could be useful in the future.
On Wed, Oct 12, 2011 at 1:19 AM, James Cammarata jimi@sngx.net wrote:
Doesn't this imply that other image formats are supported?:
http://pkgs.fedoraproject.org/gitweb/?p=python-virtinst.git;a=commit;h=1045f...
I actually got this done over the weekend, I just have pushed it up to the master branch. Part of the issue I found, was that when I set the disk to qcow the VM wouldn't boot, and when I set it to qcow2 virtinst ignored it and defaulted it back to raw (I assume because it's not one of the listed TAP drivers).
So, I can push this up, but YMMV in actually trying to use it. For the record, the #kvm guys did say that raw was the best/fastest option, but this functionality could be useful in the future.
James,
Many thanks for working on this.
It's the ability to make snapshots I'm after, which isn't possible with raw images, as far as I know.
Adam
cobbler@lists.fedorahosted.org