Haiku R1/beta1 in Vagrant
Over the last year, I have been slowly pushing patches upstream to Vagrant introducing native Haiku support. Vagrant is an open-source tool to build and maintain portable virtual development environments. Essentially, Vagrant lets you deploy and rapidly customize a Haiku virtual machine with programmatic scripts.
Since we now have a new stable release, I have prepared some updated R1/beta1 images to play with under an official Haiku, Inc. account.
Starting Haiku under the VirtualBox provider
The example below starts up a x86_64 Haiku VM.
haiku-os/r1beta1-x86_gcc2h below for a 32-bit (BeOS ABI compatible) virtual machine..
- Create a new work directory and enter it
mkdir haiku-r1beta1 && cd haiku-r1beta1
- Create a new file names “Vagrantfile” in this path.
# -*- mode: ruby -*- # vi: set ft=ruby : Vagrant.configure("2") do |config| # For a complete reference, please see the online documentation at # https://docs.vagrantup.com. config.vm.box = "haiku-os/r1beta1-x86_64" config.vm.synced_folder ".", "/vagrant", disabled: true # Example running custom commands after startup #config.vm.provision "shell", inline: <<-SHELL # pkgman update #SHELL end
vagrant upto download startup and configure the local Haiku VM.
vagrant sshto bring up a text console within your new Haiku VM.
- Launch VirtualBox to see the VM and pull up a virtual screen.
- Debugging RISCV-64 bootloader in QEMU
- Hello from the Haiku Promotion 'Team'!
- Haiku activity report - November and December 2020
- Haiku Depot and Better Icon Handling
- Haiku activity report - October 2020
- Haiku Activity Report - September 2020
- Haiku Activity Report - August 2020
- Rust on Haiku: the Case of the Disappearing Deceased Threads
- GSoC2020 Final Report: Input Preferences
- GSoC 2020 Final Report: Improving and Extending Services Kit