source: postlfs/virtualization/qemu.xml@ a29d9e0

10.0 10.1 11.0 11.1 11.2 8.2 8.3 8.4 9.0 9.1 basic bdubbs/svn elogind lazarus perl-modules plabs/python-mods qt5new trunk upgradedb xry111/intltool xry111/soup3 xry111/test-20220226
Last change on this file since a29d9e0 was a29d9e0, checked in by Bruce Dubbs <bdubbs@…>, 5 years ago

Fix qemu to work with glibc-2.27

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@19829 af4574ff-66df-0310-9fd7-8a98e5e911e0

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