9ae3a8
From 7266fe6b09986cfa24d704075d940022cabdc8f5 Mon Sep 17 00:00:00 2001
9ae3a8
From: Miroslav Rezanina <mrezanin@redhat.com>
9ae3a8
Date: Fri, 14 Nov 2014 08:28:01 +0100
9ae3a8
Subject: [PATCH 32/41] ] Use qemu-kvm in documentation instead of
9ae3a8
 qemu-system-i386
9ae3a8
9ae3a8
Message-id: <1415953681-20015-1-git-send-email-mrezanin@redhat.com>
9ae3a8
Patchwork-id: 62376
9ae3a8
O-Subject: [RHEL-7.1 qemu-kvm PATCHv4]] Use qemu-kvm in documentation instead of qemu-system-i386
9ae3a8
Bugzilla: 1140618
9ae3a8
RH-Acked-by: Laszlo Ersek <lersek@redhat.com>
9ae3a8
RH-Acked-by: Markus Armbruster <armbru@redhat.com>
9ae3a8
RH-Acked-by: Stefan Hajnoczi <stefanha@redhat.com>
9ae3a8
9ae3a8
From: Miroslav Rezanina <mrezanin@redhat.com>
9ae3a8
9ae3a8
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1140618
9ae3a8
Brew: http://brewweb.devel.redhat.com/brew/taskinfo?taskID=8244530
9ae3a8
9ae3a8
We change the name and location of qemu-kvm binaries. Update documentation
9ae3a8
to reflect this change.
9ae3a8
9ae3a8
Signed-off-by: Miroslav Rezanina <mrezanin@redhat.com>
9ae3a8
---
9ae3a8
v4:
9ae3a8
 - Replace qemu with qemu-kvm
9ae3a8
9ae3a8
v3:
9ae3a8
 - Use qemu-kvm instead of /usr/libexec/qemu-kvm
9ae3a8
 - Replace qemu-system-x86_64 too
9ae3a8
9ae3a8
v2:
9ae3a8
 - do not replace qemu-system-i386.exe
9ae3a8
---
9ae3a8
 qemu-doc.texi   |  98 ++++++++++++++++++++++-----------------------
9ae3a8
 qemu-options.hx | 120 ++++++++++++++++++++++++++++----------------------------
9ae3a8
 2 files changed, 109 insertions(+), 109 deletions(-)
9ae3a8
9ae3a8
Signed-off-by: Miroslav Rezanina <mrezanin@redhat.com>
9ae3a8
---
9ae3a8
 qemu-doc.texi   |  98 ++++++++++++++++++++++-----------------------
9ae3a8
 qemu-options.hx | 120 ++++++++++++++++++++++++++++----------------------------
9ae3a8
 2 files changed, 109 insertions(+), 109 deletions(-)
9ae3a8
9ae3a8
diff --git a/qemu-doc.texi b/qemu-doc.texi
9ae3a8
index 0f7e5f8..ff124fe 100644
9ae3a8
--- a/qemu-doc.texi
9ae3a8
+++ b/qemu-doc.texi
9ae3a8
@@ -226,12 +226,12 @@ Note that, by default, GUS shares IRQ(7) with parallel ports and so
9ae3a8
 QEMU must be told to not have parallel ports to have working GUS.
9ae3a8
 
9ae3a8
 @example
9ae3a8
-qemu-system-i386 dos.img -soundhw gus -parallel none
9ae3a8
+qemu-kvm dos.img -soundhw gus -parallel none
9ae3a8
 @end example
9ae3a8
 
9ae3a8
 Alternatively:
9ae3a8
 @example
9ae3a8
-qemu-system-i386 dos.img -device gus,irq=5
9ae3a8
+qemu-kvm dos.img -device gus,irq=5
9ae3a8
 @end example
9ae3a8
 
9ae3a8
 Or some other unclaimed IRQ.
9ae3a8
@@ -247,7 +247,7 @@ CS4231A is the chip used in Windows Sound System and GUSMAX products
9ae3a8
 Download and uncompress the linux image (@file{linux.img}) and type:
9ae3a8
 
9ae3a8
 @example
9ae3a8
-qemu-system-i386 linux.img
9ae3a8
+qemu-kvm linux.img
9ae3a8
 @end example
9ae3a8
 
9ae3a8
 Linux should boot and give you a prompt.
9ae3a8
@@ -257,7 +257,7 @@ Linux should boot and give you a prompt.
9ae3a8
 
9ae3a8
 @example
9ae3a8
 @c man begin SYNOPSIS
9ae3a8
-usage: qemu-system-i386 [options] [@var{disk_image}]
9ae3a8
+usage: qemu-kvm [options] [@var{disk_image}]
9ae3a8
 @c man end
9ae3a8
 @end example
9ae3a8
 
9ae3a8
@@ -766,7 +766,7 @@ QEMU can automatically create a virtual FAT disk image from a
9ae3a8
 directory tree. In order to use it, just type:
9ae3a8
 
9ae3a8
 @example
9ae3a8
-qemu-system-i386 linux.img -hdb fat:/my_directory
9ae3a8
+qemu-kvm linux.img -hdb fat:/my_directory
9ae3a8
 @end example
9ae3a8
 
9ae3a8
 Then you access access to all the files in the @file{/my_directory}
9ae3a8
@@ -776,14 +776,14 @@ them via SAMBA or NFS. The default access is @emph{read-only}.
9ae3a8
 Floppies can be emulated with the @code{:floppy:} option:
9ae3a8
 
9ae3a8
 @example
9ae3a8
-qemu-system-i386 linux.img -fda fat:floppy:/my_directory
9ae3a8
+qemu-kvm linux.img -fda fat:floppy:/my_directory
9ae3a8
 @end example
9ae3a8
 
9ae3a8
 A read/write support is available for testing (beta stage) with the
9ae3a8
 @code{:rw:} option:
9ae3a8
 
9ae3a8
 @example
9ae3a8
-qemu-system-i386 linux.img -fda fat:floppy:rw:/my_directory
9ae3a8
+qemu-kvm linux.img -fda fat:floppy:rw:/my_directory
9ae3a8
 @end example
9ae3a8
 
9ae3a8
 What you should @emph{never} do:
9ae3a8
@@ -801,14 +801,14 @@ QEMU can access directly to block device exported using the Network Block Device
9ae3a8
 protocol.
9ae3a8
 
9ae3a8
 @example
9ae3a8
-qemu-system-i386 linux.img -hdb nbd://my_nbd_server.mydomain.org:1024/
9ae3a8
+qemu-kvm linux.img -hdb nbd://my_nbd_server.mydomain.org:1024/
9ae3a8
 @end example
