source: postlfs/virtualization/qemu.xml@ fee79e2

10.0 10.1 11.0 8.3 8.4 9.0 9.1 basic bdubbs/svn elogind ken/refactor-virt lazarus perl-modules qt5new trunk upgradedb xry111/git-date xry111/git-date-for-trunk xry111/git-date-test
Last change on this file since fee79e2 was fee79e2, checked in by Ken Moffat <ken@…>, 4 years ago

There were current packages with external links to libssh2, change them to xrefs.

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

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