source: postlfs/virtualization/qemu.xml@ b0a073b

11.0 11.1 11.2 11.3 12.0 12.1 kea ken/TL2024 ken/inkscape-core-mods ken/tuningfonts lazarus lxqt plabs/newcss plabs/python-mods python3.11 qt5new rahul/power-profiles-daemon renodr/vulkan-addition trunk upgradedb xry111/intltool xry111/llvm18 xry111/soup3 xry111/test-20220226 xry111/xf86-video-removal
Last change on this file since b0a073b was b0a073b, checked in by Pierre Labastie <pierre.labastie@…>, 3 years ago

qemu: prevent installing /usr/var

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