9ae3a8
 
9ae3a8
 If the NBD server is located on the same host, you can use an unix socket instead
9ae3a8
 of an inet socket:
9ae3a8
 
9ae3a8
 @example
9ae3a8
-qemu-system-i386 linux.img -hdb nbd+unix://?socket=/tmp/my_socket
9ae3a8
+qemu-kvm linux.img -hdb nbd+unix://?socket=/tmp/my_socket
9ae3a8
 @end example
9ae3a8
 
9ae3a8
 In this case, the block device must be exported using qemu-nbd:
9ae3a8
@@ -825,23 +825,23 @@ qemu-nbd --socket=/tmp/my_socket --share=2 my_disk.qcow2
9ae3a8
 @noindent
9ae3a8
 and then you can use it with two guests:
9ae3a8
 @example
9ae3a8
-qemu-system-i386 linux1.img -hdb nbd+unix://?socket=/tmp/my_socket
9ae3a8
-qemu-system-i386 linux2.img -hdb nbd+unix://?socket=/tmp/my_socket
9ae3a8
+qemu-kvm linux1.img -hdb nbd+unix://?socket=/tmp/my_socket
9ae3a8
+qemu-kvm linux2.img -hdb nbd+unix://?socket=/tmp/my_socket
9ae3a8
 @end example
9ae3a8
 
9ae3a8
 If the nbd-server uses named exports (supported since NBD 2.9.18, or with QEMU's
9ae3a8
 own embedded NBD server), you must specify an export name in the URI:
9ae3a8
 @example
9ae3a8
-qemu-system-i386 -cdrom nbd://localhost/debian-500-ppc-netinst
9ae3a8
-qemu-system-i386 -cdrom nbd://localhost/openSUSE-11.1-ppc-netinst
9ae3a8
+qemu-kvm -cdrom nbd://localhost/debian-500-ppc-netinst
9ae3a8
+qemu-kvm -cdrom nbd://localhost/openSUSE-11.1-ppc-netinst
9ae3a8
 @end example
9ae3a8
 
9ae3a8
 The URI syntax for NBD is supported since QEMU 1.3.  An alternative syntax is
9ae3a8
 also available.  Here are some example of the older syntax:
9ae3a8
 @example
9ae3a8
-qemu-system-i386 linux.img -hdb nbd:my_nbd_server.mydomain.org:1024
9ae3a8
-qemu-system-i386 linux2.img -hdb nbd:unix:/tmp/my_socket
9ae3a8
-qemu-system-i386 -cdrom nbd:localhost:10809:exportname=debian-500-ppc-netinst
9ae3a8
+qemu-kvm linux.img -hdb nbd:my_nbd_server.mydomain.org:1024
9ae3a8
+qemu-kvm linux2.img -hdb nbd:unix:/tmp/my_socket
9ae3a8
+qemu-kvm -cdrom nbd:localhost:10809:exportname=debian-500-ppc-netinst
9ae3a8
 @end example
9ae3a8
 
9ae3a8
 @node disk_images_sheepdog
9ae3a8
@@ -866,7 +866,7 @@ qemu-img convert @var{filename} sheepdog:///@var{image}
9ae3a8
 
9ae3a8
 You can boot from the Sheepdog disk image with the command:
9ae3a8
 @example
9ae3a8
-qemu-system-i386 sheepdog:///@var{image}
9ae3a8
+qemu-kvm sheepdog:///@var{image}
9ae3a8
 @end example
9ae3a8
 
9ae3a8
 You can also create a snapshot of the Sheepdog image like qcow2.
9ae3a8
@@ -878,7 +878,7 @@ where @var{tag} is a tag name of the newly created snapshot.
9ae3a8
 To boot from the Sheepdog snapshot, specify the tag name of the
9ae3a8
 snapshot.
9ae3a8
 @example
9ae3a8
-qemu-system-i386 sheepdog:///@var{image}#@var{tag}
9ae3a8
+qemu-kvm sheepdog:///@var{image}#@var{tag}
9ae3a8
 @end example
9ae3a8
 
9ae3a8
 You can create a cloned image from the existing snapshot.
9ae3a8
@@ -891,14 +891,14 @@ is its tag name.
9ae3a8
 You can use an unix socket instead of an inet socket:
9ae3a8
 
9ae3a8
 @example
9ae3a8
-qemu-system-i386 sheepdog+unix:///@var{image}?socket=@var{path}
9ae3a8
+qemu-kvm sheepdog+unix:///@var{image}?socket=@var{path}
9ae3a8
 @end example
9ae3a8
 
9ae3a8
 If the Sheepdog daemon doesn't run on the local host, you need to
9ae3a8
 specify one of the Sheepdog servers to connect to.
9ae3a8
 @example
9ae3a8
 qemu-img create sheepdog://@var{hostname}:@var{port}/@var{image} @var{size}
9ae3a8
-qemu-system-i386 sheepdog://@var{hostname}:@var{port}/@var{image}
9ae3a8
+qemu-kvm sheepdog://@var{hostname}:@var{port}/@var{image}
9ae3a8
 @end example
9ae3a8
 
9ae3a8
 @node disk_images_iscsi
9ae3a8
@@ -940,7 +940,7 @@ Various session related parameters can be set via special options, either
9ae3a8
 in a configuration file provided via '-readconfig' or directly on the
9ae3a8
 command line.
9ae3a8
 
9ae3a8
-If the initiator-name is not specified qemu will use a default name
9ae3a8
+If the initiator-name is not specified qemu-kvm will use a default name
9ae3a8
 of 'iqn.2008-11.org.linux-kvm[:<name>'] where <name> is the name of the
9ae3a8
 virtual machine.
9ae3a8
 
9ae3a8
@@ -987,7 +987,7 @@ cat >iscsi.conf <
9ae3a8
   header-digest = "CRC32C"
9ae3a8
 EOF
9ae3a8
 
9ae3a8
-qemu-system-i386 -drive file=iscsi://127.0.0.1/iqn.qemu.test/1 \
9ae3a8
+qemu-kvm -drive file=iscsi://127.0.0.1/iqn.qemu.test/1 \
9ae3a8
     -readconfig iscsi.conf
9ae3a8
 @end example
9ae3a8
 
9ae3a8
@@ -1006,7 +1006,7 @@ tgtadm --lld iscsi --mode logicalunit --op new --tid 1 --lun 2 \
9ae3a8
     -b /IMAGES/cd.iso --device-type=cd
9ae3a8
 tgtadm --lld iscsi --op bind --mode target --tid 1 -I ALL
9ae3a8
 
