source: postlfs/virtualization/qemu.xml@ be2215e

10.0 10.1 11.0 8.4 9.0 9.1 ken/refactor-virt lazarus qt5new trunk xry111/git-date xry111/git-date-for-trunk xry111/git-date-test
Last change on this file since be2215e was be2215e, checked in by Bruce Dubbs <bdubbs@…>, 3 years ago

Tag packages in postlfs part

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