source: postlfs/virtualization/qemu.xml@ a12730f

12.0 12.1 kea ken/TL2024 ken/tuningfonts lazarus lxqt plabs/newcss python3.11 qt5new rahul/power-profiles-daemon renodr/vulkan-addition trunk xry111/llvm18 xry111/xf86-video-removal
Last change on this file since a12730f was a12730f, checked in by Bruce Dubbs <bdubbs@…>, 15 months ago

Remove sdl dependeny from pages that also have sdl2 as a dependency

  • Property mode set to 100644
File size: 27.7 KB
Line 
1<?xml version="1.0" encoding="ISO-8859-1"?>
2<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
3 "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
4 <!ENTITY % general-entities SYSTEM "../../general.ent">
5 %general-entities;
6
7 <!ENTITY qemu-download-http "https://download.qemu.org/qemu-&qemu-version;.tar.xz">
8 <!ENTITY qemu-download-ftp " ">
9 <!ENTITY qemu-md5sum "7630d6a9eba7ab2bcb9979d6d24c2697">
10 <!ENTITY qemu-size "117 MB">
11 <!ENTITY qemu-buildsize "2.1 GB">
12 <!ENTITY qemu-time "1.3 SBU (add 2.0 SBU for tests, both using parallelism=4)">
13]>
14
15<sect1 id="qemu" xreflabel="qemu-&qemu-version;">
16 <?dbhtml filename="qemu.html"?>
17
18
19 <title>qemu-&qemu-version;</title>
20
21 <indexterm zone="qemu">
22 <primary sortas="a-qemu">qemu</primary>
23 </indexterm>
24
25 <sect2 role="package">
26 <title>Introduction to qemu</title>
27
28 <para>
29 <application>qemu</application> is a full virtualization solution for
30 Linux on x86 hardware containing virtualization extensions (Intel VT or
31 AMD-V).
32 </para>
33
34 &lfs113_checked;
35
36 <bridgehead renderas="sect3">Package Information</bridgehead>
37 <itemizedlist spacing="compact">
38 <listitem>
39 <para>
40 Download (HTTP): <ulink url="&qemu-download-http;"/>
41 </para>
42 </listitem>
43 <listitem>
44 <para>
45 Download (FTP): <ulink url="&qemu-download-ftp;"/>
46 </para>
47 </listitem>
48 <listitem>
49 <para>
50 Download MD5 sum: &qemu-md5sum;
51 </para>
52 </listitem>
53 <listitem>
54 <para>
55 Download size: &qemu-size;
56 </para>
57 </listitem>
58 <listitem>
59 <para>
60 Estimated disk space required: &qemu-buildsize;
61 </para>
62 </listitem>
63 <listitem>
64 <para>
65 Estimated build time: &qemu-time;
66 </para>
67 </listitem>
68 </itemizedlist>
69
70 <bridgehead renderas="sect3">Qemu Dependencies</bridgehead>
71
72 <bridgehead renderas="sect4">Required</bridgehead>
73 <para role="required">
74 <xref linkend="glib2"/>, and
75 <xref linkend="x-window-system"/>
76 </para>
77
78 <bridgehead renderas="sect4">Recommended</bridgehead>
79 <para role="recommended">
80 <xref linkend="alsa-lib"/>,
81 <xref linkend="libslirp"/>, and
82 <xref linkend="sdl2"/>
83 </para>
84
85 <bridgehead renderas="sect4">Optional</bridgehead>
86 <para role="optional">
87 Depending on the sound system, various packages in <xref linkend="alsa"/>,
88 <xref linkend="python3"/>,
89 <xref linkend="pulseaudio"/>,
90 <xref linkend="bluez"/>,
91 <xref linkend="curl"/>,
92 <xref linkend="cyrus-sasl"/>,
93 <xref linkend="gnutls"/>,
94 <xref linkend="gtk2"/>,
95 <xref linkend="gtk3"/>,
96 <xref linkend="libusb"/>,
97 <xref linkend="libgcrypt"/>,
98 <xref linkend="libssh2"/>,
99 <xref linkend="lzo"/>,
100 <xref linkend="nettle"/>,
101 <xref linkend="mesa"/>,
102 <xref role="nodep" linkend="vte"/> or <xref linkend="vte2"/>, and
103<!-- libcacard has been a standalone project since qemu-2.5.-->
104 <ulink url="https://gitlab.freedesktop.org/spice/libcacard">libcacard</ulink>
105 </para>
106
107 <bridgehead renderas="sect4">Optional (for building the documentation)</bridgehead>
108 <para role="optional">
109 <xref linkend="sphinx_rtd_theme"/>
110 </para>
111
112 <note>
113 <para>
114 This optional dependencies list is not comprehensive. See the output of
115 <command>./configure --help</command> for a more complete list.
116 </para>
117 </note>
118
119 <para condition="html" role="usernotes">User Notes:
120 <ulink url="&blfs-wiki;/qemu"/></para>
121
122 </sect2>
123
124 <sect2 id='qemu-prereq'>
125 <title>KVM Prerequisites</title>
126
127 <para>
128 Before building <application>qemu</application>, check to see if
129 your processor supports Virtualization Technology (VT):
130 </para>
131
132 <screen><userinput>grep -E '^flags.*(vmx|svm)' /proc/cpuinfo</userinput></screen>
133
134 <para>
135 If you get any output, you have VT technology (vmx for Intel
136 processors and svm for AMD processors). You then need to go into your
137 system BIOS and ensure it is enabled. After enabling, reboot back to your
138 LFS instance.
139 </para>
140
141 </sect2>
142
143 <sect2 role="kernel" id='qemu-kernel'>
144 <title>Kernel Configuration</title>
145
146 <para>
147 Enable the following options in the kernel configuration and
148 recompile the kernel if necessary:
149 </para>
150
151<screen><literal>[*] Virtualization: ---&gt; [CONFIG_VIRTUALIZATION]
152 &lt;*/M&gt; Kernel-based Virtual Machine (KVM) support [CONFIG_KVM]
153 &lt;*/M&gt; KVM for Intel (and compatible) processors support [CONFIG_KVM_INTEL]
154 &lt;*/M&gt; KVM for AMD processors support [CONFIG_KVM_AMD]</literal></screen>
155
156 <indexterm zone="qemu qemu-kernel">
157 <primary sortas="d-qemu">qemu</primary>
158 </indexterm>
159
160 <para>
161 The Intel or AMD settings are not both required, but the one matching
162 your system processor is required.
163 </para>
164
165 <para>
166 To use the <quote>bridge</quote> network device, as explained below,
167 check that <xref linkend='bridgeutils'/> is installed
168 and the following options in the kernel configuration are enabled:
169 </para>
170
171<screen><literal>[*] Networking support ---&gt; [CONFIG_NET]
172 Networking options ---&gt;
173 &lt;*/M&gt; 802.1d Ethernet Bridging [CONFIG_BRIDGE]
174Device Drivers ---&gt;
175 [*] Network device support ---&gt; [CONFIG_NETDEVICES]
176 &lt;*/M&gt; Universal TUN/TAP device driver support [CONFIG_TUN]</literal></screen>
177
178 </sect2>
179
180 <sect2 role="installation">
181 <title>Installation of qemu</title>
182<!-- group kvm is created in lfs chapter 7 even for sysv
183 <para revision="sysv">
184 You will need a dedicated group that will contain users (other than root)
185 allowed to access the KVM device. Create this group by running the
186 following command as the
187 <systemitem class="username">root</systemitem> user:
188 </para>
189
190<screen role="root" revision="sysv"><userinput>groupadd -g 61 kvm</userinput></screen>
191-->
192 <para>
193 As the &root; user, add any users that might use the KVM device to that
194 group:
195 </para>
196
197<screen role="root"><userinput>usermod -a -G kvm <replaceable>&lt;username&gt;</replaceable></userinput></screen>
198
199 <para>
200 Install <application>qemu</application> by running the following
201 commands:
202 </para>
203
204 <note>
205 <para>
206 Qemu is capable of running many targets. The build process
207 is also capable of building multiple targets at one time in a
208 comma delimited list assigned to <option>--target-list</option>. Run
209 <command>./configure --help</command> to get a complete list of
210 available targets.
211 </para>
212 </note>
213
214
215<screen><userinput>if [ $(uname -m) = i686 ]; then
216 QEMU_ARCH=i386-softmmu
217else
218 QEMU_ARCH=x86_64-softmmu
219fi
220
221
222mkdir -vp build &amp;&amp;
223cd build &amp;&amp;
224
225../configure --prefix=/usr \
226 --sysconfdir=/etc \
227 --localstatedir=/var \
228 --target-list=$QEMU_ARCH \
229 --audio-drv-list=alsa \
230 --disable-pa \
231 --docdir=/usr/share/doc/qemu-&qemu-version; &amp;&amp;
232
233unset QEMU_ARCH &amp;&amp;
234
235make</userinput></screen>
236
237 <para>
238 <application>qemu</application> uses <command>ninja</command> as
239 a subprocess when building. To run the tests, issue:
240 <command>ninja test</command>.
241 </para>
242
243 <para>
244 Now, as the <systemitem class="username">root</systemitem> user:
245 </para>
246
247<screen role="root"><userinput>make install</userinput></screen>
248
249 <para>
250 You will also need to add an Udev rule so that the KVM device gets correct
251 permissions. As the &root; user, issue:
252 </para>
253
254<screen role="root"><userinput>cat > /lib/udev/rules.d/65-kvm.rules &lt;&lt; "EOF"
255<literal>KERNEL=="kvm", GROUP="kvm", MODE="0660"</literal>
256EOF</userinput></screen>
257
258 <para>
259 Change the permissions and ownership of a helper script, which is needed
260 when using the <quote>bridge</quote> network device (see below). Again
261 as the &root; user, issue:
262 </para>
263
264<screen role="root"><userinput>chgrp kvm /usr/libexec/qemu-bridge-helper &amp;&amp;
265chmod 4750 /usr/libexec/qemu-bridge-helper</userinput></screen>
266
267 <note>
268 <para>
269 For convenience you may want to create a symbolic link to run
270 the installed program. For instance (as the &root; user):
271 </para>
272
273<screen role="root"><userinput>ln -sv qemu-system-`uname -m` /usr/bin/qemu</userinput></screen>
274 </note>
275
276 </sect2>
277
278 <sect2 role="commands">
279 <title>Command Explanations</title>
280
281 <para>
282 <parameter>--audio-drv-list=alsa --disable-pa</parameter>: This switch
283 sets the audio driver to ALSA. See below for enabling other audio drivers.
284 </para>
285
286 <para>
287 <option>--audio-drv-list=pa --disable-alsa</option>: This switch sets
288 the audio driver to pulseaudio. For other drivers see the
289 --audio-drv-list choices in the output of
290 <command>./configure --help</command>. The default audio driver is OSS.
291 To enable support for both alsa and pulseaudio, use
292 <option>--audio-drv-list=alsa,pa</option>.
293 </para>
294
295 </sect2>
296
297 <sect2 role="using">
298 <title>Using Qemu</title>
299
300 <para>
301 Since using qemu means using a virtual computer, the steps to set up
302 the virtual machine are in close analogy with those to set up a real
303 computer. You'll need to decide about CPU, memory, disk, USB devices,
304 network card(s), screen size, etc. Once the <quote>hardware</quote> is
305 decided, you'll have for example to choose how to connect the machine
306 to internet, and/or to install an OS. In the following, we show basic
307 ways of performing those steps. But qemu is much more than this, and it
308 is strongly advised to read the qemu documentation in
309 <filename>/usr/share/doc/qemu-&qemu-version;/qemu-doc.html</filename>.
310 </para>
311
312 <note>
313 <para>
314 It is standard practice to name the computer running qemu
315 <quote>host</quote> and the emulated machine running under qemu the
316 <quote>guest</quote>. We'll use those notations in the following.
317 </para>
318 </note>
319
320 <note>
321 <para>
322 The following instructions assume the optional symbolic link,
323 <filename>qemu</filename>, has been created. Additionally,
324 <command>qemu</command> should be run in a graphical environment.
325 But it is possible to use qemu <quote>headless</quote> or through
326 SSH. See the documentation for the various possibilities.
327 </para>
328 </note>
329
330 <bridgehead renderas="sect3">Disk</bridgehead>
331 <para>
332 A virtual disk may be set up in the following way:
333 </para>
334
335<screen><userinput>VDISK_SIZE=<replaceable>50G</replaceable>
336VDISK_FILENAME=<replaceable>vdisk.img</replaceable>
337qemu-img create -f qcow2 $VDISK_FILENAME $VDISK_SIZE</userinput></screen>
338
339 <para>
340 The virtual disk size and filename should be adjusted as desired. The
341 actual size of the file will be less than specified, but will expand as
342 needed, so it is safe to put a high value.
343 </para>
344
345 <bridgehead renderas="sect3">Operating System</bridgehead>
346 <para>
347 To install an operating system, download an iso image from your preferred
348 Linux distribution. For the purposes of this example, we'll use
349 <filename>Fedora-16-x86_64-Live-LXDE.iso</filename> in the current
350 directory. Run the following:
351 </para>
352
353<screen><userinput>qemu -enable-kvm \
354 -drive file=$VDISK_FILENAME \
355 -cdrom Fedora-16-x86_64-Live-LXDE.iso \
356 -boot d \
357 -m <replaceable>1G</replaceable></userinput></screen>
358
359 <para>
360 Follow the normal installation procedures for the chosen distribution.
361 The <parameter>-boot</parameter> option specifies the boot order of
362 drives as a string of drive letters. Valid drive letters are: a, b
363 (floppy 1 and 2), c (first hard disk), d (first CD-ROM). The
364 <parameter>-m</parameter> option is the amount of memory to use for the
365 virtual machine. The choice depends on the load of the host. Modern
366 distributions should be comfortable with 1GB.
367 The <parameter>-enable-kvm</parameter> option allows hardware
368 acceleration. Without this switch, the emulation is much slower.
369 </para>
370
371 <bridgehead renderas="sect3">Defining the virtual hardware</bridgehead>
372 <para>
373 The virtual machine hardware is defined by the qemu command line.
374 An example command is given below:
375 </para>
376
377<screen><userinput>qemu -enable-kvm \
378 -smp 4 \
379 -cpu host \
380 -m 1G \
381 -drive file=$VDISK_FILENAME \
382 -cdrom grub-img.iso \
383 -boot order=c,once=d,menu=on \
384 -net nic,netdev=net0 \
385 -netdev user,id=net0 \
386 -device ac97 \
387 -vga std \
388 -serial mon:stdio \
389 -name "fedora-16"</userinput></screen>
390
391 <bridgehead renderas="sect3">Meaning of the command line options</bridgehead>
392 <para>
393 <parameter>-enable-kvm</parameter>: enable full KVM virtualization
394 support. On some hardware, it may be necessary to add the undocumented
395 <option>-machine smm=off</option> option in order to enable KVM.
396 </para>
397
398 <para>
399 <parameter>-smp &lt;N&gt;</parameter>: enable symmetric multiprocessing
400 with &lt;N&gt; CPUs.
401 </para>
402
403 <para>
404 <parameter>-cpu &lt;model&gt;</parameter>: simulate CPU &lt;model&gt;.
405 the list of supported models can be obtained with <option>-cpu
406 help</option>.
407 </para>
408
409 <para>
410 <parameter>-drive file=&lt;filename&gt;</parameter>: defines a virtual
411 disk whose image is stored in <filename>&lt;filename&gt;</filename>.
412 </para>
413
414 <para>
415 <parameter>-cdrom grub-img.iso</parameter>: defines an iso formatted file
416 to use as a cdrom. Here we use a grub rescue disk, which may turn handy
417 when something goes wrong at boot time.
418 </para>
419
420 <para>
421 <parameter>-boot order=c,once=d,menu=on</parameter>: defines the boot
422 order for the virtual BIOS.
423 </para>
424
425 <para>
426 <parameter>-net nic,netdev=&lt;netid&gt;</parameter>: defines a network
427 card connected to the network device with id &lt;netid&gt;.
428 </para>
429
430 <para>
431 <parameter>-netdev user,id=&lt;netid&gt;</parameter>: defines the
432 network <quote>user</quote> device. This is a virtual local network
433 with addresses 10.0.2.0/24, where the host has address 10.0.2.2 and
434 acts as a gateway to internet, and with a name server at address
435 10.0.2.3, and an smb server at address 10.0.2.4. A builtin DHCP server
436 can allocate addresses between 10.0.2.15 and 10.0.2.31.
437 </para>
438
439 <para>
440 <parameter>-soundhw &lt;model&gt;</parameter>: defines the soundcard
441 model. The list may be obtained with <option>-soundhw help</option>.
442 </para>
443
444 <para>
445 <parameter>-vga &lt;type&gt;</parameter>: defines the type of VGA card
446 to emulate. For <parameter>-vga std</parameter>, if you are building
447 a Linux kernel for the guest, it's recommended to enable
448 <option>CONFIG_DRM_BOCHS</option> (as a part of the kernel or a kernel
449 module) to drive all the features of the emulated VGA card, and
450 <option>CONFIG_FB</option> to display the Linux console on it. The
451 other <option>&lt;type&gt;</option> values are not tested by the
452 editors and may require additional dependencies.
453 </para>
454
455 <para>
456 <parameter>-serial mon:stdio</parameter>: sends the serial port of the
457 guest (<filename>/dev/ttyS0</filename> on linux guests), multiplexed with
458 the qemu monitor, to the standard input and output of the qemu
459 process.
460 </para>
461
462 <para>
463 <parameter>-name &lt;name&gt;</parameter>: sets the name of the guest.
464 This name is displayed in the guest window caption. It may be useful
465 if you run several guests at the same time.
466 </para>
467
468 <para>
469 <option>-pflash /usr/share/qemu/edk2-x86_64-code.fd</option>: Load a
470 pre-built EDK2 UEFI firmware, instead of the default PC BIOS. Use
471 this option if you want to boot the guest OS with UEFI.
472 </para>
473
474 <para>
475 <option>-drive file=&lt;filename&gt;,if=virtio</option>: Provide
476 Virtio interface to the guest kernel for accessing the disk image,
477 instead of simulating a real disk hardware. This can improve disk I/O
478 performance, but it requires a Virtio driver in guest kernel. Use
479 it instead of a plain <option>-drive</option> if the guest kernel
480 supports Virtio. To build a Linux kernel with Virtio support for the
481 guest, use
482 <command>make defconfig &amp;&amp; make kvm_guest.config</command> to
483 create an initial kernel configuration with the Virtio drives enabled,
484 then make your customization. And, if the guest kernel is Linux, the
485 virtual disks using Virtio interface will be named
486 <filename>vdx</filename> in the devtmpfs, instead of
487 <filename>sdx</filename>.
488 </para>
489
490 <para>
491 <option>-net nic,netdev=net0,model=virtio-net-pci</option>: Provide
492 Virtio interface to the guest kernel for accessing the network
493 interface, instead of simulating a real network interface card. This
494 can improve network I/O performance, but it requires a Virtio driver
495 in guest kernel. Use it instead of a plain <option>-net</option> if
496 the guest kernel supports Virtio.
497 </para>
498
499 <bridgehead renderas="sect3">Controlling the Emulated Display</bridgehead>
500 <para>
501 It may happen that the guest window displayed by qemu does not correspond
502 to the full capability of the emulated VGA card. For example, the vmware
503 card is 1600x900 capable, but only 1024x768 is displayed by default.
504 A suitable Xorg configuration on the guest allows to use the full size
505 (Note that the Xorg video driver to use is <xref
506 linkend="xorg-vmware-driver"/>):
507 </para>
508
509<screen role="root"><userinput>cat &gt; /usr/share/X11/xorg.conf.d/20-vmware.conf &lt;&lt; "EOF"
510<literal>Section "Monitor"
511 Identifier "Monitor0"
512 # cvt 1600 900
513 # 1600x900 59.95 Hz (CVT 1.44M9) hsync: 55.99 kHz; pclk: 118.25 MHz
514 Modeline "1600x900" 118.25 1600 1696 1856 2112 900 903 908 934 -hsync +vsync
515 Option "PreferredMode" "1600x900"
516 HorizSync 1-200
517 VertRefresh 1-200
518EndSection
519
520Section "Device"
521 Identifier "VMware SVGA II Adapter"
522 Option "Monitor" "default"
523 Driver "vmware"
524EndSection
525
526Section "Screen"
527 Identifier "Default Screen"
528 Device "VMware SVGA II Adapter"
529 Monitor "Monitor0"
530
531 SubSection "Display"
532 Depth 24
533 Modes "1600x900" "1440x900" "1366x768" "1280x720" "800x480"
534 EndSubSection
535
536EndSection</literal>
537EOF</userinput></screen>
538
539 <para>
540 New sizes will be available besides the native ones. You need to
541 restart X in order to have the new sizes available.
542 </para>
543
544 <bridgehead renderas="sect3">Networking</bridgehead>
545 <para>
546 The above solution for networking allows the guest to access the local
547 network through the host (and possibly to access internet through the
548 local routers), but the converse is not true. Not even the host can
549 access the guest, unless port forwarding is enabled. And in the case
550 several guests are running, they cannot communicate with each other.
551 Other network devices can be used for this purpose. For example, there
552 is the <quote>socket</quote> device, which allows several guests to
553 share a common virtual network. In the following, we describe in more
554 details how to set up the <quote>bridge</quote> device, which allows
555 the guests to appear as if connected to the local network. All the
556 commands below should be run as the <systemitem
557 class="username">root</systemitem> user.
558 </para>
559
560 <para revision="sysv">
561 Set up bridging with <xref linkend="bridgeutils"/>. Only the physical
562 interface(s) should be set up at boot. The virtual interface(s) will be
563 added as needed when qemu is started.
564 </para>
565
566 <para revision="systemd">
567 <!-- On SYS-V, IP_FORWARD is enabled by the bridge script. -->
568 Allow the host to forward IP packets:
569 </para>
570
571<screen role="root"
572 revision="systemd"><userinput>sysctl -w net.ipv4.ip_forward=1</userinput></screen>
573
574 <para revision="systemd">
575 To make this permanent, add the command to
576 <filename>/etc/sysctl.d/60-net-forward.conf:</filename>
577 </para>
578
579<screen role="root"
580 revision="systemd"><userinput>cat &gt;&gt; /etc/sysctl.d/60-net-forward.conf &lt;&lt; EOF
581<literal>net.ipv4.ip_forward=1</literal>
582EOF</userinput></screen>
583
584 <para>
585 Set up a required configuration file:
586 </para>
587
588<!-- /etc/qemu has not been installed by "make install" since version 2.4 -->
589<screen role="root"><userinput>install -vdm 755 /etc/qemu &amp;&amp;
590echo allow br0 &gt; /etc/qemu/bridge.conf</userinput></screen>
591
592 <para>
593 In the qemu command line above, replace the switch
594 <parameter>-netdev user,...</parameter> with
595 <parameter>-netdev bridge,...</parameter>.
596 </para>
597
598 </sect2>
599
600 <sect2 role="content">
601 <title>Contents</title>
602
603 <segmentedlist>
604 <segtitle>Installed Programs</segtitle>
605 <segtitle>Installed Library</segtitle>
606 <segtitle>Installed Directories</segtitle>
607
608 <seglistitem>
609 <seg>
610 elf2dmp,
611 qemu (symlink),
612 qemu-edid,
613 qemu-ga,
614 qemu-img,
615 qemu-io,
616 qemu-keymap,
617 qemu-nbd,
618 qemu-pr-helper,
619 qemu-storage-daemon, and
620 qemu-system-&lt;arch&gt;
621 </seg>
622 <seg>None</seg>
623 <seg>
624 /usr/share/qemu and
625 /usr/share/doc/qemu-&qemu-version; (optional)
626 </seg>
627 </seglistitem>
628 </segmentedlist>
629
630 <variablelist>
631 <bridgehead renderas="sect3">Short Description</bridgehead>
632 <?dbfo list-presentation="list"?>
633 <?dbhtml list-presentation="table"?>
634
635 <varlistentry id="elf2dmp">
636 <term><command>elf2dmp</command></term>
637 <listitem>
638 <para>
639 Converts files from elf to dmp format
640 </para>
641 <indexterm zone="qemu elf2dmp">
642 <primary sortas="b-elf2dmp">elf2dmp</primary>
643 </indexterm>
644 </listitem>
645 </varlistentry>
646<!--
647 <varlistentry id="ivshmem-client">
648 <term><command>ivshmem-client</command></term>
649 <listitem>
650 <para>
651 is a standalone client for using the ivshmem device
652 </para>
653 <indexterm zone="qemu ivshmem-client">
654 <primary sortas="b-ivshmem-client">ivshmem-client</primary>
655 </indexterm>
656 </listitem>
657 </varlistentry>
658
659 <varlistentry id="ivshmem-server">
660 <term><command>ivshmem-server</command></term>
661 <listitem>
662 <para>
663 is an example server for the ivshmem device
664 </para>
665 <indexterm zone="qemu ivshmem-server">
666 <primary sortas="b-ivshmem-server">ivshmem-server</primary>
667 </indexterm>
668 </listitem>
669 </varlistentry>
670-->
671 <varlistentry id="qemu-edid">
672 <term><command>qemu-edid</command></term>
673 <listitem>
674 <para>
675 is a test tool for the qemu EDID generator
676 </para>
677 <indexterm zone="qemu qemu-edid">
678 <primary sortas="b-qemu-edid">qemu-edid</primary>
679 </indexterm>
680 </listitem>
681 </varlistentry>
682
683 <varlistentry id="qemu-ga">
684 <term><command>qemu-ga</command></term>
685 <listitem>
686 <para>
687 implements support for QMP (QEMU Monitor Protocol) commands and
688 events that terminate and originate respectively within the guest
689 using an agent built as part of QEMU
690 </para>
691 <indexterm zone="qemu qemu-ga">
692 <primary sortas="b-qemu-ga">qemu-ga</primary>
693 </indexterm>
694 </listitem>
695 </varlistentry>
696
697 <varlistentry id="qemu-img">
698 <term><command>qemu-img</command></term>
699 <listitem>
700 <para>
701 provides commands to manage QEMU disk images
702 </para>
703 <indexterm zone="qemu qemu-img">
704 <primary sortas="b-qemu-img">qemu-img</primary>
705 </indexterm>
706 </listitem>
707 </varlistentry>
708
709 <varlistentry id="qemu-io">
710 <term><command>qemu-io</command></term>
711 <listitem>
712 <para>
713 is a diagnostic and manipulation program for (virtual) memory
714 media. It is still at an early stage of development
715 </para>
716 <indexterm zone="qemu qemu-io">
717 <primary sortas="b-qemu-io">qemu-io</primary>
718 </indexterm>
719 </listitem>
720 </varlistentry>
721
722 <varlistentry id="qemu-keymap">
723 <term><command>qemu-keymap</command></term>
724 <listitem>
725 <para>
726 generates qemu reverse keymaps from xkb keymaps,
727 which can be used with the qemu "-k" command line switch
728 </para>
729 <indexterm zone="qemu qemu-keymap">
730 <primary sortas="b-qemu-keymap">qemu-keymap</primary>
731 </indexterm>
732 </listitem>
733 </varlistentry>
734
735
736 <varlistentry id="qemu-nbd">
737 <term><command>qemu-nbd</command></term>
738 <listitem>
739 <para>
740 exports Qemu disk images using the QEMU Disk Network Block
741 Device (NBD) protocol
742 </para>
743 <indexterm zone="qemu qemu-nbd">
744 <primary sortas="b-qemu-nbd">qemu-nbd</primary>
745 </indexterm>
746 </listitem>
747 </varlistentry>
748
749 <varlistentry id="qemu-pr-helper">
750 <term><command>qemu-pr-helper</command></term>
751 <listitem>
752 <para>
753 Implements the persistent reservation helper for QEMU
754 </para>
755 <indexterm zone="qemu qemu-pr-helper">
756 <primary sortas="b-qemu-pr-helper">qemu-pr-helper</primary>
757 </indexterm>
758 </listitem>
759 </varlistentry>
760
761 <varlistentry id="qemu-storage-daemon">
762 <term><command>qemu-storage-daemon</command></term>
763 <listitem>
764 <para>
765 allows to modify disk images using the QEMU Monitor Protocol (QMP)
766 without running a VM
767 </para>
768 <indexterm zone="qemu qemu-storage-daemon">
769 <primary sortas="b-qemu-storage-daemon">qemu-storage-daemon</primary>
770 </indexterm>
771 </listitem>
772 </varlistentry>
773
774 <varlistentry id="qemu-system">
775 <term><command>qemu-system-x86_64</command></term>
776 <listitem>
777 <para>
778 is the QEMU PC System emulator
779 </para>
780 <indexterm zone="qemu qemu-system">
781 <primary sortas="b-qemu-system">qemu-system-x86_64</primary>
782 </indexterm>
783 </listitem>
784 </varlistentry>
785<!--
786 <varlistentry id="virtfs-proxy-helper">
787 <term><command>virtfs-proxy-helper</command></term>
788 <listitem>
789 <para>
790 creates a socket pair or a named socket. QEMU and the proxy helper
791 communicate using this socket. The QEMU proxy fs driver sends
792 filesystem requests to the proxy helper and receives the response
793 from it
794 </para>
795 <indexterm zone="qemu virtfs-proxy-helper">
796 <primary sortas="b-virtfs-proxy-helper">virtfs-proxy-helper</primary>
797 </indexterm>
798 </listitem>
799 </varlistentry>
800-->
801 </variablelist>
802
803 </sect2>
804
805</sect1>
Note: See TracBrowser for help on using the repository browser.