Lines Matching +full:directory +full:- +full:based
1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK
34 - `QEMU Website <https://wiki.qemu.org/Main_Page>`__\ *:* The official
37 - `Documentation <https://wiki.qemu.org/Manual>`__\ *:* The QEMU user
49 (SDK). See ":ref:`sdk-manual/intro:the qemu emulator`" section in the
56 - If you cloned the ``poky`` repository or you downloaded and
58 environment script (i.e. :ref:`structure-core-script`)::
61 $ source oe-init-build-env
63 - If you installed a cross-toolchain, you can run the script that
65 the initialization script from the default ``poky_sdk`` directory::
67 . poky_sdk/environment-setup-core2-64-poky-linux
70 pre-built kernel that will boot in QEMU. You also need the target
73 - If you have previously built an image for QEMU (e.g. ``qemux86``,
75 your :term:`Build Directory`.
77 - If you have not built an image, you can go to the
78 :yocto_dl:`machines/qemu </releases/yocto/yocto-&DISTRO;/machines/qemu/>` area and download a
79 pre-built image that matches your architecture and can be run on
82 See the ":ref:`sdk-manual/appendix-obtain:extracting the root filesystem`"
91 Based on what you provide on the command
101 - This example starts QEMU with MACHINE set to "qemux86-64".
103 :term:`Build Directory`, ``runqemu``
104 automatically finds the ``bzImage-qemux86-64.bin`` image file and
105 the ``core-image-minimal-qemux86-64-20200218002850.rootfs.ext4``
106 (assuming the current build created a ``core-image-minimal``
117 $ runqemu qemux86-64
119 - This example produces the exact same results as the previous
124 $ runqemu qemux86-64 core-image-minimal ext4
126 - This example specifies to boot an initial RAM disk image and to
133 $ runqemu qemux86-64 ramfs audio
135 - This example does not provide enough information for QEMU to
142 - This example specifies to boot a virtual machine image
144 determines the QEMU architecture (`MACHINE`) to be "qemux86-64" and
148 $ runqemu /home/scott-lenovo/vm/core-image-minimal-qemux86-64.wic.vmdk
194 environment, you can use the ``runqemu-extract-sdk`` script, which is
195 located in the ``scripts`` directory along with the ``runqemu``
198 The ``runqemu-extract-sdk`` takes a root filesystem tarball and
200 takes a file system and extracts it to a directory named
201 ``test-nfs``:
203 .. code-block:: none
205 runqemu-extract-sdk ./tmp/deploy/images/qemux86-64/core-image-sato-qemux86-64.tar.bz2 test-nfs
209 You can then also make changes to the files within ``./test-nfs`` and
213 .. code-block:: none
215 runqemu qemux86-64 ./test-nfs
222 - To start the NFS share::
224 runqemu-export-rootfs start file-system-location
226 - To stop the NFS share::
228 runqemu-export-rootfs stop file-system-location
230 - To restart the NFS share::
232 runqemu-export-rootfs restart file-system-location
237 By default, the QEMU build compiles for and targets 64-bit and x86 Intel
238 Core2 Duo processors and 32-bit x86 Intel Pentium II processors. QEMU
250 :term:`Build Directory` ``deploy/image``
251 directory. This setting specifies a ``-cpu`` option passed into QEMU in
252 the ``runqemu`` script. Running ``qemu -cpu help`` returns a list of
260 ``qemux86`` image in the emulator on an Intel-based 32-bit (x86) host
262 other hand, using the ``qemuarm`` image on the same Intel-based host can
263 be slower. But, you still achieve faithful emulation of ARM-specific
267 cross-compiler outside the emulated system. If you used ``runqemu`` to
269 system, any BitBake cross-compiling toolchain available from the build
271 ``distcc``. You can accomplish this by defining the cross-compiler
273 a suitable SDK image or the appropriate stand-alone toolchain is
281 - QEMU provides a framebuffer interface that makes standard consoles
284 - Generally, headless embedded devices have a serial port. If so,
289 - SSH servers are available in some QEMU images. The ``core-image-sato``
291 the root password disabled. The ``core-image-full-cmdline`` and
292 ``core-image-lsb`` QEMU images have OpenSSH instead of Dropbear.
294 ``scp`` commands. The ``core-image-minimal`` QEMU image, however,
297 - You can use a provided, user-space NFS server to boot the QEMU
300 tarball by using the ``runqemu-extract-sdk`` command. After
302 the extracted directory instead of a root filesystem image file.
304 ":ref:`dev-manual/qemu:running under a network file system (nfs) server`"
307 QEMU Command-Line Syntax
314 Based on what you provide on the command line, ``runqemu`` does a
321 Following is the command-line help output for the ``runqemu`` command::
323 $ runqemu --help
327 KERNEL - the kernel image file to use
328 ROOTFS - the rootfs image file or nfsroot directory to use
329 MACHINE - the machine name (optional, autodetected from KERNEL filename if unspecified)
330 Simplified QEMU command-line options can be passed with:
331 nographic - disable video console
332 serial - enable a serial console on /dev/ttyS0
333 slirp - enable user networking, no root privileges is required
334 kvm - enable KVM when running x86/x86_64 (VT-capable CPU required)
335 kvm-vhost - enable KVM with vhost when running x86/x86_64 (VT-capable CPU required)
336 publicvnc - enable a VNC server open to all hosts
337 audio - enable audio
338 [*/]ovmf* - OVMF firmware file or base name for booting with UEFI
339 tcpserial=<port> - specify tcp serial port number
340 biosdir=<dir> - specify custom bios dir
341 biosfilename=<filename> - specify bios filename
342 qemuparams=<xyz> - specify custom parameters to QEMU
343 bootparams=<xyz> - specify custom kernel parameters during boot
344 help, -h, --help: print this text
351 runqemu qemux86-64 core-image-sato ext4
352 runqemu qemux86-64 wic-image-minimal wic
353 runqemu path/to/bzImage-qemux86.bin path/to/nfsrootdir/ serial
355 runqemu qemux86 qemuparams="-m 256"
357 runqemu path/to/<image>-<machine>.wic
358 runqemu path/to/<image>-<machine>.wic.vmdk
360 ``runqemu`` Command-Line Options
372 - `QEMUARCH`: The QEMU machine architecture, which must be "qemuarm",
374 "qemux86-64".
376 - `VM`: The virtual machine image, which must be a ``.wic.vmdk``
379 strings: "qemux86-64", "qemux86", "qemuarm", "qemumips64",
382 - `ROOTFS`: A root filesystem that has one of the following filetype
387 - `KERNEL`: A kernel image, which is a ``.bin`` file. When you provide a
391 - `MACHINE`: The architecture of the QEMU machine, which must be one of
392 the following: "qemux86", "qemux86-64", "qemuarm", "qemuarm64",
395 option, ``runqemu`` tries to determine it based on other options.
397 - ``ramfs``: Indicates you are booting an initial RAM disk (initramfs)
400 - ``iso``: Indicates you are booting an ISO image, which means the
403 - ``nographic``: Disables the video console, which sets the console to
408 - ``serial``: Enables a serial console on ``/dev/ttyS0``.
410 - ``biosdir``: Establishes a custom directory for BIOS, VGA BIOS and
413 - ``biosfilename``: Establishes a custom BIOS name.
415 - ``qemuparams=\"xyz\"``: Specifies custom QEMU parameters. Use this
419 - ``bootparams=\"xyz\"``: Specifies custom boot parameters for the
422 - ``audio``: Enables audio in QEMU. The MACHINE option must be either
423 "qemux86" or "qemux86-64" in order for audio to be enabled.
427 - ``slirp``: Enables "slirp" networking, which is a different way of
431 - ``kvm``: Enables KVM when running "qemux86" or "qemux86-64" QEMU
435 - Your MACHINE must be either qemux86" or "qemux86-64".
437 - Your build host has to have the KVM modules installed, which are
440 - The build host ``/dev/kvm`` directory has to be both writable and
443 - ``kvm-vhost``: Enables KVM with VHOST support when running "qemux86"
444 or "qemux86-64" QEMU architectures. For KVM with VHOST to work, the
447 - ``kvm`` option conditions defined above must be met.
449 - Your build host has to have virtio net device, which are
450 ``/dev/vhost-net``.
452 - The build host ``/dev/vhost-net`` directory has to be either
453 readable or writable and "slirp-enabled".
455 - ``publicvnc``: Enables a VNC server open to all hosts.