Cole Robinson ba08f84b34 addstorage: Return to using qcow2 sparse by default ... https://bugzilla.redhat.com/show_bug.cgi?id=1759454 See 15a6a7e210 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>		2020-09-20 10:11:36 -04:00
..
__init__.py	virtManager: move device UI files to virtManager/device/	2019-06-17 00:12:32 -04:00
addstorage.py	addstorage: Return to using qcow2 sparse by default	2020-09-20 10:11:36 -04:00
fsdetails.py	cli: Fill in all --filesystem suboptions	2020-09-11 09:00:33 -04:00
gfxdetails.py	gfxdetails: Update UI a bit	2020-09-01 20:10:34 -04:00
mediacombo.py	virtManager: add coverage annotations and remove dead code	2020-08-26 15:20:05 -04:00
netlist.py	netlist: Remove some leftover print debugging	2020-09-01 18:04:29 -04:00
vsockdetails.py	uitests: Add vsockdetails full coverage	2020-08-26 15:20:05 -04:00