docs/system/pr-manager.rst

9 the operating system restricts sending these commands to unprivileged
13 For this reason, QEMU's SCSI passthrough devices, ``scsi-block``
14 and ``scsi-generic`` (both are only available on Linux) can delegate
18 manager object; other commands are processed by QEMU as usual.
20 -----------------------------------------
22 -----------------------------------------
25 "pr-manager" QOM class.
27 Right now only one subclass is defined, ``pr-manager-helper``, which
30 reservation commands to devices for which QEMU has a file descriptor,
31 so that QEMU will not be able to effect persistent reservations
34 ``pr-manager-helper`` has a single string property, ``path``, which
36 the following command line defines a ``pr-manager-helper`` object and
39       $ qemu-system-x86_64
40           -device virtio-scsi \
41           -object pr-manager-helper,id=helper0,path=/var/run/qemu-pr-helper.sock
42           -drive if=none,id=hd,driver=raw,file.filename=/dev/sdb,file.pr-manager=helper0
43           -device scsi-block,drive=hd
45 Alternatively, using ``-blockdev``::
47       $ qemu-system-x86_64
48           -device virtio-scsi \
49           -object pr-manager-helper,id=helper0,path=/var/run/qemu-pr-helper.sock
50 …-blockdev node-name=hd,driver=raw,file.driver=host_device,file.filename=/dev/sdb,file.pr-manager=h…
51           -device scsi-block,drive=hd
54 :command:`qemu-pr-helper` is running, and that it has been
55 set up to use the same socket filename as your QEMU commandline
56 specifies. See the qemu-pr-helper documentation or manpage for
59 ---------------------------------------------
61 ---------------------------------------------
66 again.  :command:`qemu-pr-helper` can do this if the ``libmpathpersist``
67 library was available on the system at build time.
82 Linking :program:`qemu-pr-helper` to ``libmpathpersist`` does not impede