9ae3a8
-qemu-system-i386 -iscsi initiator-name=iqn.qemu.test:my-initiator \
9ae3a8
+qemu-kvm -iscsi initiator-name=iqn.qemu.test:my-initiator \
9ae3a8
     -boot d -drive file=iscsi://127.0.0.1/iqn.qemu.test/1 \
9ae3a8
     -cdrom iscsi://127.0.0.1/iqn.qemu.test/2
9ae3a8
 @end example
9ae3a8
@@ -1018,7 +1018,7 @@ GlusterFS is an user space distributed file system.
9ae3a8
 
9ae3a8
 You can boot from the GlusterFS disk image with the command:
9ae3a8
 @example
9ae3a8
-qemu-system-x86_64 -drive file=gluster[+@var{transport}]://[@var{server}[:@var{port}]]/@var{volname}/@var{image}[?socket=...]
9ae3a8
+qemu-kvm -drive file=gluster[+@var{transport}]://[@var{server}[:@var{port}]]/@var{volname}/@var{image}[?socket=...]
9ae3a8
 @end example
9ae3a8
 
9ae3a8
 @var{gluster} is the protocol.
9ae3a8
@@ -1051,14 +1051,14 @@ qemu-img create gluster://@var{server}/@var{volname}/@var{image} @var{size}
9ae3a8
 
9ae3a8
 Examples
9ae3a8
 @example
9ae3a8
-qemu-system-x86_64 -drive file=gluster://1.2.3.4/testvol/a.img
9ae3a8
-qemu-system-x86_64 -drive file=gluster+tcp://1.2.3.4/testvol/a.img
9ae3a8
-qemu-system-x86_64 -drive file=gluster+tcp://1.2.3.4:24007/testvol/dir/a.img
9ae3a8
-qemu-system-x86_64 -drive file=gluster+tcp://[1:2:3:4:5:6:7:8]/testvol/dir/a.img
9ae3a8
-qemu-system-x86_64 -drive file=gluster+tcp://[1:2:3:4:5:6:7:8]:24007/testvol/dir/a.img
9ae3a8
-qemu-system-x86_64 -drive file=gluster+tcp://server.domain.com:24007/testvol/dir/a.img
9ae3a8
-qemu-system-x86_64 -drive file=gluster+unix:///testvol/dir/a.img?socket=/tmp/glusterd.socket
9ae3a8
-qemu-system-x86_64 -drive file=gluster+rdma://1.2.3.4:24007/testvol/a.img
9ae3a8
+qemu-kvm -drive file=gluster://1.2.3.4/testvol/a.img
9ae3a8
+qemu-kvm -drive file=gluster+tcp://1.2.3.4/testvol/a.img
9ae3a8
+qemu-kvm -drive file=gluster+tcp://1.2.3.4:24007/testvol/dir/a.img
9ae3a8
+qemu-kvm -drive file=gluster+tcp://[1:2:3:4:5:6:7:8]/testvol/dir/a.img
9ae3a8
+qemu-kvm -drive file=gluster+tcp://[1:2:3:4:5:6:7:8]:24007/testvol/dir/a.img
9ae3a8
+qemu-kvm -drive file=gluster+tcp://server.domain.com:24007/testvol/dir/a.img
9ae3a8
+qemu-kvm -drive file=gluster+unix:///testvol/dir/a.img?socket=/tmp/glusterd.socket
9ae3a8
+qemu-kvm -drive file=gluster+rdma://1.2.3.4:24007/testvol/a.img
9ae3a8
 @end example
9ae3a8
 
9ae3a8
 @node disk_images_ssh
9ae3a8
@@ -1068,13 +1068,13 @@ You can access disk images located on a remote ssh server
9ae3a8
 by using the ssh protocol:
9ae3a8
 
9ae3a8
 @example
9ae3a8
-qemu-system-x86_64 -drive file=ssh://[@var{user}@@]@var{server}[:@var{port}]/@var{path}[?host_key_check=@var{host_key_check}]
9ae3a8
+qemu-kvm -drive file=ssh://[@var{user}@@]@var{server}[:@var{port}]/@var{path}[?host_key_check=@var{host_key_check}]
9ae3a8
 @end example
9ae3a8
 
9ae3a8
 Alternative syntax using properties:
9ae3a8
 
9ae3a8
 @example
9ae3a8
-qemu-system-x86_64 -drive file.driver=ssh[,file.user=@var{user}],file.host=@var{server}[,file.port=@var{port}],file.path=@var{path}[,file.host_key_check=@var{host_key_check}]
9ae3a8
+qemu-kvm -drive file.driver=ssh[,file.user=@var{user}],file.host=@var{server}[,file.port=@var{port}],file.path=@var{path}[,file.host_key_check=@var{host_key_check}]
9ae3a8
 @end example
9ae3a8
 
9ae3a8
 @var{ssh} is the protocol.
9ae3a8
@@ -1211,7 +1211,7 @@ zero-copy communication to the application level of the guests.  The basic
9ae3a8
 syntax is:
9ae3a8
 
9ae3a8
 @example
9ae3a8
-qemu-system-i386 -device ivshmem,size=<size in="" format="" accepted="" by="" -m="">[,shm=<shm name="">]
9ae3a8
+qemu-kvm -device ivshmem,size=<size in="" format="" accepted="" by="" -m="">[,shm=<shm name="">]
9ae3a8
 @end example
9ae3a8
 
9ae3a8
 If desired, interrupts can be sent between guest VMs accessing the same shared
9ae3a8
@@ -1221,9 +1221,9 @@ is qemu.git/contrib/ivshmem-server.  An example syntax when using the shared
9ae3a8
 memory server is:
9ae3a8
 
9ae3a8
 @example
9ae3a8
-qemu-system-i386 -device ivshmem,size=<size in="" format="" accepted="" by="" -m="">[,chardev=<id>]
9ae3a8
+qemu-kvm -device ivshmem,size=<size in="" format="" accepted="" by="" -m="">[,chardev=<id>]
9ae3a8
                  [,msi=on][,ioeventfd=on][,vectors=n][,role=peer|master]
9ae3a8
-qemu-system-i386 -chardev socket,path=<path>,id=<id>
9ae3a8
+qemu-kvm -chardev socket,path=<path>,id=<id>
9ae3a8
 @end example
9ae3a8
 
9ae3a8
 When using the server, the guest will be assigned a VM ID (>=0) that allows guests
9ae3a8
@@ -1253,7 +1253,7 @@ kernel testing.
9ae3a8
 
9ae3a8
 The syntax is:
9ae3a8
 @example
