source: postlfs/virtualization/qemu.xml@ 15edee5

11.0 11.1 11.2 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 upgradedb xry111/intltool xry111/llvm18 xry111/soup3 xry111/test-20220226 xry111/xf86-video-removal
Last change on this file since 15edee5 was 45ab6c7, checked in by Xi Ruoyao <xry111@…>, 3 years ago

more SVN prop clean up

Remove "$LastChanged$" everywhere, and also some unused $Date$
  • Property mode set to 100644
File size: 24.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 "179f86928835da857c237b42f4b2df73">
10 <!ENTITY qemu-size "102 MB">
11 <!ENTITY qemu-buildsize "1.7 GB">
12 <!ENTITY qemu-time "0.9 SBU (using parallelism=4; add 0.3 SBU for tests)">
13]>
14
15<sect1 id="qemu" xreflabel="qemu-&qemu-version;">
16 <?dbhtml filename="qemu.html"?>
17
18 <sect1info>
19 <date>$Date$</date>
20 </sect1info>
21
22 <title>qemu-&qemu-version;</title>
23
24 <indexterm zone="qemu">
25 <primary sortas="a-qemu">qemu</primary>
26 </indexterm>
27
28 <sect2 role="package">
29 <title>Introduction to qemu</title>
30
31 <para>
32 <application>qemu</application> is a full virtualization solution for
33 Linux on x86 hardware containing virtualization extensions (Intel VT or
34 AMD-V).
35 </para>
36
37 &lfs101_checked;
38
39 <bridgehead renderas="sect3">Package Information</bridgehead>
40 <itemizedlist spacing="compact">
41 <listitem>
42 <para>
43 Download (HTTP): <ulink url="&qemu-download-http;"/>
44 </para>
45 </listitem>
46 <listitem>
47 <para>
48 Download (FTP): <ulink url="&qemu-download-ftp;"/>
49 </para>
50 </listitem>
51 <listitem>
52 <para>
53 Download MD5 sum: &qemu-md5sum;
54 </para>
55 </listitem>
56 <listitem>
57 <para>
58 Download size: &qemu-size;
59 </para>
60 </listitem>
61 <listitem>
62 <para>
63 Estimated disk space required: &qemu-buildsize;
64 </para>
65 </listitem>
66 <listitem>
67 <para>
68 Estimated build time: &qemu-time;
69 </para>
70 </listitem>
71 </itemizedlist>
72
73 <bridgehead renderas="sect3">Qemu Dependencies</bridgehead>
74
75 <bridgehead renderas="sect4">Required</bridgehead>
76 <para role="required">
77 <xref linkend="glib2"/>, and
78 <xref linkend="x-window-system"/>
79 </para>
80
81 <bridgehead renderas="sect4">Recommended</bridgehead>
82 <para role="recommended">
83 <xref linkend="alsa-lib"/> and
84 <xref linkend="sdl2"/>
85 </para>
86
87 <bridgehead renderas="sect4">Optional</bridgehead>
88 <para role="optional">
89 Depending on the sound system, various packages in <xref linkend="alsa"/>,
90 <xref linkend="python3"/>,
91 <xref linkend="pulseaudio"/>,
92 <xref linkend="bluez"/>,
93 <xref linkend="curl"/>,
94 <xref linkend="cyrus-sasl"/>,
95 <xref linkend="gnutls"/>,
96 <xref linkend="gtk2"/>,
97 <xref linkend="gtk3"/>,
98 <xref linkend="libusb"/>,
99 <xref linkend="libgcrypt"/>,
100 <xref linkend="libssh2"/>,
101 <xref linkend="lzo"/>,
102 <xref linkend="nettle"/>,
103 <xref linkend="mesa"/>,
104 <xref linkend="sdl"/>,
105 <xref role="nodep" linkend="vte"/> or <xref linkend="vte2"/>, and
106<!-- libcacard has been a standalone project since qemu-2.5.-->
107 <ulink url="https://www.spice-space.org/page/Libcacard">libcacard</ulink>
108 </para>
109
110 <note>
111 <para>
112 This optional dependencies list is not comprehensive. See the output of
113 <command>./configure --help</command> for a more complete list.
114 </para>
115 </note>
116
117 <para condition="html" role="usernotes">User Notes:
118 <ulink url="&blfs-wiki;/qemu"/></para>
119
120 </sect2>
121
122 <sect2 id='qemu-prereq'>
123 <title>KVM Prerequisites</title>
124
125 <para>
126 Before building <application>qemu</application>, check to see if
127 your processor supports Virtualization Technology (VT):
128 </para>
129
130 <screen><userinput>egrep '^flags.*(vmx|svm)' /proc/cpuinfo</userinput></screen>
131
132 <para>
133 If you get any output, you have VT technology (vmx for Intel
134 processors and svm for AMD processors). You then need to go into your
135 system BIOS and ensure it is enabled. After enabing, reboot back to your
136 LFS instance.
137 </para>
138
139 </sect2>
140
141 <sect2 role="kernel" id='qemu-kernel'>
142 <title>Kernel Configuration</title>
143
144 <para>
145 Enable the following options in the kernel configuration and
146 recompile the kernel if necessary:
147 </para>
148
149<screen><literal>[*] Virtualization: ---&gt; [CONFIG_VIRTUALIZATION]
150 &lt;*/M&gt; Kernel-based Virtual Machine (KVM) support [CONFIG_KVM]
151 &lt;*/M&gt; KVM for Intel (and compatible) processors support [CONFIG_KVM_INTEL]
152 &lt;*/M&gt; KVM for AMD processors support [CONFIG_KVM_AMD]</literal></screen>
153
154 <indexterm zone="qemu qemu-kernel">
155 <primary sortas="d-qemu">qemu</primary>
156 </indexterm>
157
158 <para>
159 The Intel or AMD settings are not both required, but the one matching
160 your system processor is required.
161 </para>
162
163 <para>
164 To use the <quote>bridge</quote> network device, as explained below,
165 check that <xref linkend='bridgeutils'/> is installed
166 and the following options in the kernel configuration are enabled:
167 </para>
168
169<screen><literal>[*] Networking support ---&gt; [CONFIG_NET]
170 Networking options ---&gt;
171 &lt;*/M&gt; 802.1d Ethernet Bridging [CONFIG_BRIDGE]
172Device Drivers ---&gt;
173 [*] Network device support ---&gt; [CONFIG_NETDEVICES]
174 &lt;*/M&gt; Universal TUN/TAP device driver support [CONFIG_TUN]</literal></screen>
175
176 </sect2>
177
178 <sect2 role="installation">
179 <title>Installation of qemu</title>
180
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 Add any users that might use the KVM device to that group:
192 </para>
193
194<screen role="root"><userinput>usermod -a -G kvm <replaceable>&lt;username&gt;</replaceable></userinput></screen>
195
196 <para>
197 Fix an issue exposed by binutils-2.36:
198 </para>
199
200<screen><userinput>sed -i "/LDFLAGS_NOPIE/d" configure pc-bios/optionrom/Makefile</userinput></screen>
201
202 <para>
203 Install <application>qemu</application> by running the following
204 commands:
205 </para>
206
207 <note>
208 <para>
209 Qemu is capable of running many targets. The build process
210 is also capable of building multiple targets at one time in a
211 comma delimited list assigned to <option>--target-list</option>. Run
212 <command>./configure --help</command> to get a complete list of
213 available targets.
214 </para>
215 </note>
216
217
218<screen><userinput>if [ $(uname -m) = i686 ]; then
219 QEMU_ARCH=i386-softmmu
220else
221 QEMU_ARCH=x86_64-softmmu
222fi
223
224
225mkdir -vp build &amp;&amp;
226cd build &amp;&amp;
227
228../configure --prefix=/usr \
229 --sysconfdir=/etc \
230 --target-list=$QEMU_ARCH \
231 --audio-drv-list=alsa \
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:
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):
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:
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<!-- Not used anymore
282 <para>
283 <command>sed ... util/memfd.c</command>: This command fixes a conflict
284 introduced with glibc-2.27.
285 </para>
286-->
287 <para>
288 <parameter>--audio-drv-list=alsa</parameter>: This switch sets the audio
289 driver to ALSA. See below for enabling other audio drivers.
290 </para>
291
292 <para>
293 <option>--audio-drv-list=pa</option>: This switch sets the audio
294 driver to pulseaudio. For other drivers see the --audio-drv-list list in
295 <command>configure</command>'s help output. The default audio driver is
296 OSS. To enable support for both alsa and pulseaudio, use
297 <option>--audio-drv-list=alsa,pa</option>.
298 </para>
299
300 <!-- this appears to be rejected in 4.1.0
301 ERROR: unknown option \-\-with-gtkabi=3.0
302 <para>
303 <option>\-\-with-gtkabi=3.0</option>: builds with GTK+-3 if both GTK+-2
304 and GTK+-3 are installed.
305 </para> -->
306
307 </sect2>
308
309 <sect2 role="using">
310 <title>Using Qemu</title>
311
312 <para>
313 Since using qemu means using a virtual computer, the steps to set up
314 the virtual machine are in close analogy with those to set up a real
315 computer. You'll need to decide about CPU, memory, disk, USB devices,
316 network card(s), screen size, etc. Once the <quote>hardware</quote> is
317 decided, you'll have for example to choose how to connect the machine
318 to internet, and/or to install an OS. In the following, we show basic
319 ways of performing those steps. But qemu is much more than this, and it
320 is strongly advised to read the qemu documentation in
321 <filename>/usr/share/doc/qemu-&qemu-version;/qemu-doc.html</filename>.
322 </para>
323
324 <note>
325 <para>
326 It is standard practice to name the computer running qemu
327 <quote>host</quote> and the emulated machine running under qemu the
328 <quote>guest</quote>. We'll use those notations in the following.
329 </para>
330 </note>
331
332 <note>
333 <para>
334 The following instructions assume the optional symbolic link,
335 <filename>qemu</filename>, has been created. Additionally,
336 <command>qemu</command> must be run from an X Window System based
337 terminal (either locally or over ssh).
338 </para>
339 </note>
340
341 <bridgehead renderas="sect3">Disk</bridgehead>
342 <para>
343 A virtual disk may be set up in the following way:
344 </para>
345
346<screen><userinput>VDISK_SIZE=<replaceable>50G</replaceable>
347VDISK_FILENAME=<replaceable>vdisk.img</replaceable>
348qemu-img create -f qcow2 $VDISK_FILENAME $VDISK_SIZE</userinput></screen>
349
350 <para>
351 The virtual disk size and filename should be ajusted as desired. The
352 actual size of the file will be less than specified, but will expand as
353 needed, so it is safe to put a high value.
354 </para>
355
356 <bridgehead renderas="sect3">Operating System</bridgehead>
357 <para>
358 To install an operating system, download an iso image from your preferred
359 Linux distribution. For the purposes of this example, we'll use
360 <filename>Fedora-16-x86_64-Live-LXDE.iso</filename> in the current
361 directory. Run the following:
362 </para>
363
364<screen><userinput>qemu -enable-kvm \
365 -drive file=$VDISK_FILENAME \
366 -cdrom Fedora-16-x86_64-Live-LXDE.iso \
367 -boot d \
368 -m <replaceable>1G</replaceable></userinput></screen>
369
370 <para>
371 Follow the normal installation procedures for the chosen distribution.
372 The <parameter>-boot</parameter> option specifies the boot order of
373 drives as a string of drive letters. Valid drive letters are: a, b
374 (floppy 1 and 2), c (first hard disk), d (first CD-ROM). The
375 <parameter>-m</parameter> option is the amount of memory to use for the
376 virtual machine. The choice depends on the load of the host. Modern
377 distributions should be comfortable with 1GB.
378 The <parameter>-enable-kvm</parameter> option allows hardware
379 acceleration. Without this switch, the emulation is much slower.
380 </para>
381
382 <bridgehead renderas="sect3">Defining the virtual hardware</bridgehead>
383 <para>
384 The virtual machine hardware is defined by the qemu command line.
385 An example command is given below:
386 </para>
387
388<screen><userinput>qemu -enable-kvm \
389 -smp 4 \
390 -cpu host \
391 -m 1G \
392 -drive file=$VDISK_FILENAME \
393 -cdrom grub-img.iso \
394 -boot order=c,once=d,menu=on \
395 -net nic,netdev=net0 \
396 -netdev user,id=net0 \
397 -device ac97 \
398 -vga std \
399 -serial mon:stdio \
400 -name "fedora-16"</userinput></screen>
401
402 <bridgehead renderas="sect3">Meaning of the command line options</bridgehead>
403 <para>
404 <parameter>-enable-kvm</parameter>: enable full KVM virtualization
405 support. On some hardware, it may be necessary to add the undocumented
406 <option>-machine smm=off</option> option in order to enable KVM.
407 </para>
408
409 <para>
410 <parameter>-smp &lt;N&gt;</parameter>: enable symmetric multiprocessing
411 with &lt;N&gt; CPUs.
412 </para>
413
414 <para>
415 <parameter>-cpu &lt;model&gt;</parameter>: simulate CPU &lt;model&gt;.
416 the list of supported models can be obtained with <option>-cpu
417 help</option>.
418 </para>
419
420 <para>
421 <parameter>-drive file=&lt;filename&gt;</parameter>: defines a virtual
422 disk whose image is stored in <filename>&lt;filename&gt;</filename>.
423 </para>
424
425 <para>
426 <parameter>-cdrom grub-img.iso</parameter>: defines an iso formated file
427 to use as a cdrom. Here we use a grub rescue disk, which may turn handy
428 when something goes wrong at boot time.
429 </para>
430
431 <para>
432 <parameter>-boot order=c,once=d,menu=on</parameter>: defines the boot
433 order for the virtual BIOS.
434 </para>
435
436 <para>
437 <parameter>-net nic,netdev=&lt;netid&gt;</parameter>: defines a network
438 card connected to the network device with id &lt;netid&gt;.
439 </para>
440
441 <para>
442 <parameter>-netdev user,id=&lt;netid&gt;</parameter>: defines the
443 network <quote>user</quote> device. This is a virtual local network
444 with addresses 10.0.2.0/24, where the host has address 10.0.2.2 and
445 acts as a gateway to internet, and with a name server at address
446 10.0.2.3, and an smb server at address 10.0.2.4. A builtin DHCP server
447 can allocate addresses between 10.0.2.15 and 10.0.2.31.
448 </para>
449
450 <para>
451 <parameter>-soundhw &lt;model&gt;</parameter>: defines the soundcard
452 model. The list may be obtained with <option>-soundhw help</option>.
453 </para>
454
455 <para>
456 <parameter>-vga &lt;type&gt;</parameter>: defines the type of vga card
457 to emulate.
458 </para>
459
460 <para>
461 <parameter>-serial mon:stdio</parameter>: sends the serial port of the
462 guest (<filename>/dev/ttyS0</filename> on linux guests), multiplexed with
463 the qemu monitor, to the standard input and output of the qemu
464 process.
465 </para>
466
467 <para>
468 <parameter>-name &lt;name&gt;</parameter>: sets the name of the guest.
469 This name is displayed in the guest window caption. It may be useful
470 if you run several guests at the same time.
471 </para>
472
473 <bridgehead renderas="sect3">Controlling the Emulated Display</bridgehead>
474 <para>
475 It may happen that the guest window displayed by qemu does not correspond
476 to the full capability of the emulated vga card. For example, the vmware
477 card is 1600x900 capable, but only 1024x768 is displayed by default.
478 A suitable Xorg configuration on the guest allows to use the full size
479 (Note that the Xorg video driver to use is <xref
480 linkend="xorg-vmware-driver"/>):
481 </para>
482
483<screen role="root"><userinput>cat &gt; /usr/share/X11/xorg.conf.d/20-vmware.conf &lt;&lt; "EOF"
484<literal>Section "Monitor"
485 Identifier "Monitor0"
486 # cvt 1600 900
487 # 1600x900 59.95 Hz (CVT 1.44M9) hsync: 55.99 kHz; pclk: 118.25 MHz
488 Modeline "1600x900" 118.25 1600 1696 1856 2112 900 903 908 934 -hsync +vsync
489 Option "PreferredMode" "1600x900"
490 HorizSync 1-200
491 VertRefresh 1-200
492EndSection
493
494Section "Device"
495 Identifier "VMware SVGA II Adapter"
496 Option "Monitor" "default"
497 Driver "vmware"
498EndSection
499
500Section "Screen"
501 Identifier "Default Screen"
502 Device "VMware SVGA II Adapter"
503 Monitor "Monitor0"
504
505 SubSection "Display"
506 Depth 24
507 Modes "1600x900" "1440x900" "1366x768" "1280x720" "800x480"
508 EndSubSection
509
510EndSection</literal>
511EOF</userinput></screen>
512
513 <para>
514 New sizes will be available besides the native ones. You need to
515 restart X in order to have the new sizes available.
516 </para>
517
518 <bridgehead renderas="sect3">Networking</bridgehead>
519 <para>
520 The above solution for networking allows the guest to access the local
521 network through the host (and possibly to access internet through the
522 local routers), but the converse is not true. Not even the host can
523 access the guest, unless port forwarding is enabled. And in the case
524 several guests are running, they cannot communicate with each other.
525 Other network devices can be used for this purpose. For example, there
526 is the <quote>socket</quote> device, which allows several guests to
527 share a common virtual network. In the following, we describe in more
528 details how to set up the <quote>bridge</quote> device, which allows
529 the guests to appear as if connected to the local network. All the
530 commands below should be run as the <systemitem
531 class="username">root</systemitem> user.
532 </para>
533
534 <para revision="sysv">
535 Set up bridging with <xref linkend="bridgeutils"/>. Only the physical
536 interface(s) should be set up at boot. The virtual interface(s) will be
537 added as needed when qemu is started.
538 </para>
539
540 <para revision="systemd">
541 <!-- On SYS-V, IP_FORWARD is enabled by the bridge script. -->
542 Allow the host to forward IP packets:
543 </para>
544
545<screen role="root"
546 revision="systemd"><userinput>sysctl -w net.ipv4.ip_forward=1</userinput></screen>
547
548 <para revision="systemd">
549 To make this permanent, add the command to
550 <filename>/etc/sysctl.d/60-net-forward.conf:</filename>
551 </para>
552
553<screen role="root"
554 revision="systemd"><userinput>cat &gt;&gt; /etc/sysctl.d/60-net-forward.conf &lt;&lt; EOF
555<literal>net.ipv4.ip_forward=1</literal>
556EOF</userinput></screen>
557
558 <para>
559 Set up a required configuration file:
560 </para>
561
562<!-- /etc/qemu has not been installed by "make install" since version 2.4 -->
563<screen role="root"><userinput>install -vdm 755 /etc/qemu &amp;&amp;
564echo allow br0 &gt; /etc/qemu/bridge.conf</userinput></screen>
565
566 <para>
567 In the command above, replace the switch <parameter>-netdev user,...
568 </parameter> with <parameter>-netdev bridge,id=net0</parameter>.
569 </para>
570
571 </sect2>
572
573 <sect2 role="content">
574 <title>Contents</title>
575
576 <segmentedlist>
577 <segtitle>Installed Programs</segtitle>
578 <segtitle>Installed Library</segtitle>
579 <segtitle>Installed Directories</segtitle>
580
581 <seglistitem>
582 <seg>
583 ivshmem-client,
584 ivshmem-server,
585 qemu (symlink),
586 qemu-ga,
587 qemu-img,
588 qemu-io,
589 qemu-nbd,
590 qemu-system-&lt;arch&gt;, and
591 virtfs-proxy-helper
592 </seg>
593 <seg>None</seg>
594 <seg>
595 /usr/share/qemu and
596 /usr/share/doc/qemu-&qemu-version;
597 </seg>
598 </seglistitem>
599 </segmentedlist>
600
601 <variablelist>
602 <bridgehead renderas="sect3">Short Description</bridgehead>
603 <?dbfo list-presentation="list"?>
604 <?dbhtml list-presentation="table"?>
605
606 <varlistentry id="ivshmem-client">
607 <term><command>ivshmem-client</command></term>
608 <listitem>
609 <para>
610 is a standalone client for using the ivshmem device
611 </para>
612 <indexterm zone="qemu ivshmem-client">
613 <primary sortas="b-ivshmem-client">ivshmem-client</primary>
614 </indexterm>
615 </listitem>
616 </varlistentry>
617
618 <varlistentry id="ivshmem-server">
619 <term><command>ivshmem-server</command></term>
620 <listitem>
621 <para>
622 is an example server for the ivshmem device
623 </para>
624 <indexterm zone="qemu ivshmem-server">
625 <primary sortas="b-ivshmem-server">ivshmem-server</primary>
626 </indexterm>
627 </listitem>
628 </varlistentry>
629
630 <varlistentry id="qemu-edid">
631 <term><command>qemu-edid</command></term>
632 <listitem>
633 <para>
634 is a test tool for the qemu EDID generator
635 </para>
636 <indexterm zone="qemu qemu-edid">
637 <primary sortas="b-qemu-edid">qemu-edid</primary>
638 </indexterm>
639 </listitem>
640 </varlistentry>
641
642 <varlistentry id="qemu-ga">
643 <term><command>qemu-ga</command></term>
644 <listitem>
645 <para>
646 implements support for QMP (QEMU Monitor Protocol) commands and
647 events that terminate and originate respectively within the guest
648 using an agent built as part of QEMU
649 </para>
650 <indexterm zone="qemu qemu-ga">
651 <primary sortas="b-qemu-ga">qemu-ga</primary>
652 </indexterm>
653 </listitem>
654 </varlistentry>
655
656 <varlistentry id="qemu-img">
657 <term><command>qemu-img</command></term>
658 <listitem>
659 <para>
660 provides commands to manage QEMU disk images
661 </para>
662 <indexterm zone="qemu qemu-img">
663 <primary sortas="b-qemu-img">qemu-img</primary>
664 </indexterm>
665 </listitem>
666 </varlistentry>
667
668 <varlistentry id="qemu-io">
669 <term><command>qemu-io</command></term>
670 <listitem>
671 <para>
672 is a diagnostic and manipulation program for (virtual) memory
673 media. It is still at an early stage of development
674 </para>
675 <indexterm zone="qemu qemu-io">
676 <primary sortas="b-qemu-io">qemu-io</primary>
677 </indexterm>
678 </listitem>
679 </varlistentry>
680
681 <varlistentry id="qemu-nbd">
682 <term><command>qemu-nbd</command></term>
683 <listitem>
684 <para>
685 exports Qemu disk images using the QEMU Disk Network Block
686 Device (NBD) protocol
687 </para>
688 <indexterm zone="qemu qemu-nbd">
689 <primary sortas="b-qemu-nbd">qemu-nbd</primary>
690 </indexterm>
691 </listitem>
692 </varlistentry>
693
694 <varlistentry id="qemu-system">
695 <term><command>qemu-system-x86_64</command></term>
696 <listitem>
697 <para>
698 is the QEMU PC System emulator
699 </para>
700 <indexterm zone="qemu qemu-system">
701 <primary sortas="b-qemu-system">qemu-system-x86_64</primary>
702 </indexterm>
703 </listitem>
704 </varlistentry>
705
706 <varlistentry id="virtfs-proxy-helper">
707 <term><command>virtfs-proxy-helper</command></term>
708 <listitem>
709 <para>
710 creates a socket pair or a named socket. QEMU and proxy helper
711 communicate using this socket. QEMU proxy fs driver sends
712 filesystem request to proxy helper and receives the response
713 from it
714 </para>
715 <indexterm zone="qemu virtfs-proxy-helper">
716 <primary sortas="b-virtfs-proxy-helper">virtfs-proxy-helper</primary>
717 </indexterm>
718 </listitem>
719 </varlistentry>
720
721 </variablelist>
722
723 </sect2>
724
725</sect1>
Note: See TracBrowser for help on using the repository browser.