Vagrant VS QEMU

You can give Vagrant a go (https://www.vagrantup.com). It is pretty handy for spinning up/down development VMs without even leaving your IDE.

Vagrant is a popular tool for launching virtual machines on your local desktop. https://www.vagrantup.com/

And, for the record, if you ever need to do something cross falls down on and Docker isn't suited to (eg. some of my sites are on a shared webhost that uses FreeBSD), the simplest way I've found is to use Vagrant with a script like this to run inside Vagrant to copy the project in, trigger a build, and then copy the binary out.

Have a look at vagrant to spin up VMs quickly, then use 'em to do stuff like configure a salt environment - you could incorporate cron jobs here ;)

I was building a new version of YugabyteDB vagrant box with packer and virtual box. Because we (Yugabyte) have a new preview release out.

I also suggest having a look at Vagrant (https://www.vagrantup.com/) for learning kind of work. It makes running isolated env easy and clean.

Another point to consider is how difficult is it to install the API Gateway or redeploy the gateway when changes are made. Check what installation options are offered. Most modern API Gateways can be installed in many different ways(Package based, Docker, Helm, RPM) in any environment (Linux, Windows, macOS). For example, one of the biggest advantages of Kong is its wide range of installation choices, with pre-made containers such as Docker and Vagrant so you can get a deployment running quickly.

Laravel wanted to make the entire PHP development process as seamless as possible. At the time, Laravel achieved this with Laravel Homestead, apre-packaged Vagrant box. Everything you would need would be bundled into a virtual machine, nice and neat, away from your OS. And this was how I was introduced to Vagrant. A means of packaging virtual machines into a portable format, so you could easily create local development environments. Vagrant worked by using a Vagrantfile to describe the virtual machine you would want to use, how it would be provisioned, the ports you would forward, and the filepaths you would want shared from host to guest. All of these tasks would be handled by the provider, the underlying virtual machine program itself, in my case, VirtualBox. Perhaps the one thing I liked the most about Vagrant, was the ability to provision my machine, clear down if I wanted to and have it back in a clean state for development.

The following is a pretty decent historical page about the pre-(U)EFI MBR (Master Boot Record) boot process:

https://thestarman.pcministry.com/asm/mbr/STDMBR.htm

Note that EFI/UEFI -- occurred much later in time than MBR...

Related: https://en.wikipedia.org/wiki/Master_boot_record

You might also wish to check out some emulators, most notably Bochs (https://bochs.sourceforge.io/) and QEMU (https://www.qemu.org/) because they simulate the boot process, and if you're in their debuggers, you should be able to inspect that process step by step -- but also more generally emulators for other machines/platforms/architectures (https://en.wikipedia.org/wiki/List_of_computer_system_emulat...) -- because in general, most of those emulators should simulate the given machine/platform/architecture's boot process...

It's also possible to set up a little software-only debug environent based on an emulator like QEMU (https://www.qemu.org/) using gdb etc. but I haven't personally taken it far from there - yet? :)

Qualcomm | Hyderabad, India | Full Time | ONSITE | QEMU

My team is looking to hire a software developer to help us design and extend QEMU support [1] for the Hexagon DSP [2]. We're looking for candidates who have experience coding in C, C++ or Rust* and who aren't afraid of rolling up their sleeves and poring over disassembled code. This particular architecture is a bit more challenging than most, because it's a bit unique. It's a VLIW [3], so it's a great opportunity to learn about an interesting architecture. Millions of Hexagon DSPs are out there, most are found in Snapdragon SoCs for Android phones and more!

We collaborate a lot with Open Source communities like QEMU, LLVM [4], the Linux kernel [5], and more. I love being able to work on Open Source software at my day job.

You can contact me directly (email addr is in my HN user link). If you don't have experience with QEMU - don't worry! Most of us didn't have any experience with it until recently, too.

The rest of the team you'd work with lives mostly in EU, US.

* Rust experience may serve the role well but we don’t (yet) have any product software in Rust.

[1] https://github.com/qemu/qemu/tree/master/target/hexagon

[2] https://en.wikipedia.org/wiki/Qualcomm_Hexagon

[3] https://en.wikipedia.org/wiki/Very_long_instruction_word

[4] https://foundation.llvm.org/docs/sponsors/

[5] https://www.linuxfoundation.org/our-members-are-our-superpow...

QEMU - machine emulator and virtualizer

In this post, I will step through an example setup that shows how to debug a FreeRTOS application in the Visual Studio Code (VSCode) editor using QEMU to emulate an Arm Cortex-M3 microcontroller. No actual hardware is required for this example, except a laptop or desktop as your development environment.

Your options are to use a toolchain available to you on Linux (e.g. LLVM), or to create a Windows VM and run Dev-C++ in the VM. (See https://www.virtualbox.org/wiki/Linux_Downloads or https://www.qemu.org/).

#!/usr/bin/env bash # Special thanks to: # https://github.com/Leoyzen/KVM-Opencore # https://github.com/thenickdude/KVM-Opencore/ # https://github.com/qemu/qemu/blob/master/docs/usb2.txt # # qemu-img create -f qcow2 mac_hdd_ng.img 128G # # echo 1 > /sys/module/kvm/parameters/ignore_msrs (this is required) ############################################################################ # NOTE: Tweak the "MY_OPTIONS" line in case you are having booting problems! ############################################################################ MY_OPTIONS="+ssse3,+sse4.2,+popcnt,+avx,+aes,+xsave,+xsaveopt,check" # This script works for Big Sur, Catalina, Mojave, and High Sierra. Tested with # macOS 10.15.6, macOS 10.14.6, and macOS 10.13.6. ALLOCATED_RAM="7096" # MiB CPU_SOCKETS="1" CPU_CORES="8" CPU_THREADS="8" REPO_PATH="." OVMF_DIR="." # shellcheck disable=SC2054 args=( -enable-kvm -m "$ALLOCATED_RAM" -cpu Penryn,kvm=on,vendor=GenuineIntel,+invtsc,vmware-cpuid-freq=on,"$MY_OPTIONS" -machine q35 -usb -device usb-kbd -device usb-tablet -smp "$CPU_THREADS",cores="$CPU_CORES",sockets="$CPU_SOCKETS" -device usb-ehci,id=ehci # -device usb-kbd,bus=ehci.0 # -device usb-mouse,bus=ehci.0 -device nec-usb-xhci,id=xhci -global nec-usb-xhci.msi=off # -device usb-host,vendorid=0x8086,productid=0x0808 # 2 USD USB Sound Card # -device usb-host,vendorid=0x1b3f,productid=0x2008 # Another 2 USD USB Sound Card # -device vfio-pci,host=3:00.0,bus=pcie.0 -device isa-applesmc,osk="ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc" -drive if=pflash,format=raw,readonly=on,file="$REPO_PATH/$OVMF_DIR/OVMF_CODE.fd" -drive if=pflash,format=raw,file="$REPO_PATH/$OVMF_DIR/OVMF_VARS-1024x768.fd" -smbios type=2 -device ich9-intel-hda -device hda-duplex -device ich9-ahci,id=sata -drive id=OpenCoreBoot,if=none,snapshot=on,format=qcow2,file="$REPO_PATH/OpenCore/OpenCore.qcow2" -device ide-hd,bus=sata.2,drive=OpenCoreBoot -device ide-hd,bus=sata.3,drive=InstallMedia -drive id=InstallMedia,if=none,file="$REPO_PATH/BaseSystem.img",format=raw -drive id=MacHDD,if=none,file="$REPO_PATH/mac_hdd_ng.img",format=qcow2 -device ide-hd,bus=sata.4,drive=MacHDD # -netdev tap,id=net0,ifname=tap0,script=no,downscript=no -device virtio-net-pci,netdev=net0,id=net0,mac=52:54:00:c9:18:27 -netdev user,id=net0 -device virtio-net-pci,netdev=net0,id=net0,mac=52:54:00:c9:18:27 # -netdev user,id=net0 -device vmxnet3,netdev=net0,id=net0,mac=52:54:00:c9:18:27 # Note: Use this line for High Sierra -monitor stdio -device VGA,vgamem_mb=128 ) qemu-system-x86_64 "${args[@]}"

Qualcomm | Hyderabad, India | Full Time | ONSITE | QEMU

My team is looking to hire a software developer to help us design and extend QEMU support [1] for the Hexagon DSP [2]. We're looking for candidates who have experience coding in C, C++ or Rust* and who aren't afraid of rolling up their sleeves and poring over disassembled code. This particular architecture is a bit more challenging than most, because it's a bit unique. It's a VLIW [3], so it's a great opportunity to learn about an interesting architecture. Millions of Hexagon DSPs are out there, most are found in Snapdragon SoCs for Android phones and more!

We collaborate a lot with Open Source communities like QEMU, LLVM [4], the Linux kernel [5], and more. I love being able to work on Open Source software at my day job.

You can contact me directly (email addr is in my HN user link). If you don't have experience with QEMU - don't worry! Most of us didn't have any experience with it until recently, too.

The rest of the team you'd work with lives mostly in EU, US.

* Rust experience may serve the role well but we don’t (yet) have any product software in Rust.

[1] https://github.com/qemu/qemu/tree/master/target/hexagon

[2] https://en.wikipedia.org/wiki/Qualcomm_Hexagon

[3] https://en.wikipedia.org/wiki/Very_long_instruction_word

[4] https://foundation.llvm.org/docs/sponsors/

[5] https://www.linuxfoundation.org/our-members-are-our-superpow...

Give qemu a try.

Next, you need to enable Qemu support for your Docker host instance. Qemu is a generic machine emulator and virtualiser. In simple terms, it allows your machine with one type of processor to emulate other types of processor, allowing your machine to execute scripts on different processor architectures.