9ae3a8
-qemu-system-i386 -kernel arch/i386/boot/bzImage -hda root-2.4.20.img -append "root=/dev/hda"
9ae3a8
+qemu-kvm -kernel arch/i386/boot/bzImage -hda root-2.4.20.img -append "root=/dev/hda"
9ae3a8
 @end example
9ae3a8
 
9ae3a8
 Use @option{-kernel} to provide the Linux kernel image and
9ae3a8
@@ -1268,7 +1268,7 @@ If you do not need graphical output, you can disable it and redirect
9ae3a8
 the virtual serial port and the QEMU monitor to the console with the
9ae3a8
 @option{-nographic} option. The typical command line is:
9ae3a8
 @example
9ae3a8
-qemu-system-i386 -kernel arch/i386/boot/bzImage -hda root-2.4.20.img \
9ae3a8
+qemu-kvm -kernel arch/i386/boot/bzImage -hda root-2.4.20.img \
9ae3a8
                  -append "root=/dev/hda console=ttyS0" -nographic
9ae3a8
 @end example
9ae3a8
 
9ae3a8
@@ -1332,7 +1332,7 @@ Network adapter that supports CDC ethernet and RNDIS protocols.  @var{options}
9ae3a8
 specifies NIC options as with @code{-net nic,}@var{options} (see description).
9ae3a8
 For instance, user-mode networking can be used with
9ae3a8
 @example
9ae3a8
-qemu-system-i386 [...OPTIONS...] -net user,vlan=0 -usbdevice net:vlan=0
9ae3a8
+qemu-kvm [...OPTIONS...] -net user,vlan=0 -usbdevice net:vlan=0
9ae3a8
 @end example
9ae3a8
 Currently this cannot be used in machines that support PCI NICs.
9ae3a8
 @item bt[:@var{hci-type}]
9ae3a8
@@ -1342,7 +1342,7 @@ no type is given, the HCI logic corresponds to @code{-bt hci,vlan=0}.
9ae3a8
 This USB device implements the USB Transport Layer of HCI.  Example
9ae3a8
 usage:
9ae3a8
 @example
9ae3a8
-qemu-system-i386 [...OPTIONS...] -usbdevice bt:hci,vlan=3 -bt device:keyboard,vlan=3
9ae3a8
+qemu-kvm [...OPTIONS...] -usbdevice bt:hci,vlan=3 -bt device:keyboard,vlan=3
9ae3a8
 @end example
9ae3a8
 @end table
9ae3a8
 
9ae3a8
@@ -1420,7 +1420,7 @@ For this setup it is recommended to restrict it to listen on a UNIX domain
9ae3a8
 socket only. For example
9ae3a8
 
9ae3a8
 @example
9ae3a8
-qemu-system-i386 [...OPTIONS...] -vnc unix:/home/joebloggs/.qemu-myvm-vnc
9ae3a8
+qemu-kvm [...OPTIONS...] -vnc unix:/home/joebloggs/.qemu-myvm-vnc
9ae3a8
 @end example
9ae3a8
 
9ae3a8
 This ensures that only users on local box with read/write access to that
9ae3a8
@@ -1443,7 +1443,7 @@ is running the password is set with the monitor. Until the monitor is used to
9ae3a8
 set the password all clients will be rejected.
9ae3a8
 
9ae3a8
 @example
9ae3a8
-qemu-system-i386 [...OPTIONS...] -vnc :1,password -monitor stdio
9ae3a8
+qemu-kvm [...OPTIONS...] -vnc :1,password -monitor stdio
9ae3a8
 (qemu) change vnc password
9ae3a8
 Password: ********
9ae3a8
 (qemu)
9ae3a8
@@ -1460,7 +1460,7 @@ support provides a secure session, but no authentication. This allows any
9ae3a8
 client to connect, and provides an encrypted session.
9ae3a8
 
9ae3a8
 @example
9ae3a8
-qemu-system-i386 [...OPTIONS...] -vnc :1,tls,x509=/etc/pki/qemu -monitor stdio
9ae3a8
+qemu-kvm [...OPTIONS...] -vnc :1,tls,x509=/etc/pki/qemu -monitor stdio
9ae3a8
 @end example
9ae3a8
 
9ae3a8
 In the above example @code{/etc/pki/qemu} should contain at least three files,
9ae3a8
@@ -1478,7 +1478,7 @@ then validate against the CA certificate. This is a good choice if deploying
9ae3a8
 in an environment with a private internal certificate authority.
9ae3a8
 
9ae3a8
 @example
9ae3a8
-qemu-system-i386 [...OPTIONS...] -vnc :1,tls,x509verify=/etc/pki/qemu -monitor stdio
9ae3a8
+qemu-kvm [...OPTIONS...] -vnc :1,tls,x509verify=/etc/pki/qemu -monitor stdio
9ae3a8
 @end example
9ae3a8
 
9ae3a8
 
9ae3a8
@@ -1489,7 +1489,7 @@ Finally, the previous method can be combined with VNC password authentication
9ae3a8
 to provide two layers of authentication for clients.
9ae3a8
 
9ae3a8
 @example
9ae3a8
-qemu-system-i386 [...OPTIONS...] -vnc :1,password,tls,x509verify=/etc/pki/qemu -monitor stdio
9ae3a8
+qemu-kvm [...OPTIONS...] -vnc :1,password,tls,x509verify=/etc/pki/qemu -monitor stdio
9ae3a8
 (qemu) change vnc password
9ae3a8
 Password: ********
9ae3a8
 (qemu)
9ae3a8
@@ -1512,7 +1512,7 @@ used for authentication, but assuming use of one supporting SSF,
9ae3a8
 then QEMU can be launched with:
9ae3a8
 
9ae3a8
 @example
9ae3a8
-qemu-system-i386 [...OPTIONS...] -vnc :1,sasl -monitor stdio
9ae3a8
+qemu-kvm [...OPTIONS...] -vnc :1,sasl -monitor stdio
9ae3a8
 @end example
9ae3a8
 
9ae3a8
 @node vnc_sec_certificate_sasl
9ae3a8
@@ -1526,7 +1526,7 @@ credentials. This can be enabled, by combining the 'sasl' option
9ae3a8
 with the aforementioned TLS + x509 options:
9ae3a8
 
9ae3a8
 @example
9ae3a8
-qemu-system-i386 [...OPTIONS...] -vnc :1,tls,x509,sasl -monitor stdio
9ae3a8
+qemu-kvm [...OPTIONS...] -vnc :1,tls,x509,sasl -monitor stdio
9ae3a8
 @end example
9ae3a8
 
9ae3a8
 
