Control: severity -1 important Hi,
thank you for reporting this bug to Debian. I concur with your analysis; in particular, I appreciate that you're taking into account how the behavior of other virsh commands sets users' expectations which are not matched by blockresize. I encourage you to share your analysis upstream: https://libvirt.org/ https://www.redhat.com/mailman/listinfo/libvir-list This being said, I disagree this bug should block the Buster release and I'm thus challenging its RC severity for 2 reasons: 1. It seems that "virsh blockresize" was introduced, with this behavior, about 7 years ago. I'm not aware of actual data loss reported by Debian users during that time. 2. Considering the target audience of libvirt, which is mostly system administrators rather than non-technical users, it seems reasonable to have slightly higher expectations than usual wrt. reading the blockresize's documentation before using it and wrt. having proper backups, which makes the "causes serious data loss" justification disputable IMHO. Cheers, -- intrigeri
