From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:50434) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SSx3y-0005mh-6x for qemu-devel@nongnu.org; Fri, 11 May 2012 17:07:49 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SSx3v-0003B2-EH for qemu-devel@nongnu.org; Fri, 11 May 2012 17:07:45 -0400 Received: from v220110690675601.yourvserver.net ([78.47.199.172]:45067) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SSx3v-0003Ag-34 for qemu-devel@nongnu.org; Fri, 11 May 2012 17:07:43 -0400 From: Stefan Weil Date: Fri, 11 May 2012 23:07:36 +0200 Message-Id: <1336770456-6260-5-git-send-email-sw@weilnetz.de> In-Reply-To: <1336770456-6260-1-git-send-email-sw@weilnetz.de> References: <1336770456-6260-1-git-send-email-sw@weilnetz.de> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: [Qemu-devel] =?utf-8?q?=5BPATCH_4/4=5D_qemu-doc=3A_Use_QEMU_inste?= =?utf-8?q?ad_of_qemu_for_product_name?= List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: Blue Swirl , Stefan Weil , Anthony Liguori , =?UTF-8?q?Andreas=20F=C3=A4rber?= When 'qemu' was used as a product name or as a generic process name, it is now replaced by the official upper case 'QEMU'. Signed-off-by: Stefan Weil --- qemu-doc.texi | 10 +++++----- qemu-options.hx | 30 +++++++++++++++--------------- 2 files changed, 20 insertions(+), 20 deletions(-) diff --git a/qemu-doc.texi b/qemu-doc.texi index 6feac2c..1148525 100644 --- a/qemu-doc.texi +++ b/qemu-doc.texi @@ -227,7 +227,7 @@ QEMU uses GUS emulation (GUSEMU32 @url{http://www.dei= nmeister.de/gusemu/}) by Tibor "TS" Sch=C3=BCtz. =20 Note that, by default, GUS shares IRQ(7) with parallel ports and so -qemu must be told to not have parallel ports to have working GUS +QEMU must be told to not have parallel ports to have working GUS =20 @example qemu-system-i386 dos.img -soundhw gus -parallel none @@ -986,7 +986,7 @@ or the @code{usb_add} monitor command. Available dev= ices are: Virtual Mouse. This will override the PS/2 mouse emulation when activat= ed. @item tablet Pointer device that uses absolute coordinates (like a touchscreen). -This means qemu is able to report the mouse position without having +This means QEMU is able to report the mouse position without having to grab the mouse. Also overrides the PS/2 mouse emulation when activat= ed. @item disk:@var{file} Mass storage device based on @var{file} (@pxref{disk_images}) @@ -1377,7 +1377,7 @@ use TLS and x509 certificates to protect security c= redentials from snooping. QEMU has a primitive support to work with gdb, so that you can do 'Ctrl-C' while the virtual machine is running and inspect its state. =20 -In order to use gdb, launch qemu with the '-s' option. It will wait for = a +In order to use gdb, launch QEMU with the '-s' option. It will wait for = a gdb connection: @example qemu-system-i386 -s -kernel arch/i386/boot/bzImage -hda root-2.4.20.img = \ @@ -2313,8 +2313,8 @@ qemu-i386 -L / /bin/ls @code{-L /} tells that the x86 dynamic linker must be searched with a @file{/} prefix. =20 -@item Since QEMU is also a linux process, you can launch qemu with -qemu (NOTE: you can only do that if you compiled QEMU from the sources): +@item Since QEMU is also a linux process, you can launch QEMU with +QEMU (NOTE: you can only do that if you compiled QEMU from the sources): =20 @example qemu-i386 -L / qemu-i386 -L / /bin/ls diff --git a/qemu-options.hx b/qemu-options.hx index 17e9963..52a956a 100644 --- a/qemu-options.hx +++ b/qemu-options.hx @@ -221,7 +221,7 @@ qcow2. If performance is more important than correct= ness, @option{cache=3Dwriteback} should be used with qcow2. =20 In case you don't care about data integrity over host failures, use -cache=3Dunsafe. This option tells qemu that it never needs to write any = data +cache=3Dunsafe. This option tells QEMU that it never needs to write any = data to the disk but can instead keeps things in cache. If anything goes wron= g, like your host losing power, the disk storage getting disconnected accid= entally, etc. you're image will most probably be rendered unusable. When using @@ -515,7 +515,7 @@ Virtual Mouse. This will override the PS/2 mouse emul= ation when activated. =20 @item tablet Pointer device that uses absolute coordinates (like a touchscreen). This -means qemu is able to report the mouse position without having to grab t= he +means QEMU is able to report the mouse position without having to grab t= he mouse. Also overrides the PS/2 mouse emulation when activated. =20 @item disk:[format=3D@var{format}]:@var{file} @@ -587,7 +587,7 @@ this path will be available to the 9p client on the g= uest. Specifies the security model to be used for this export path. Supported security models are "passthrough", "mapped-xattr", "mapped-fil= e" and "none". In "passthrough" security model, files are stored using the same -credentials as they are created on the guest. This requires qemu +credentials as they are created on the guest. This requires QEMU to run as root. In "mapped-xattr" security model, some of the file attributes like uid, gid, mode bits and link target are stored as file attributes. For "mapped-file" these attributes are stored in the @@ -654,7 +654,7 @@ this path will be available to the 9p client on the g= uest. Specifies the security model to be used for this export path. Supported security models are "passthrough", "mapped-xattr", "mapped-fil= e" and "none". In "passthrough" security model, files are stored using the same -credentials as they are created on the guest. This requires qemu +credentials as they are created on the guest. This requires QEMU to run as root. In "mapped-xattr" security model, some of the file attributes like uid, gid, mode bits and link target are stored as file attributes. For "mapped-file" these attributes are stored in the @@ -1117,7 +1117,7 @@ disables exclusive client access. Useful for share= d desktop sessions, where you don't want someone forgetting specify -shared disconnect everybody else. 'ignore' completely ignores the shared flag and allows everybody connect unconditionally. Doesn't conform to the rfb -spec but is traditional qemu behavior. +spec but is traditional QEMU behavior. =20 @end table ETEXI @@ -1800,7 +1800,7 @@ not take any options. @option{pty} is not available on Windows hosts. =20 @item -chardev stdio ,id=3D@var{id} [,signal=3Don|off] -Connect to standard input and standard output of the qemu process. +Connect to standard input and standard output of the QEMU process. =20 @option{signal} controls if signals are enabled on the terminal, that in= cludes exiting QEMU with the key sequence @key{Control-c}. This option is enabl= ed by @@ -2128,19 +2128,19 @@ they default to @code{0.0.0.0}. When not using a specified @var{src_port} a random port is automatically= chosen. =20 If you just want a simple readonly console you can use @code{netcat} or -@code{nc}, by starting qemu with: @code{-serial udp::4555} and nc as: -@code{nc -u -l -p 4555}. Any time qemu writes something to that port it +@code{nc}, by starting QEMU with: @code{-serial udp::4555} and nc as: +@code{nc -u -l -p 4555}. Any time QEMU writes something to that port it will appear in the netconsole session. =20 If you plan to send characters back via netconsole or you want to stop -and start qemu a lot of times, you should have qemu use the same +and start QEMU a lot of times, you should have QEMU use the same source port each time by using something like @code{-serial -udp::4555@@:4556} to qemu. Another approach is to use a patched +udp::4555@@:4556} to QEMU. Another approach is to use a patched version of netcat which can listen to a TCP port and send and receive characters via udp. If you have a patched version of netcat which activates telnet remote echo and single char transfer, then you can use the following options to step up a netcat redirector to allow -telnet on port 5555 to access the qemu port. +telnet on port 5555 to access the QEMU port. @table @code @item QEMU Options: -serial udp::4555@@:4556 @@ -2295,7 +2295,7 @@ STEXI @findex -gdb Wait for gdb connection on device @var{dev} (@pxref{gdb_usage}). Typical connections will likely be TCP-based, but also UDP, pseudo TTY, or even -stdio are reasonable use case. The latter is allowing to start qemu from +stdio are reasonable use case. The latter is allowing to start QEMU from within gdb and establish the connection via a pipe: @example (gdb) target remote | exec qemu-system-i386 -gdb stdio ... @@ -2333,7 +2333,7 @@ ETEXI DEF("hdachs", HAS_ARG, QEMU_OPTION_hdachs, \ "-hdachs c,h,s[,t]\n" \ " force hard disk 0 physical geometry and the optiona= l BIOS\n" \ - " translation (t=3Dnone or lba) (usually qemu can gue= ss them)\n", + " translation (t=3Dnone or lba) (usually QEMU can gue= ss them)\n", QEMU_ARCH_ALL) STEXI @item -hdachs @var{c},@var{h},@var{s},[,@var{t}] @@ -2379,7 +2379,7 @@ DEF("xen-create", 0, QEMU_OPTION_xen_create, QEMU_ARCH_ALL) DEF("xen-attach", 0, QEMU_OPTION_xen_attach, "-xen-attach attach to existing xen domain\n" - " xend will use this when starting qemu\n", + " xend will use this when starting QEMU\n", QEMU_ARCH_ALL) STEXI @item -xen-domid @var{id} @@ -2392,7 +2392,7 @@ Warning: should not be used when xend is in use (XE= N only). @item -xen-attach @findex -xen-attach Attach to existing xen domain. -xend will use this when starting qemu (XEN only). +xend will use this when starting QEMU (XEN only). ETEXI =20 DEF("no-reboot", 0, QEMU_OPTION_no_reboot, \ --=20 1.7.9