9ae3a8
@@ -1694,7 +1694,7 @@ QEMU has a primitive support to work with gdb, so that you can do
9ae3a8
 In order to use gdb, launch QEMU with the '-s' option. It will wait for a
9ae3a8
 gdb connection:
9ae3a8
 @example
9ae3a8
-qemu-system-i386 -s -kernel arch/i386/boot/bzImage -hda root-2.4.20.img \
9ae3a8
+qemu-kvm -s -kernel arch/i386/boot/bzImage -hda root-2.4.20.img \
9ae3a8
                     -append "root=/dev/hda"
9ae3a8
 Connected to host network interface: tun0
9ae3a8
 Waiting gdb connection on port 1234
9ae3a8
diff --git a/qemu-options.hx b/qemu-options.hx
9ae3a8
index 5d0f2cd..62c3e06 100644
9ae3a8
--- a/qemu-options.hx
9ae3a8
+++ b/qemu-options.hx
9ae3a8
@@ -124,7 +124,7 @@ This option defines a free-form string that can be used to describe @var{fd}.
9ae3a8
 
9ae3a8
 You can open an image using pre-opened file descriptors from an fd set:
9ae3a8
 @example
9ae3a8
-qemu-system-i386
9ae3a8
+qemu-kvm
9ae3a8
 -add-fd fd=3,set=2,opaque="rdwr:/path/to/file"
9ae3a8
 -add-fd fd=4,set=2,opaque="rdonly:/path/to/file"
9ae3a8
 -drive file=/dev/fdset/2,index=0,media=disk
9ae3a8
@@ -151,7 +151,7 @@ STEXI
9ae3a8
 Set default value of @var{driver}'s property @var{prop} to @var{value}, e.g.:
9ae3a8
 
9ae3a8
 @example
9ae3a8
-qemu-system-i386 -global ide-drive.physical_block_size=4096 -drive file=file,if=ide,index=0,media=disk
9ae3a8
+qemu-kvm -global ide-drive.physical_block_size=4096 -drive file=file,if=ide,index=0,media=disk
9ae3a8
 @end example
9ae3a8
 
9ae3a8
 In particular, you can use this to set driver properties for devices which are 
9ae3a8
@@ -189,7 +189,7 @@ the recommended is 320x240, 640x480, 800x640.
9ae3a8
 
9ae3a8
 A timeout could be passed to bios, guest will pause for @var{rb_timeout} ms
9ae3a8
 when boot failed, then reboot. If @var{rb_timeout} is '-1', guest will not
9ae3a8
-reboot, qemu passes '-1' to bios by default. Currently Seabios for X86
9ae3a8
+reboot, qemu-kvm passes '-1' to bios by default. Currently Seabios for X86
9ae3a8
 system support it.
9ae3a8
 
9ae3a8
 Do strict boot via @option{strict=on} as far as firmware/BIOS
9ae3a8
@@ -198,11 +198,11 @@ bootindex options. The default is non-strict boot.
9ae3a8
 
9ae3a8
 @example
9ae3a8
 # try to boot from network first, then from hard disk
9ae3a8
-qemu-system-i386 -boot order=nc
9ae3a8
+qemu-kvm -boot order=nc
9ae3a8
 # boot from CD-ROM first, switch back to default order after reboot
9ae3a8
-qemu-system-i386 -boot once=d
9ae3a8
+qemu-kvm -boot once=d
9ae3a8
 # boot with a splash picture for 5 seconds.
9ae3a8
-qemu-system-i386 -boot menu=on,splash=/root/boot.bmp,splash-time=5000
9ae3a8
+qemu-kvm -boot menu=on,splash=/root/boot.bmp,splash-time=5000
9ae3a8
 @end example
9ae3a8
 
9ae3a8
 Note: The legacy format '-boot @var{drives}' is still supported but its
9ae3a8
@@ -282,12 +282,12 @@ Enable audio and selected sound hardware. Use 'help' to print all
9ae3a8
 available sound hardware.
9ae3a8
 
9ae3a8
 @example
9ae3a8
-qemu-system-i386 -soundhw sb16,adlib disk.img
9ae3a8
-qemu-system-i386 -soundhw es1370 disk.img
9ae3a8
-qemu-system-i386 -soundhw ac97 disk.img
9ae3a8
-qemu-system-i386 -soundhw hda disk.img
9ae3a8
-qemu-system-i386 -soundhw all disk.img
9ae3a8
-qemu-system-i386 -soundhw help
9ae3a8
+qemu-kvm -soundhw sb16,adlib disk.img
9ae3a8
+qemu-kvm -soundhw es1370 disk.img
9ae3a8
+qemu-kvm -soundhw ac97 disk.img
9ae3a8
+qemu-kvm -soundhw hda disk.img
9ae3a8
+qemu-kvm -soundhw all disk.img
9ae3a8
+qemu-kvm -soundhw help
9ae3a8
 @end example
9ae3a8
 
9ae3a8
 Note that Linux's i810_audio OSS kernel (for AC97) module might
9ae3a8
@@ -500,21 +500,21 @@ is off.
9ae3a8
 
9ae3a8
 Instead of @option{-cdrom} you can use:
9ae3a8
 @example
9ae3a8
-qemu-system-i386 -drive file=file,index=2,media=cdrom
9ae3a8
+qemu-kvm -drive file=file,index=2,media=cdrom
9ae3a8
 @end example
9ae3a8
 
9ae3a8
 Instead of @option{-hda}, @option{-hdb}, @option{-hdc}, @option{-hdd}, you can
9ae3a8
 use:
9ae3a8
 @example
9ae3a8
-qemu-system-i386 -drive file=file,index=0,media=disk
9ae3a8
-qemu-system-i386 -drive file=file,index=1,media=disk
9ae3a8
-qemu-system-i386 -drive file=file,index=2,media=disk
9ae3a8
-qemu-system-i386 -drive file=file,index=3,media=disk
9ae3a8
+qemu-kvm -drive file=file,index=0,media=disk
9ae3a8
+qemu-kvm -drive file=file,index=1,media=disk
9ae3a8
+qemu-kvm -drive file=file,index=2,media=disk
9ae3a8
+qemu-kvm -drive file=file,index=3,media=disk
9ae3a8
 @end example
9ae3a8
 
9ae3a8
 You can open an image using pre-opened file descriptors from an fd set:
9ae3a8
 @example
9ae3a8
-qemu-system-i386
9ae3a8
+qemu-kvm
9ae3a8
 -add-fd fd=3,set=2,opaque="rdwr:/path/to/file"
9ae3a8
 -add-fd fd=4,set=2,opaque="rdonly:/path/to/file"
