I am not sure if this is the correct mailing list so if it is not, point me to the correct one.
I am a fan of the BTRFS filesystem and even use a subvolume for /var/lib/libvirt/images. Now, if you don't do anything, the disk image files are going to be hugely fragmented and get even more fragmented over time since BTRFS is a copy-on-write filesystem. I thought I knew how this stuff worked but apparently I do not because it does not currently work for me on Fedora 20 with current updates (not the preview although I will likely install that "real soon now").
1. To disable C-O-W I did "chattr +C /var/lib/libvirt/images" but new files are showing large fragmentation.
2. I want the default disk image format to be raw rather than qcow2. On one of my systems, new disk images default to raw. On another system, new disk images default to qcow2. Both are Fedora 20 and I did nothing to either.
3. I tried: "sudo virsh pool-edit default" and adding "<format type=raw'/>" to the definition for <target>. The command executed with no errors when I did ":wq" but the definition was *not* changed.
Are these bugs I need to report or is there something I need to do.
Gene
On 07/20/2014 11:25 AM, Jorge Fábregas wrote:
On 07/20/2014 11:09 AM, Gene Czarcinski wrote:
- I want the default disk image format to be raw rather than qcow2.
Hi Gene,
There's an option in virt-manager for that. Go to Edit --> Preferences : you'll see it on the "New VM' tab.
Thank you.
I must have known this at one time because the system where it was working had that set.
However, that does not explain why virtsh pool-edit default ignored the addition of <format type='raw'>
The documentation says this is something that has been around for a while.
Gene
On 07/21/2014 01:42 AM, Gene Czarcinski wrote:
On 07/20/2014 11:25 AM, Jorge Fábregas wrote:
On 07/20/2014 11:09 AM, Gene Czarcinski wrote:
- I want the default disk image format to be raw rather than qcow2.
Hi Gene,
There's an option in virt-manager for that. Go to Edit --> Preferences : you'll see it on the "New VM' tab.
Thank you.
I must have known this at one time because the system where it was working had that set.
However, that does not explain why virtsh pool-edit default ignored the addition of <format type='raw'>
Because directory pool does not use the pool format type element. You can refer to http://libvirt.org/storage.html
The documentation says this is something that has been around for a while.
Gene _______________________________________________ virt mailing list virt@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/virt
On 07/20/2014 09:38 PM, shyu wrote:
On 07/21/2014 01:42 AM, Gene Czarcinski wrote:
On 07/20/2014 11:25 AM, Jorge Fábregas wrote:
On 07/20/2014 11:09 AM, Gene Czarcinski wrote:
- I want the default disk image format to be raw rather than qcow2.
Hi Gene,
There's an option in virt-manager for that. Go to Edit --> Preferences : you'll see it on the "New VM' tab.
Thank you.
I must have known this at one time because the system where it was working had that set.
However, that does not explain why virtsh pool-edit default ignored the addition of <format type='raw'>
Because directory pool does not use the pool format type element. You can refer to http://libvirt.org/storage.html
Some pools do have a <format> element FWIW
However, in this case, Gene sounds like he's talking about a volume <format> element, since only volumes will ever report qcow2/raw.
Gene, the reason that pool-edit/vol-edit won't work for changing a volume's format from raw to qcow2 is that it's a read only XML value, just reporting what the format of the referenced disk image is. If you want to change the disk image format, you will have to manually use 'qemu-img convert', then do 'sudo virsh pool-refresh <poolname>' of the parent pool and it should pick up the change.
- Cole
-
Cole Robinson -
Gene Czarcinski -
Jorge Fábregas -
shyu