We don't have to carry around a lot of devices we can have a powerful computer and emulate the rest.
Virtualisation is such a handy technology. Ok, that's it, enjoy playing with your VM. Your prompt should be displayed in red and will make you realise that you are in the raspberry VM. Create a file called startBusterVM.sh and add the following content: So let's create a small bash script to bring our VM up. We could run that command every time, but it's a long command, and if we want to tweak something, it becomes messy. -nographic - QEMU supports graphic mode, but we are going to run it just using the command-line, so we are specifying just to use the command line and forego all the graphic window support.First, specify where to find the root directory, and panic=1, just sets the delay to wait after a kernel panic to reboot (You can omit this last parameter if you like). -append 'root=/dev/sda2 panic=1' - Send these parameters to the kernel.qemu-rpi-kernel/kernel-qemu-4.19.50-buster - Use the file as the kernel. qemu-rpi-kernel/versatile-pb.dtb - Specify the Device Tree Blob file. -net user,hostfwd=tcp::5022-:22 - We are mapping the ssh port (22) to the local port 5022, so we can later just ssh -p5022 localhost and access the VM.-net nic - Creates a network interface.raspbian-buster-lite.img - We tell QEMU to use the image file as the hard drive. -m 256 - specify the machine memory to be 256Mb.-cpu arm1176 - specify the CPU we are going to use as arm1176.
-M versatilepb - specify the machine type versatilepb.Let's break it apart and understand what we are doing (some options are self-explanatory): qemu-rpi-kernel/kernel-qemu-4.19.50-buster \ -append 'root=/dev/sda2 panic=1' \ -no-reboot \ -nographic qemu-rpi-kernel/versatile-pb.dtb \ -kernel. raspbian-buster-lite.img \ -net nic, \ -net user,hostfwd =tcp::5022-:22 \ -dtb. $ qemu-system-arm \ -M versatilepb \ -cpu arm1176 \ -m 256 \ -hda.
0 kommentar(er)
