| /qemu/tests/migration/aarch64/ |
| A D | Makefile | 5 all: a-b-kernel.h
7 a-b-kernel.h: aarch64.kernel
11 aarch64.kernel: aarch64.elf
14 aarch64.elf: a-b-kernel.S
18 $(RM) *.kernel *.elf
|
| /qemu/tests/migration/ppc64/ |
| A D | Makefile | 2 all: a-b-kernel.h
4 a-b-kernel.h: ppc64.kernel
8 ppc64.kernel: ppc64.elf
11 ppc64.elf: a-b-kernel.S
15 $(RM) *.kernel *.elf
|
| /qemu/docs/system/ |
| A D | linuxboot.rst | 6 This section explains how to launch a Linux kernel inside QEMU without
8 kernel testing.
14 |qemu_system| -kernel bzImage -hda rootdisk.img -append "root=/dev/hda"
16 Use ``-kernel`` to provide the Linux kernel image and ``-append`` to
17 give the kernel command line arguments. The ``-initrd`` option can be
26 |qemu_system| -kernel bzImage -hda rootdisk.img \
|
| A D | guest-loader.rst | 22 |qemu_system| -kernel ~/xen.git/xen/xen \
24 …-device guest-loader,addr=0x42000000,kernel=Image,bootargs="root=/dev/sda2 ro console=hvc0 earlypr…
27 In the above example the Xen hypervisor is loaded by the -kernel
42 -device guest-loader,addr=<addr>[,kernel=<file>,[bootargs=<args>]][,initrd=<file>]
47 ``kernel|initrd=<file>``
48 Indicates the filename of the kernel or initrd blob. Both blobs will
50 "multiboot,kernel" or "multiboot,ramdisk" as appropriate.
53 This is an optional field for kernel blobs which will pass command
|
| A D | target-openrisc.rst | 24 If you intend to boot Linux, it is possible to have a single kernel image that
26 drivers into the kernel. This is possible because QEMU will create a device tree
28 the kernel. The kernel can then use this to configure itself for the machine.
32 If you already have a system image or a kernel that works on hardware and you
37 different kernel which boots on a system that QEMU does emulate.)
|
| /qemu/docs/system/arm/ |
| A D | sabrelite.rst | 36 The SABRE Lite machine can start using the standard -kernel functionality
37 for loading a Linux kernel, U-Boot bootloader or ELF executable.
39 Running Linux kernel
43 mainline kernel that can be booted by the SABRE Lite machine, simply configure
44 the kernel using the imx_v6_v7_defconfig configuration:
59 -kernel arch/arm/boot/zImage \
87 the -kernel argument, along with an SD card image with rootfs:
93 -kernel u-boot
95 The following example shows booting Linux kernel from dhcp, and uses the
101 -nic user,tftp=/path/to/kernel/zImage \
[all …]
|
| A D | orangepi.rst | 83 simply configure the kernel using the sunxi_defconfig configuration:
101 Build the Linux kernel with:
112 -kernel /path/to/linux/arch/arm/boot/zImage \
144 argument and provide the proper root= kernel parameter:
149 -kernel /path/to/linux/arch/arm/boot/zImage \
162 Instead of providing a custom Linux kernel via the -kernel command you may also
165 argument and remove the -kernel, -append, -dbt and -initrd arguments:
176 give the following kernel parameters via U-Boot (or via -append):
192 u-boot binary to the -kernel argument:
197 -kernel /path/to/uboot/u-boot -sd disk.img
[all …]
|
| A D | bananapi_m2u.rst | 45 The Banana Pi M2U machine can start using the standard -kernel functionality
46 for loading a Linux kernel or ELF executable. Additionally, the Banana Pi M2U
54 To build a Linux mainline kernel that can be booted by the Banana Pi M2U machine,
55 simply configure the kernel using the sunxi_defconfig configuration:
62 To boot the newly build linux kernel in QEMU with the Banana Pi M2U machine, use:
67 -kernel /path/to/linux/arch/arm/boot/zImage \
74 Note that the mainline kernel does not have a root filesystem. You can choose
95 Instead of providing a custom Linux kernel via the -kernel command you may also
98 argument and remove the -kernel, -append, -dbt and -initrd arguments:
|
| /qemu/hw/core/ |
| A D | guest-loader.c | 58 if (s->kernel) { in loader_insert_platform_data()
85 char *file = s->kernel ? s->kernel : s->initrd; in guest_loader_realize()
89 if (s->kernel && s->initrd) { in guest_loader_realize()
92 } else if (!s->kernel && !s->initrd) { in guest_loader_realize()
98 } else if (s->args && !s->kernel) { in guest_loader_realize()
116 DEFINE_PROP_STRING("kernel", GuestLoaderState, kernel),
|
| /qemu/tests/multiboot/ |
| A D | run_test.sh | 26 local kernel=$1
29 printf %b "\n\n=== Running test case: $kernel $* ===\n\n" >> test.log
32 -kernel $kernel \
46 printf %b "\e[31m ?? \e[0m $kernel $* (no debugexit used, exit code $ret)\n"
49 printf %b "\e[31mFAIL\e[0m $kernel $* (exit code $ret)\n"
|
| /qemu/docs/system/ppc/ |
| A D | ppce500.rst | 62 The ``ppce500`` machine can start using the standard -kernel functionality
69 -bios -kernel payload
72 N Y kernel
77 automatically loads the kernel image specified by the -kernel parameter via
81 Running Linux kernel
85 Linux mainline kernel that can be booted by the ``ppce500`` machine in
105 -kernel vmlinux \
113 To boot the 32-bit Linux kernel:
119 -kernel vmlinux \
181 -kernel vmlinux \
[all …]
|
| /qemu/docs/system/riscv/ |
| A D | microchip-icicle-kit.rst | 34 HSS loads the second stage bootloader U-Boot from an SD card. Then a kernel
35 can be loaded from U-Boot. It also supports direct kernel booting via the
36 -kernel option along with the device tree blob via -dtb. When direct kernel
38 like U-Boot or OS kernel directly.
51 -bios -kernel -dtb payload
55 N Y Y kernel
106 second serial port. U-Boot will automatically load the Linux kernel from
112 Sometimes we just want to test booting a new kernel, and transforming the
114 use '-kernel' for direct kernel booting just like other RISC-V machines do.
117 used to boot an S-mode payload like U-Boot or OS kernel directly.
[all …]
|
| A D | sifive_u.rst | 60 for loading a Linux kernel, a VxWorks kernel, a modified U-Boot bootloader
111 Running Linux kernel
131 -kernel arch/riscv/boot/Image \
136 node in fu540-c000.dtsi in the Linux kernel,
156 -kernel arch/riscv/boot/Image \
163 fix the 32-bit boot issue for Linux kernel v5.10.
176 applications shall be used in order for kernel to boot to user space.
178 Running VxWorks kernel
203 -kernel /path/to/vxWorks \
342 -kernel /path/to/u-boot.bin
[all …]
|
| A D | virt.rst | 50 The ``virt`` machine can start using the standard -kernel functionality
51 for loading a Linux kernel, a VxWorks kernel, an S-mode U-Boot bootloader
132 Running Linux kernel
136 Linux mainline kernel that can be booted by the ``virt`` machine in
137 64-bit mode, simply configure the kernel using the defconfig configuration:
146 To boot the newly built Linux kernel in QEMU with the ``virt`` machine:
152 -kernel arch/riscv/boot/Image \
156 To build a Linux mainline kernel that can be booted by the ``virt`` machine
158 fix the 32-bit boot issue for Linux kernel v5.12.
171 applications shall be used in order for kernel to boot to user space.
[all …]
|
| /qemu/tests/tcg/xtensa/ |
| A D | test_mmu.S | 85 set_vector kernel, 1f
99 set_vector kernel, 1f
113 set_vector kernel, 1f
128 set_vector kernel, 1f
145 set_vector kernel, 3f
172 set_vector kernel, 2f
221 set_vector kernel, 0
251 set_vector kernel, 2f
287 set_vector kernel, 2f
428 set_vector kernel, 0
[all …]
|
| A D | test_load_store.S | 13 set_vector kernel, 0
33 set_vector kernel, 0
35 set_vector kernel, 2f
69 set_vector kernel, 0
90 set_vector kernel, 0
117 set_vector kernel, 0
119 set_vector kernel, 4f
159 set_vector kernel, 0
|
| A D | test_phys_mem.S | 27 set_vector kernel, 2f
43 set_vector kernel, 2f
62 set_vector kernel, 2f
83 set_vector kernel, 2f
99 set_vector kernel, 2f
118 set_vector kernel, 2f
|
| A D | test_interrupt.S | 93 set_vector kernel, 1f
115 set_vector kernel, 1f
134 set_vector kernel, 1f
153 set_vector kernel, 1f
171 set_vector kernel, 1f
197 set_vector kernel, 1f
|
| /qemu/docs/specs/ |
| A D | riscv-iommu.rst | 33 As of this writing the existing Linux kernel support `linux-v8`_, not yet merged,
35 was tested using a public Ventana Micro Systems kernel repository in
36 `ventana-linux`_. This kernel is based on `linux-v8`_ with additional patches that
37 enable features like KVM VFIO passthrough with irqbypass. Until the kernel support
38 is feature complete feel free to use the kernel available in the Ventana Micro Systems
41 The current Linux kernel support will use the IOMMU device to create IOMMU groups
46 IOMMU kernel driver behaves:
66 Another thing to notice on `linux-v8`_ and `ventana-linux`_ is that the kernel driver
68 use the riscv-iommu-pci device with the existing kernel support we need to emulate
88 .. _linux-v8: https://lore.kernel.org/linux-riscv/cover.1718388908.git.tjeznach@rivosinc.com/
|
| /qemu/docs/system/openrisc/ |
| A D | or1k-sim.rst | 17 The Or1ksim machine can be started using the ``-kernel`` and ``-initrd`` options
18 to load a Linux kernel and optional disk image.
23 -kernel vmlinux \
27 Linux guest kernel configuration
|
| A D | virt.rst | 24 The virt machine can be started using the ``-kernel`` and ``-initrd`` options
25 to load a Linux kernel and optional disk image. For example:
32 -kernel vmlinux \
36 Linux guest kernel configuration
|
| /qemu/docs/interop/ |
| A D | vhost-vdpa.rst | 14 Here is the kernel commit here
15 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=4c8cf31885f69e86be0b5…
|
| /qemu/tests/functional/qemu_test/ |
| A D | tuxruntest.py | 92 def prepare_run(self, kernel, disk, drive, dtb=None, console_index=0): argument
106 self.vm.add_args('-kernel', kernel,
153 (kernel, disk, dtb) = self.fetch_tuxrun_assets(kernel_asset, rootfs_asset,
156 self.prepare_run(kernel, disk, drive, dtb, console_index)
|
| /qemu/linux-headers/LICENSES/exceptions/ |
| A D | Linux-syscall-note | 13 NOTE! This copyright does *not* cover user programs that use kernel
15 of the kernel, and does *not* fall under the heading of "derived work".
18 kernel) is copyrighted by me and others who actually wrote it.
20 Also note that the only valid version of the GPL as far as the kernel
|
| /qemu/docs/system/i386/ |
| A D | xen.rst | 22 |qemu_system| --accel kvm,xen-version=0x40011,kernel-irqchip=split
29 |qemu_system| --accel kvm,xen-version=0x40011,kernel-irqchip=split --cpu host,+xen-vapic
95 kernel, which then unplugs the IDE and continues with the Xen PV block device.
101 |qemu_system| --accel kvm,xen-version=0x40011,kernel-irqchip=split \\
115 The Xen binary is provided as the ``-kernel`` and the guest kernel itself (or
121 |qemu_system| --accel kvm,xen-version=0x40011,kernel-irqchip=split \\
123 -display none -m 1G -kernel xen -initrd bzImage \\
131 The example above provides the guest kernel command line after a separator
132 (" ``--`` ") on the Xen command line, and does not provide the guest kernel
|