9ae3a8
 -drive file=/dev/fdset/2,index=0,media=disk
9ae3a8
@@ -522,33 +522,33 @@ qemu-system-i386
9ae3a8
 
9ae3a8
 You can connect a CDROM to the slave of ide0:
9ae3a8
 @example
9ae3a8
-qemu-system-i386 -drive file=file,if=ide,index=1,media=cdrom
9ae3a8
+qemu-kvm -drive file=file,if=ide,index=1,media=cdrom
9ae3a8
 @end example
9ae3a8
 
9ae3a8
 If you don't specify the "file=" argument, you define an empty drive:
9ae3a8
 @example
9ae3a8
-qemu-system-i386 -drive if=ide,index=1,media=cdrom
9ae3a8
+qemu-kvm -drive if=ide,index=1,media=cdrom
9ae3a8
 @end example
9ae3a8
 
9ae3a8
 You can connect a SCSI disk with unit ID 6 on the bus #0:
9ae3a8
 @example
9ae3a8
-qemu-system-i386 -drive file=file,if=scsi,bus=0,unit=6
9ae3a8
+qemu-kvm -drive file=file,if=scsi,bus=0,unit=6
9ae3a8
 @end example
9ae3a8
 
9ae3a8
 Instead of @option{-fda}, @option{-fdb}, you can use:
9ae3a8
 @example
9ae3a8
-qemu-system-i386 -drive file=file,index=0,if=floppy
9ae3a8
-qemu-system-i386 -drive file=file,index=1,if=floppy
9ae3a8
+qemu-kvm -drive file=file,index=0,if=floppy
9ae3a8
+qemu-kvm -drive file=file,index=1,if=floppy
9ae3a8
 @end example
9ae3a8
 
9ae3a8
 By default, @var{interface} is "ide" and @var{index} is automatically
9ae3a8
 incremented:
9ae3a8
 @example
9ae3a8
-qemu-system-i386 -drive file=a -drive file=b"
9ae3a8
+qemu-kvm -drive file=a -drive file=b"
9ae3a8
 @end example
9ae3a8
 is interpreted like:
9ae3a8
 @example
9ae3a8
-qemu-system-i386 -hda a -hdb b
9ae3a8
+qemu-kvm -hda a -hdb b
9ae3a8
 @end example
9ae3a8
 ETEXI
9ae3a8
 
9ae3a8
@@ -1477,7 +1477,7 @@ can not be resolved.
9ae3a8
 
9ae3a8
 Example:
9ae3a8
 @example
9ae3a8
-qemu -net user,dnssearch=mgmt.example.org,dnssearch=example.org [...]
9ae3a8
+qemu-kvm -net user,dnssearch=mgmt.example.org,dnssearch=example.org [...]
9ae3a8
 @end example
9ae3a8
 
9ae3a8
 @item tftp=@var{dir}
9ae3a8
@@ -1493,7 +1493,7 @@ a guest from a local directory.
9ae3a8
 
9ae3a8
 Example (using pxelinux):
9ae3a8
 @example
9ae3a8
-qemu-system-i386 -hda linux.img -boot n -net user,tftp=/path/to/tftp/files,bootfile=/pxelinux.0
9ae3a8
+qemu-kvm -hda linux.img -boot n -net user,tftp=/path/to/tftp/files,bootfile=/pxelinux.0
9ae3a8
 @end example
9ae3a8
 
9ae3a8
 @item smb=@var{dir}[,smbserver=@var{addr}]
9ae3a8
@@ -1528,7 +1528,7 @@ screen 0, use the following:
9ae3a8
 
9ae3a8
 @example
9ae3a8
 # on the host
9ae3a8
-qemu-system-i386 -net user,hostfwd=tcp:127.0.0.1:6001-:6000 [...]
9ae3a8
+qemu-kvm -net user,hostfwd=tcp:127.0.0.1:6001-:6000 [...]
9ae3a8
 # this host xterm should open in the guest X11 server
9ae3a8
 xterm -display :1
9ae3a8
 @end example
9ae3a8
@@ -1538,7 +1538,7 @@ the guest, use the following:
9ae3a8
 
9ae3a8
 @example
9ae3a8
 # on the host
9ae3a8
-qemu-system-i386 -net user,hostfwd=tcp::5555-:23 [...]
9ae3a8
+qemu-kvm -net user,hostfwd=tcp::5555-:23 [...]
9ae3a8
 telnet localhost 5555
9ae3a8
 @end example
9ae3a8
 
9ae3a8
@@ -1557,7 +1557,7 @@ lifetime, like in the following example:
9ae3a8
 @example
9ae3a8
 # open 10.10.1.1:4321 on bootup, connect 10.0.2.100:1234 to it whenever
9ae3a8
 # the guest accesses it
9ae3a8
-qemu -net user,guestfwd=tcp:10.0.2.100:1234-tcp:10.10.1.1:4321 [...]
9ae3a8
+qemu-kvm -net user,guestfwd=tcp:10.0.2.100:1234-tcp:10.10.1.1:4321 [...]
9ae3a8
 @end example
9ae3a8
 
9ae3a8
 Or you can execute a command on every TCP connection established by the guest,
9ae3a8
@@ -1566,7 +1566,7 @@ so that QEMU behaves similar to an inetd process for that virtual server:
9ae3a8
 @example
9ae3a8
 # call "netcat 10.10.1.1 4321" on every TCP connection to 10.0.2.100:1234
9ae3a8
 # and connect the TCP stream to its stdin/stdout
9ae3a8
-qemu -net 'user,guestfwd=tcp:10.0.2.100:1234-cmd:netcat 10.10.1.1 4321'
9ae3a8
+qemu-kvm -net 'user,guestfwd=tcp:10.0.2.100:1234-cmd:netcat 10.10.1.1 4321'
9ae3a8
 @end example
9ae3a8
 
9ae3a8
 @end table
9ae3a8
@@ -1598,13 +1598,13 @@ Examples:
9ae3a8
 
9ae3a8
 @example
9ae3a8
 #launch a QEMU instance with the default network script
9ae3a8
-qemu-system-i386 linux.img -net nic -net tap
9ae3a8
+qemu-kvm linux.img -net nic -net tap
9ae3a8
 @end example
9ae3a8
 
9ae3a8
 @example
9ae3a8
 #launch a QEMU instance with two NICs, each one connected
9ae3a8
 #to a TAP device
9ae3a8
-qemu-system-i386 linux.img \
9ae3a8
+qemu-kvm linux.img \
9ae3a8
                  -net nic,vlan=0 -net tap,vlan=0,ifname=tap0 \
9ae3a8
                  -net nic,vlan=1 -net tap,vlan=1,ifname=tap1
