host info: # uname -r && rpm -q qemu-kvm 3.10.0-220.el7.x86_64 qemu-kvm-1.5.3-85.el7.x86_64
Hi Cong, Please update the QA contact.
Bug description got hidden by clone, I hate that. Repeat: rerror/werror require support in the underlying device model. Currently, only ide-hd, ide-cd, ide-drive (legacy), scsi-hd, scsi-cd, scsi-disk (legacy), scsi-block (partially[*]), virtio-blk-device do. Device models that do not support it: isa-fdc, cfi.pflash01, scsi-generic, nvme, ... There are two ways to control rerror & werror: * Device properties "rerror", "werror" Only the devices supporting the feature (whole or in part) provide these properties. They reject values they don't support, if any. The properties are only documented in -device DRIVER,help, as usual. * -drive parameters "rerror", "werror" These predate device properties. Devices supporting the feature fall back to them when the device properties are not set, for backwards compatibility. See commit 8c398252182. When the device doesn't support the feature, they're silently ignored, except for a few devices that take the trouble to reject them. This bug is about documenting the "silently ignored" part. It's tied to -drive; -blockdev does not provide these parameters, Since we're pretty close to ditching -drive for good, there is no need for documenting its minor defects anymore.