source: postlfs/virtualization/qemu.xml@ 5b1bcc93

12.0 12.1 ken/TL2024 ken/tuningfonts lazarus plabs/newcss python3.11 rahul/power-profiles-daemon renodr/vulkan-addition trunk xry111/llvm18
Last change on this file since 5b1bcc93 was 17b1ad9, checked in by Xi Ruoyao <xry111@…>, 11 months ago

qemu: Fix the command option for running UEFI

A plain "-pflash <file>" option does not work if <file> is not writable
with the current qemu version.

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