source: postlfs/virtualization/qemu.xml@ e29b55b2

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

Update to qemu-7.2.0.

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