source: postlfs/virtualization/qemu.xml@ 7ebdf4e

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 7ebdf4e was 293e4018, checked in by Xi Ruoyao <xry111@…>, 11 months ago

qemu: Remove dependency to x-window-system

I'm pretty sure it's at least not "required": there are some
configurations running qemu "headless".

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