9ae3a8
 @end example
9ae3a8
@@ -1612,7 +1612,7 @@ qemu-system-i386 linux.img \
9ae3a8
 @example
9ae3a8
 #launch a QEMU instance with the default network helper to
9ae3a8
 #connect a TAP device to bridge br0
9ae3a8
-qemu-system-i386 linux.img \
9ae3a8
+qemu-kvm linux.img \
9ae3a8
                  -net nic -net tap,"helper=/path/to/qemu-bridge-helper"
9ae3a8
 @end example
9ae3a8
 
9ae3a8
@@ -1630,13 +1630,13 @@ Examples:
9ae3a8
 @example
9ae3a8
 #launch a QEMU instance with the default network helper to
9ae3a8
 #connect a TAP device to bridge br0
9ae3a8
-qemu-system-i386 linux.img -net bridge -net nic,model=virtio
9ae3a8
+qemu-kvm linux.img -net bridge -net nic,model=virtio
9ae3a8
 @end example
9ae3a8
 
9ae3a8
 @example
9ae3a8
 #launch a QEMU instance with the default network helper to
9ae3a8
 #connect a TAP device to bridge qemubr0
9ae3a8
-qemu-system-i386 linux.img -net bridge,br=qemubr0 -net nic,model=virtio
9ae3a8
+qemu-kvm linux.img -net bridge,br=qemubr0 -net nic,model=virtio
9ae3a8
 @end example
9ae3a8
 
9ae3a8
 @item -netdev socket,id=@var{id}[,fd=@var{h}][,listen=[@var{host}]:@var{port}][,connect=@var{host}:@var{port}]
9ae3a8
@@ -1652,12 +1652,12 @@ specifies an already opened TCP socket.
9ae3a8
 Example:
9ae3a8
 @example
9ae3a8
 # launch a first QEMU instance
9ae3a8
-qemu-system-i386 linux.img \
9ae3a8
+qemu-kvm linux.img \
9ae3a8
                  -net nic,macaddr=52:54:00:12:34:56 \
9ae3a8
                  -net socket,listen=:1234
9ae3a8
 # connect the VLAN 0 of this instance to the VLAN 0
9ae3a8
 # of the first instance
9ae3a8
-qemu-system-i386 linux.img \
9ae3a8
+qemu-kvm linux.img \
9ae3a8
                  -net nic,macaddr=52:54:00:12:34:57 \
9ae3a8
                  -net socket,connect=127.0.0.1:1234
9ae3a8
 @end example
9ae3a8
@@ -1683,15 +1683,15 @@ Use @option{fd=h} to specify an already opened UDP multicast socket.
9ae3a8
 Example:
9ae3a8
 @example
9ae3a8
 # launch one QEMU instance
9ae3a8
-qemu-system-i386 linux.img \
9ae3a8
+qemu-kvm linux.img \
9ae3a8
                  -net nic,macaddr=52:54:00:12:34:56 \
9ae3a8
                  -net socket,mcast=230.0.0.1:1234
9ae3a8
 # launch another QEMU instance on same "bus"
9ae3a8
-qemu-system-i386 linux.img \
9ae3a8
+qemu-kvm linux.img \
9ae3a8
                  -net nic,macaddr=52:54:00:12:34:57 \
9ae3a8
                  -net socket,mcast=230.0.0.1:1234
9ae3a8
 # launch yet another QEMU instance on same "bus"
9ae3a8
-qemu-system-i386 linux.img \
9ae3a8
+qemu-kvm linux.img \
9ae3a8
                  -net nic,macaddr=52:54:00:12:34:58 \
9ae3a8
                  -net socket,mcast=230.0.0.1:1234
9ae3a8
 @end example
9ae3a8
@@ -1700,7 +1700,7 @@ Example (User Mode Linux compat.):
9ae3a8
 @example
9ae3a8
 # launch QEMU instance (note mcast address selected
9ae3a8
 # is UML's default)
9ae3a8
-qemu-system-i386 linux.img \
9ae3a8
+qemu-kvm linux.img \
9ae3a8
                  -net nic,macaddr=52:54:00:12:34:56 \
9ae3a8
                  -net socket,mcast=239.192.168.1:1102
9ae3a8
 # launch UML
9ae3a8
@@ -1709,7 +1709,7 @@ qemu-system-i386 linux.img \
9ae3a8
 
