source: postlfs/virtualization/qemu.xml@ fefc5d54

11.0 ken/refactor-virt lazarus qt5new trunk
Last change on this file since fefc5d54 was fefc5d54, checked in by Douglas R. Reno <renodr@…>, 5 months ago

Qemu: Fix libcacrd URL

  • Property mode set to 100644
File size: 23.9 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 "cce185dc0119546e395909e8a71a75bb">
10 <!ENTITY qemu-size "102 MB">
11 <!ENTITY qemu-buildsize "2.2 GB">
12 <!ENTITY qemu-time "1.2 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://gitlab.freedesktop.org/spice/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 Install <application>qemu</application> by running the following
198 commands:
199 </para>
200
201 <note>
202 <para>
203 Qemu is capable of running many targets. The build process
204 is also capable of building multiple targets at one time in a
205 comma delimited list assigned to <option>--target-list</option>. Run
206 <command>./configure --help</command> to get a complete list of
207 available targets.
208 </para>
209 </note>
210
211
212<screen><userinput>if [ $(uname -m) = i686 ]; then
213 QEMU_ARCH=i386-softmmu
214else
215 QEMU_ARCH=x86_64-softmmu
216fi
217
218
219mkdir -vp build &amp;&amp;
220cd build &amp;&amp;
221
222../configure --prefix=/usr \
223 --sysconfdir=/etc \
224 --target-list=$QEMU_ARCH \
225 --audio-drv-list=alsa \
226 --docdir=/usr/share/doc/qemu-&qemu-version; &amp;&amp;
227
228unset QEMU_ARCH &amp;&amp;
229
230make</userinput></screen>
231
232 <para>
233 <application>qemu</application> uses <command>ninja</command> as
234 a subprocess when building. To run the tests, issue:
235 <command>ninja test</command>.
236 </para>
237
238 <para>
239 Now, as the <systemitem class="username">root</systemitem> user:
240 </para>
241
242<screen role="root"><userinput>make install</userinput></screen>
243
244 <para>
245 You will also need to add an Udev rule so that the KVM device gets correct
246 permissions:
247 </para>
248
249<screen role="root"><userinput>cat > /lib/udev/rules.d/65-kvm.rules &lt;&lt; "EOF"
250<literal>KERNEL=="kvm", GROUP="kvm", MODE="0660"</literal>
251EOF</userinput></screen>
252
253 <para>
254 Change the permissions and ownership of a helper script, which is needed
255 when using the <quote>bridge</quote> network device (see below):
256 </para>
257
258<screen role="root"><userinput>chgrp kvm /usr/libexec/qemu-bridge-helper &amp;&amp;
259chmod 4750 /usr/libexec/qemu-bridge-helper</userinput></screen>
260
261 <note>
262 <para>
263 For convenience you may want to create a symbolic link to run
264 the installed program. For instance:
265 </para>
266
267<screen role="root"><userinput>ln -sv qemu-system-`uname -m` /usr/bin/qemu</userinput></screen>
268 </note>
269
270 </sect2>
271
272 <sect2 role="commands">
273 <title>Command Explanations</title>
274
275<!-- Not used anymore
276 <para>
277 <command>sed ... util/memfd.c</command>: This command fixes a conflict
278 introduced with glibc-2.27.
279 </para>
280-->
281 <para>
282 <parameter>--audio-drv-list=alsa</parameter>: This switch sets the audio
283 driver to ALSA. See below for enabling other audio drivers.
284 </para>
285
286 <para>
287 <option>--audio-drv-list=pa</option>: This switch sets the audio
288 driver to pulseaudio. For other drivers see the --audio-drv-list list in
289 <command>configure</command>'s help output. The default audio driver is
290 OSS. To enable support for both alsa and pulseaudio, use
291 <option>--audio-drv-list=alsa,pa</option>.
292 </para>
293
294 <!-- this appears to be rejected in 4.1.0
295 ERROR: unknown option \-\-with-gtkabi=3.0
296 <para>
297 <option>\-\-with-gtkabi=3.0</option>: builds with GTK+-3 if both GTK+-2
298 and GTK+-3 are installed.
299 </para> -->
300
301 </sect2>
302
303 <sect2 role="using">
304 <title>Using Qemu</title>
305
306 <para>
307 Since using qemu means using a virtual computer, the steps to set up
308 the virtual machine are in close analogy with those to set up a real
309 computer. You'll need to decide about CPU, memory, disk, USB devices,
310 network card(s), screen size, etc. Once the <quote>hardware</quote> is
311 decided, you'll have for example to choose how to connect the machine
312 to internet, and/or to install an OS. In the following, we show basic
313 ways of performing those steps. But qemu is much more than this, and it
314 is strongly advised to read the qemu documentation in
315 <filename>/usr/share/doc/qemu-&qemu-version;/qemu-doc.html</filename>.
316 </para>
317
318 <note>
319 <para>
320 It is standard practice to name the computer running qemu
321 <quote>host</quote> and the emulated machine running under qemu the
322 <quote>guest</quote>. We'll use those notations in the following.
323 </para>
324 </note>
325
326 <note>
327 <para>
328 The following instructions assume the optional symbolic link,
329 <filename>qemu</filename>, has been created. Additionally,
330 <command>qemu</command> must be run from an X Window System based
331 terminal (either locally or over ssh).
332 </para>
333 </note>
334
335 <bridgehead renderas="sect3">Disk</bridgehead>
336 <para>
337 A virtual disk may be set up in the following way:
338 </para>
339
340<screen><userinput>VDISK_SIZE=<replaceable>50G</replaceable>
341VDISK_FILENAME=<replaceable>vdisk.img</replaceable>
342qemu-img create -f qcow2 $VDISK_FILENAME $VDISK_SIZE</userinput></screen>
343
344 <para>
345 The virtual disk size and filename should be ajusted as desired. The
346 actual size of the file will be less than specified, but will expand as
347 needed, so it is safe to put a high value.
348 </para>
349
350 <bridgehead renderas="sect3">Operating System</bridgehead>
351 <para>
352 To install an operating system, download an iso image from your preferred
353 Linux distribution. For the purposes of this example, we'll use
354 <filename>Fedora-16-x86_64-Live-LXDE.iso</filename> in the current
355 directory. Run the following:
356 </para>
357
358<screen><userinput>qemu -enable-kvm \
359 -drive file=$VDISK_FILENAME \
360 -cdrom Fedora-16-x86_64-Live-LXDE.iso \
361 -boot d \
362 -m <replaceable>1G</replaceable></userinput></screen>
363
364 <para>
365 Follow the normal installation procedures for the chosen distribution.
366 The <parameter>-boot</parameter> option specifies the boot order of
367 drives as a string of drive letters. Valid drive letters are: a, b
368 (floppy 1 and 2), c (first hard disk), d (first CD-ROM). The
369 <parameter>-m</parameter> option is the amount of memory to use for the
370 virtual machine. The choice depends on the load of the host. Modern
371 distributions should be comfortable with 1GB.
372 The <parameter>-enable-kvm</parameter> option allows hardware
373 acceleration. Without this switch, the emulation is much slower.
374 </para>
375
376 <bridgehead renderas="sect3">Defining the virtual hardware</bridgehead>
377 <para>
378 The virtual machine hardware is defined by the qemu command line.
379 An example command is given below:
380 </para>
381
382<screen><userinput>qemu -enable-kvm \
383 -smp 4 \
384 -cpu host \
385 -m 1G \
386 -drive file=$VDISK_FILENAME \
387 -cdrom grub-img.iso \
388 -boot order=c,once=d,menu=on \
389 -net nic,netdev=net0 \
390 -netdev user,id=net0 \
391 -device ac97 \
392 -vga std \
393 -serial mon:stdio \
394 -name "fedora-16"</userinput></screen>
395
396 <bridgehead renderas="sect3">Meaning of the command line options</bridgehead>
397 <para>
398 <parameter>-enable-kvm</parameter>: enable full KVM virtualization
399 support. On some hardware, it may be necessary to add the undocumented
400 <option>-machine smm=off</option> option in order to enable KVM.
401 </para>
402
403 <para>
404 <parameter>-smp &lt;N&gt;</parameter>: enable symmetric multiprocessing
405 with &lt;N&gt; CPUs.
406 </para>
407
408 <para>
409 <parameter>-cpu &lt;model&gt;</parameter>: simulate CPU &lt;model&gt;.
410 the list of supported models can be obtained with <option>-cpu
411 help</option>.
412 </para>
413
414 <para>
415 <parameter>-drive file=&lt;filename&gt;</parameter>: defines a virtual
416 disk whose image is stored in <filename>&lt;filename&gt;</filename>.
417 </para>
418
419 <para>
420 <parameter>-cdrom grub-img.iso</parameter>: defines an iso formated file
421 to use as a cdrom. Here we use a grub rescue disk, which may turn handy
422 when something goes wrong at boot time.
423 </para>
424
425 <para>
426 <parameter>-boot order=c,once=d,menu=on</parameter>: defines the boot
427 order for the virtual BIOS.
428 </para>
429
430 <para>
431 <parameter>-net nic,netdev=&lt;netid&gt;</parameter>: defines a network
432 card connected to the network device with id &lt;netid&gt;.
433 </para>
434
435 <para>
436 <parameter>-netdev user,id=&lt;netid&gt;</parameter>: defines the
437 network <quote>user</quote> device. This is a virtual local network
438 with addresses 10.0.2.0/24, where the host has address 10.0.2.2 and
439 acts as a gateway to internet, and with a name server at address
440 10.0.2.3, and an smb server at address 10.0.2.4. A builtin DHCP server
441 can allocate addresses between 10.0.2.15 and 10.0.2.31.
442 </para>
443
444 <para>
445 <parameter>-soundhw &lt;model&gt;</parameter>: defines the soundcard
446 model. The list may be obtained with <option>-soundhw help</option>.
447 </para>
448
449 <para>
450 <parameter>-vga &lt;type&gt;</parameter>: defines the type of vga card
451 to emulate.
452 </para>
453
454 <para>
455 <parameter>-serial mon:stdio</parameter>: sends the serial port of the
456 guest (<filename>/dev/ttyS0</filename> on linux guests), multiplexed with
457 the qemu monitor, to the standard input and output of the qemu
458 process.
459 </para>
460
461 <para>
462 <parameter>-name &lt;name&gt;</parameter>: sets the name of the guest.
463 This name is displayed in the guest window caption. It may be useful
464 if you run several guests at the same time.
465 </para>
466
467 <bridgehead renderas="sect3">Controlling the Emulated Display</bridgehead>
468 <para>
469 It may happen that the guest window displayed by qemu does not correspond
470 to the full capability of the emulated vga card. For example, the vmware
471 card is 1600x900 capable, but only 1024x768 is displayed by default.
472 A suitable Xorg configuration on the guest allows to use the full size
473 (Note that the Xorg video driver to use is <xref
474 linkend="xorg-vmware-driver"/>):
475 </para>
476
477<screen role="root"><userinput>cat &gt; /usr/share/X11/xorg.conf.d/20-vmware.conf &lt;&lt; "EOF"
478<literal>Section "Monitor"
479 Identifier "Monitor0"
480 # cvt 1600 900
481 # 1600x900 59.95 Hz (CVT 1.44M9) hsync: 55.99 kHz; pclk: 118.25 MHz
482 Modeline "1600x900" 118.25 1600 1696 1856 2112 900 903 908 934 -hsync +vsync
483 Option "PreferredMode" "1600x900"
484 HorizSync 1-200
485 VertRefresh 1-200
486EndSection
487
488Section "Device"
489 Identifier "VMware SVGA II Adapter"
490 Option "Monitor" "default"
491 Driver "vmware"
492EndSection
493
494Section "Screen"
495 Identifier "Default Screen"
496 Device "VMware SVGA II Adapter"
497 Monitor "Monitor0"
498
499 SubSection "Display"
500 Depth 24
501 Modes "1600x900" "1440x900" "1366x768" "1280x720" "800x480"
502 EndSubSection
503
504EndSection</literal>
505EOF</userinput></screen>
506
507 <para>
508 New sizes will be available besides the native ones. You need to
509 restart X in order to have the new sizes available.
510 </para>
511
512 <bridgehead renderas="sect3">Networking</bridgehead>
513 <para>
514 The above solution for networking allows the guest to access the local
515 network through the host (and possibly to access internet through the
516 local routers), but the converse is not true. Not even the host can
517 access the guest, unless port forwarding is enabled. And in the case
518 several guests are running, they cannot communicate with each other.
519 Other network devices can be used for this purpose. For example, there
520 is the <quote>socket</quote> device, which allows several guests to
521 share a common virtual network. In the following, we describe in more
522 details how to set up the <quote>bridge</quote> device, which allows
523 the guests to appear as if connected to the local network. All the
524 commands below should be run as the <systemitem
525 class="username">root</systemitem> user.
526 </para>
527
528 <para revision="sysv">
529 Set up bridging with <xref linkend="bridgeutils"/>. Only the physical
530 interface(s) should be set up at boot. The virtual interface(s) will be
531 added as needed when qemu is started.
532 </para>
533
534 <para revision="systemd">
535 <!-- On SYS-V, IP_FORWARD is enabled by the bridge script. -->
536 Allow the host to forward IP packets:
537 </para>
538
539<screen role="root"
540 revision="systemd"><userinput>sysctl -w net.ipv4.ip_forward=1</userinput></screen>
541
542 <para revision="systemd">
543 To make this permanent, add the command to
544 <filename>/etc/sysctl.d/60-net-forward.conf:</filename>
545 </para>
546
547<screen role="root"
548 revision="systemd"><userinput>cat &gt;&gt; /etc/sysctl.d/60-net-forward.conf &lt;&lt; EOF
549<literal>net.ipv4.ip_forward=1</literal>
550EOF</userinput></screen>
551
552 <para>
553 Set up a required configuration file:
554 </para>
555
556<!-- /etc/qemu has not been installed by "make install" since version 2.4 -->
557<screen role="root"><userinput>install -vdm 755 /etc/qemu &amp;&amp;
558echo allow br0 &gt; /etc/qemu/bridge.conf</userinput></screen>
559
560 <para>
561 In the command above, replace the switch <parameter>-netdev user,...
562 </parameter> with <parameter>-netdev bridge,id=net0</parameter>.
563 </para>
564
565 </sect2>
566
567 <sect2 role="content">
568 <title>Contents</title>
569
570 <segmentedlist>
571 <segtitle>Installed Programs</segtitle>
572 <segtitle>Installed Library</segtitle>
573 <segtitle>Installed Directories</segtitle>
574
575 <seglistitem>
576 <seg>
577 ivshmem-client,
578 ivshmem-server,
579 qemu (symlink),
580 qemu-ga,
581 qemu-img,
582 qemu-io,
583 qemu-nbd,
584 qemu-system-&lt;arch&gt;, and
585 virtfs-proxy-helper
586 </seg>
587 <seg>None</seg>
588 <seg>
589 /usr/share/qemu and
590 /usr/share/doc/qemu-&qemu-version;
591 </seg>
592 </seglistitem>
593 </segmentedlist>
594
595 <variablelist>
596 <bridgehead renderas="sect3">Short Description</bridgehead>
597 <?dbfo list-presentation="list"?>
598 <?dbhtml list-presentation="table"?>
599
600 <varlistentry id="ivshmem-client">
601 <term><command>ivshmem-client</command></term>
602 <listitem>
603 <para>
604 is a standalone client for using the ivshmem device
605 </para>
606 <indexterm zone="qemu ivshmem-client">
607 <primary sortas="b-ivshmem-client">ivshmem-client</primary>
608 </indexterm>
609 </listitem>
610 </varlistentry>
611
612 <varlistentry id="ivshmem-server">
613 <term><command>ivshmem-server</command></term>
614 <listitem>
615 <para>
616 is an example server for the ivshmem device
617 </para>
618 <indexterm zone="qemu ivshmem-server">
619 <primary sortas="b-ivshmem-server">ivshmem-server</primary>
620 </indexterm>
621 </listitem>
622 </varlistentry>
623
624 <varlistentry id="qemu-edid">
625 <term><command>qemu-edid</command></term>
626 <listitem>
627 <para>
628 is a test tool for the qemu EDID generator
629 </para>
630 <indexterm zone="qemu qemu-edid">
631 <primary sortas="b-qemu-edid">qemu-edid</primary>
632 </indexterm>
633 </listitem>
634 </varlistentry>
635
636 <varlistentry id="qemu-ga">
637 <term><command>qemu-ga</command></term>
638 <listitem>
639 <para>
640 implements support for QMP (QEMU Monitor Protocol) commands and
641 events that terminate and originate respectively within the guest
642 using an agent built as part of QEMU
643 </para>
644 <indexterm zone="qemu qemu-ga">
645 <primary sortas="b-qemu-ga">qemu-ga</primary>
646 </indexterm>
647 </listitem>
648 </varlistentry>
649
650 <varlistentry id="qemu-img">
651 <term><command>qemu-img</command></term>
652 <listitem>
653 <para>
654 provides commands to manage QEMU disk images
655 </para>
656 <indexterm zone="qemu qemu-img">
657 <primary sortas="b-qemu-img">qemu-img</primary>
658 </indexterm>
659 </listitem>
660 </varlistentry>
661
662 <varlistentry id="qemu-io">
663 <term><command>qemu-io</command></term>
664 <listitem>
665 <para>
666 is a diagnostic and manipulation program for (virtual) memory
667 media. It is still at an early stage of development
668 </para>
669 <indexterm zone="qemu qemu-io">
670 <primary sortas="b-qemu-io">qemu-io</primary>
671 </indexterm>
672 </listitem>
673 </varlistentry>
674
675 <varlistentry id="qemu-nbd">
676 <term><command>qemu-nbd</command></term>
677 <listitem>
678 <para>
679 exports Qemu disk images using the QEMU Disk Network Block
680 Device (NBD) protocol
681 </para>
682 <indexterm zone="qemu qemu-nbd">
683 <primary sortas="b-qemu-nbd">qemu-nbd</primary>
684 </indexterm>
685 </listitem>
686 </varlistentry>
687
688 <varlistentry id="qemu-system">
689 <term><command>qemu-system-x86_64</command></term>
690 <listitem>
691 <para>
692 is the QEMU PC System emulator
693 </para>
694 <indexterm zone="qemu qemu-system">
695 <primary sortas="b-qemu-system">qemu-system-x86_64</primary>
696 </indexterm>
697 </listitem>
698 </varlistentry>
699
700 <varlistentry id="virtfs-proxy-helper">
701 <term><command>virtfs-proxy-helper</command></term>
702 <listitem>
703 <para>
704 creates a socket pair or a named socket. QEMU and proxy helper
705 communicate using this socket. QEMU proxy fs driver sends
706 filesystem request to proxy helper and receives the response
707 from it
708 </para>
709 <indexterm zone="qemu virtfs-proxy-helper">
710 <primary sortas="b-virtfs-proxy-helper">virtfs-proxy-helper</primary>
711 </indexterm>
712 </listitem>
713 </varlistentry>
714
715 </variablelist>
716
717 </sect2>
718
719</sect1>
Note: See TracBrowser for help on using the repository browser.