Hide Forgot
Description of problem: When creating a guest, one selects an os. So we give information to virt-manager of what we intend to run. So virt-manager should just 'hint' wich disk format is better for the guest we are creating. In form of a short description "recommended" in the format combo list. For example "qcow recommended" (with recommended in green). If there is a known problem, the opposite may happend. a "non-recommended" in red. Version-Release number of selected component (if applicable): libvirt.x86_64 0.8.8-7.fc15 @updates libvirt-client.x86_64 0.8.8-7.fc15 @updates libvirt-python.x86_64 0.8.8-7.fc15 @updates virt-manager.noarch 0.8.7-6.fc15 @updates virt-viewer.x86_64 0.3.1-1.fc15 @fedora How reproducible: allways Steps to Reproduce: 1. raw is allways selected by default. Actual results: raw everywhere Expected results: there are different formats for a reason, the decision to use any of them must be show by virt-manager itself. Additional info:
Thanks for the report. However disk image format choice doesn't have anything to do with OS choice. We use raw by default because it is the safest default: older versions of qemu had data integrity issues with qcow2. Also, you can always create a qcow2 image with the 'use managed or existing storage' option in the new vm wizard. Long term we may change the default to qcow2 but it will require some work.