mirrors
/
qemu
mirror of https://gitlab.com/qemu-project/qemu
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

docs/interop/live-block-operations: Do not hard-code the QEMU binary name 

In downstream, we want to use a different name for the QEMU binary,
and some people might also use the docs for non-x86 binaries, that's
why we already created the |qemu_system| placeholder in the past.
Use it now in the live-block-operations doc, too.

Signed-off-by: Thomas Huth <thuth@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Message-Id: <20210607172311.915385-1-thuth@redhat.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>
This commit is contained in:
Thomas Huth 2021-06-07 19:23:11 +02:00
parent 8f521741e1
commit 2c1730f780
1 changed files with 17 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

30
docs/interop/live-block-operations.rst
View File

@ -127,13 +127,15 @@ Interacting with a QEMU instance
To show some example invocations of command-line, we will use the To show some example invocations of command-line, we will use the
following invocation of QEMU, with a QMP server running over UNIX following invocation of QEMU, with a QMP server running over UNIX
socket:: socket:
$ ./qemu-system-x86_64 -display none -no-user-config \ .. parsed-literal::
-M q35 -nodefaults -m 512 \
-blockdev node-name=node-A,driver=qcow2,file.driver=file,file.node-name=file,file.filename=./a.qcow2 \ $ |qemu_system| -display none -no-user-config -nodefaults \\
-device virtio-blk,drive=node-A,id=virtio0 \ -m 512 -blockdev \\
-monitor stdio -qmp unix:/tmp/qmp-sock,server=on,wait=off node-name=node-A,driver=qcow2,file.driver=file,file.node-name=file,file.filename=./a.qcow2 \\
-device virtio-blk,drive=node-A,id=virtio0 \\
-monitor stdio -qmp unix:/tmp/qmp-sock,server=on,wait=off
The ``-blockdev`` command-line option, used above, is available from The ``-blockdev`` command-line option, used above, is available from
QEMU 2.9 onwards. In the above invocation, notice the ``node-name`` QEMU 2.9 onwards. In the above invocation, notice the ``node-name``
@ -692,14 +694,16 @@ And start the destination QEMU (we already have the source QEMU running
-- discussed in the section: `Interacting with a QEMU instance`_) -- discussed in the section: `Interacting with a QEMU instance`_)
instance, with the following invocation. (As noted earlier, for instance, with the following invocation. (As noted earlier, for
simplicity's sake, the destination QEMU is started on the same host, but simplicity's sake, the destination QEMU is started on the same host, but
it could be located elsewhere):: it could be located elsewhere):
$ ./qemu-system-x86_64 -display none -no-user-config \ .. parsed-literal::
-M q35 -nodefaults -m 512 \
-blockdev node-name=node-TargetDisk,driver=qcow2,file.driver=file,file.node-name=file,file.filename=./target-disk.qcow2 \ $ |qemu_system| -display none -no-user-config -nodefaults \\
-device virtio-blk,drive=node-TargetDisk,id=virtio0 \ -m 512 -blockdev \\
-S -monitor stdio -qmp unix:./qmp-sock2,server=on,wait=off \ node-name=node-TargetDisk,driver=qcow2,file.driver=file,file.node-name=file,file.filename=./target-disk.qcow2 \\
-incoming tcp:localhost:6666 -device virtio-blk,drive=node-TargetDisk,id=virtio0 \\
-S -monitor stdio -qmp unix:./qmp-sock2,server=on,wait=off \\
-incoming tcp:localhost:6666
Given the disk image chain on source QEMU:: Given the disk image chain on source QEMU::