mirror of
https://github.com/virt-manager/virt-manager.git
synced 2025-01-21 18:03:58 +03:00
ba08f84b34
https://bugzilla.redhat.com/show_bug.cgi?id=1759454 See 15a6a7e2105440df528f75c4df4d2471df28bd1e The idea behind virt-manager's sparse vs nonsparse default, is that if the user selected 'raw' for as the default image format, assume they want to maximize performance, so fully allocate the disk. qcow2 didn't support anything except sparse, so the sparse=True vs sparse=False made no difference. So we always set sparse=False Then qcow2 grows non-sparse support, and virt-manager is suddenly defaulting to it, which is not the intention. Default to sparse when requested format isn't raw Signed-off-by: Cole Robinson <crobinso@redhat.com>