source: postlfs/virtualization/qemu.xml@ cf905e0

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 cf905e0 was cf905e0, checked in by Pierre Labastie <pierre.labastie@…>, 19 months ago

Merge branch 'trunk' into plabs/python-mods

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