diff options
author | Richard Jones <rjones@redhat.com> | 2010-03-16 21:50:13 +0000 |
---|---|---|
committer | Richard Jones <rjones@redhat.com> | 2010-03-16 21:50:13 +0000 |
commit | 676462684e05dd8341dd695762dd99a87d8ec022 (patch) | |
tree | bf1e674da820e27c1a4b512bd719fa1323506679 /src/MAX_PROC_NR | |
parent | 5442f45aea522a728fa5b06396d4f08d8506d7de (diff) | |
download | libguestfs-676462684e05dd8341dd695762dd99a87d8ec022.tar.gz libguestfs-676462684e05dd8341dd695762dd99a87d8ec022.tar.xz libguestfs-676462684e05dd8341dd695762dd99a87d8ec022.zip |
add_drive_ro adds readonly=on option if available.
Change the add_drive_ro call so it adds the readonly=on option
if qemu supports that.
This just means that qemu will not try to open the drive with
O_RDWR, and should not otherwise change the behaviour of qemu or
libguestfs. (In particular, writes to the read-only drive are
still permitted, and are just discarded when the handle is closed).
However it should alleviate RHBZ#571714 where udev was deciding
to incorrectly relabel a device because we had opened the device
for writing (even though we didn't actually write to it).
Diffstat (limited to 'src/MAX_PROC_NR')
0 files changed, 0 insertions, 0 deletions