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