Re: [Qemu-devel] [PATCH] Warn if a qcow (not qcow2) file is opened

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Andreas Färber schrieb:
> I'm confused now. Only recently someone stepped up, saying that qcow2  
> was broken and that qcow should be used instead for safety reasons.  
> Now all of a sudden, it's the exact opposite, you're even considering  
> replacing qcow with qcow2 for vvfat and dropping qcow support.

Basically, qcow1 is unmaintained. On the one hand this means that its
code is rarely changed and is quite stable in that respect, on the other
hand it means that nobody cares if it's broken e.g. by changes to the
block layer in general. There is no breakage I know of in the current
stable release, however git master has been broken for a month now.

And I'm pretty sure that qcow2 receives more testing than qcow.

Kevin
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux