Control: fixed 918950 1:2.12+dfsg-3
Control: tags 918950 + upstream
Hello Jakub Wilk, dear Maintainer,
just tried to find out when this started and found it
working with 2.12.
Then tried to build it from git and a bisect leads to
following commit:
eeae6a596b0efc092f5101c67683053e245e6250 is the first bad commit
commit eeae6a596b0efc092f5101c67683053e245e6250
Author: Kevin Wolf <kw...@redhat.com>
Date: Tue Oct 9 16:57:12 2018 +0200
block: Update flags in bdrv_set_read_only()
To fully change the read-only state of a node, we must not only change
bs->read_only, but also update bs->open_flags.
Signed-off-by: Kevin Wolf <kw...@redhat.com>
Reviewed-by: Eric Blake <ebl...@redhat.com>
Reviewed-by: Alberto Garcia <be...@igalia.com>
:100644 100644 9d2adf79623907b42e73482701def00bbc3bb1ea
3132c78f0104b3f9d95d3f715fbfc7e847e504c4 M block.c
Unfortunately there were too much changes until version 3.1
where that patch cannot be reverted anymore.
A workaround, when the drive being writable does not matter,
can be to make it explicitly writable:
qemu-system-x86_64 -hda fat:rw:$(mktemp -d)
To avoid the message about automatic raw image detection
following line could be used:
qemu-system-x86_64 -drive format=raw,file=fat:rw:$(mktemp -d)
Kind regards,
Bernhard
