source: postlfs/virtualization/qemu.xml@ f0e8534

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 f0e8534 was f0e8534, checked in by Bruce Dubbs <bdubbs@…>, 5 years ago

Update to qemu-2.11.1

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

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