Paul Brook wrote:
IMHO there's little value in just printing a warning. Until it actually goes
away, people are liable to assume we're just being paranoid/awkward and keep
using it anyway.
I suggest crippling it now and, assuming noone steps up to fix+maintain it,
ripping out the write support altogether at next release.
I'm assuming the readonly code is in better shape, and can be supported with
relatively little effort.
Yes, that's what I was getting at. We need to support read-only in
order to allow people to convert to qcow2.
If we're sufficiently concerned that there is data corruption in the
write path, we should disable it to keep a user from shooting themselves
in the foot.
Regards,
Anthony Liguori
Paul
--
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