9ae3a8
 Example (send packets from host's 1.2.3.4):
9ae3a8
 @example
9ae3a8
-qemu-system-i386 linux.img \
9ae3a8
+qemu-kvm linux.img \
9ae3a8
                  -net nic,macaddr=52:54:00:12:34:56 \
9ae3a8
                  -net socket,mcast=239.192.168.1:1102,localaddr=1.2.3.4
9ae3a8
 @end example
9ae3a8
@@ -1727,7 +1727,7 @@ Example:
9ae3a8
 # launch vde switch
9ae3a8
 vde_switch -F -sock /tmp/myswitch
9ae3a8
 # launch QEMU instance
9ae3a8
-qemu-system-i386 linux.img -net nic -net vde,sock=/tmp/myswitch
9ae3a8
+qemu-kvm linux.img -net nic -net vde,sock=/tmp/myswitch
9ae3a8
 @end example
9ae3a8
 
9ae3a8
 @item -netdev hubport,id=@var{id},hubid=@var{hubid}
9ae3a8
@@ -2043,28 +2043,28 @@ images for the guest storage. Both disk and cdrom images are supported.
9ae3a8
 Syntax for specifying iSCSI LUNs is
9ae3a8
 ``iscsi://<target-ip>[:<port>]/<target-iqn>/<lun>''
9ae3a8
 
9ae3a8
-By default qemu will use the iSCSI initiator-name
9ae3a8
+By default qemu-kvm will use the iSCSI initiator-name
9ae3a8
 'iqn.2008-11.org.linux-kvm[:<name>]' but this can also be set from the command
9ae3a8
 line or a configuration file.
9ae3a8
 
9ae3a8
 
9ae3a8
 Example (without authentication):
9ae3a8
 @example
9ae3a8
-qemu-system-i386 -iscsi initiator-name=iqn.2001-04.com.example:my-initiator \
9ae3a8
+qemu-kvm -iscsi initiator-name=iqn.2001-04.com.example:my-initiator \
9ae3a8
                  -cdrom iscsi://192.0.2.1/iqn.2001-04.com.example/2 \
9ae3a8
                  -drive file=iscsi://192.0.2.1/iqn.2001-04.com.example/1
9ae3a8
 @end example
9ae3a8
 
9ae3a8
 Example (CHAP username/password via URL):
9ae3a8
 @example
9ae3a8
-qemu-system-i386 -drive file=iscsi://user%password@@192.0.2.1/iqn.2001-04.com.example/1
9ae3a8
+qemu-kvm -drive file=iscsi://user%password@@192.0.2.1/iqn.2001-04.com.example/1
9ae3a8
 @end example
9ae3a8
 
9ae3a8
 Example (CHAP username/password via environment variables):
9ae3a8
 @example
9ae3a8
 LIBISCSI_CHAP_USERNAME="user" \
9ae3a8
 LIBISCSI_CHAP_PASSWORD="password" \
9ae3a8
-qemu-system-i386 -drive file=iscsi://192.0.2.1/iqn.2001-04.com.example/1
9ae3a8
+qemu-kvm -drive file=iscsi://192.0.2.1/iqn.2001-04.com.example/1
9ae3a8
 @end example
9ae3a8
 
9ae3a8
 iSCSI support is an optional feature of QEMU and only available when
9ae3a8
@@ -2093,12 +2093,12 @@ Syntax for specifying a NBD device using Unix Domain Sockets
9ae3a8
 
9ae3a8
 Example for TCP
9ae3a8
 @example
9ae3a8
-qemu-system-i386 --drive file=nbd:192.0.2.1:30000
9ae3a8
+qemu-kvm --drive file=nbd:192.0.2.1:30000
9ae3a8
 @end example
9ae3a8
 
9ae3a8
 Example for Unix Domain Sockets
9ae3a8
 @example
9ae3a8
-qemu-system-i386 --drive file=nbd:unix:/tmp/nbd-socket
9ae3a8
+qemu-kvm --drive file=nbd:unix:/tmp/nbd-socket
9ae3a8
 @end example
9ae3a8
 
9ae3a8
 @item SSH
9ae3a8
@@ -2106,8 +2106,8 @@ QEMU supports SSH (Secure Shell) access to remote disks.
9ae3a8
 
9ae3a8
 Examples:
9ae3a8
 @example
9ae3a8
-qemu-system-i386 -drive file=ssh://user@@host/path/to/disk.img
9ae3a8
-qemu-system-i386 -drive file.driver=ssh,file.user=user,file.host=host,file.port=22,file.path=/path/to/disk.img
9ae3a8
+qemu-kvm -drive file=ssh://user@@host/path/to/disk.img
9ae3a8
+qemu-kvm -drive file.driver=ssh,file.user=user,file.host=host,file.port=22,file.path=/path/to/disk.img
9ae3a8
 @end example
9ae3a8
 
9ae3a8
 Currently authentication must be done using ssh-agent.  Other
9ae3a8
@@ -2125,7 +2125,7 @@ sheepdog[+tcp|+unix]://[host:port]/vdiname[?socket=path][#snapid|#tag]
9ae3a8
 
9ae3a8
 Example
9ae3a8
 @example
9ae3a8
-qemu-system-i386 --drive file=sheepdog://192.0.2.1:30000/MyVirtualMachine
9ae3a8
+qemu-kvm --drive file=sheepdog://192.0.2.1:30000/MyVirtualMachine
9ae3a8
 @end example
9ae3a8
 
9ae3a8
 See also @url{http://http://www.osrg.net/sheepdog/}.
9ae3a8
@@ -2143,7 +2143,7 @@ gluster[+transport]://[server[:port]]/volname/image[?socket=...]
9ae3a8
 
9ae3a8
 Example
9ae3a8
 @example
9ae3a8
-qemu-system-x86_64 --drive file=gluster://192.0.2.1/testvol/a.img
9ae3a8
+qemu-kvm --drive file=gluster://192.0.2.1/testvol/a.img
9ae3a8
 @end example
9ae3a8
 
9ae3a8
 See also @url{http://www.gluster.org}.
9ae3a8
@@ -2209,7 +2209,7 @@ and communicate.  Requires the Linux @code{vhci} driver installed.  Can
9ae3a8
 be used as following:
9ae3a8
 
9ae3a8
 @example
9ae3a8
-qemu-system-i386 [...OPTIONS...] -bt hci,vlan=5 -bt vhci,vlan=5
9ae3a8
+qemu-kvm [...OPTIONS...] -bt hci,vlan=5 -bt vhci,vlan=5
9ae3a8
 @end example
9ae3a8
 
9ae3a8
 @item -bt device:@var{dev}[,vlan=@var{n}]
9ae3a8
@@ -2255,7 +2255,7 @@ Options to each backend are described below.
9ae3a8
 
9ae3a8
 Use 'help' to print all available TPM backend types.
9ae3a8
 @example
9ae3a8
-qemu -tpmdev help
9ae3a8
+qemu-kvm -tpmdev help
9ae3a8
 @end example
9ae3a8
 
9ae3a8
 @item -tpmdev passthrough, id=@var{id}, path=@var{path}, cancel-path=@var{cancel-path}
9ae3a8
@@ -2579,14 +2579,14 @@ ETEXI
9ae3a8
 
9ae3a8
 DEF("realtime", HAS_ARG, QEMU_OPTION_realtime,
9ae3a8
     "-realtime [mlock=on|off]\n"
9ae3a8
-    "                run qemu with realtime features\n"
9ae3a8
+    "                run qemu-kvm with realtime features\n"
9ae3a8
     "                mlock=on|off controls mlock support (default: on)\n",
9ae3a8
     QEMU_ARCH_ALL)
9ae3a8
 STEXI
9ae3a8
 @item -realtime mlock=on|off
9ae3a8
 @findex -realtime
9ae3a8
-Run qemu with realtime features.
9ae3a8
-mlocking qemu and guest memory can be enabled via @option{mlock=on}
9ae3a8
+Run qemu-kvm with realtime features.
9ae3a8
+mlocking qemu-kvm and guest memory can be enabled via @option{mlock=on}
9ae3a8
 (enabled by default).
9ae3a8
 ETEXI
9ae3a8
 
9ae3a8
@@ -2600,7 +2600,7 @@ connections will likely be TCP-based, but also UDP, pseudo TTY, or even
9ae3a8
 stdio are reasonable use case. The latter is allowing to start QEMU from
9ae3a8
 within gdb and establish the connection via a pipe:
9ae3a8
 @example
9ae3a8
-(gdb) target remote | exec qemu-system-i386 -gdb stdio ...
9ae3a8
+(gdb) target remote | exec qemu-kvm -gdb stdio ...
9ae3a8
 @end example
9ae3a8
 ETEXI
9ae3a8
 
9ae3a8
-- 
9ae3a8
1.8.3.1
9ae3a8