source: postlfs/virtualization/qemu.xml@ 0fea832

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 0fea832 was 0fea832, checked in by Xi Ruoyao <xry111@…>, 15 months ago

qemu: /dev/kvm mode is now set in LFS, and logind-based access is allowed

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