The second beta for Haiku R1 marks twenty months of hard work to improve Haiku’s hardware support and its overall stability. Since Beta 1, there have been 101 contributors with over 2800 code commits in total. More than 900 bugs and enhancement tickets have been resolved for this release.
Please keep in mind that this is beta-quality software, which means it is feature complete but still contains known and unknown bugs. While we are mostly confident in its stability, we cannot provide assurances against data loss.
Amazon Web Services (or, in short, AWS) is one of the most prominent cloud computing platforms that’s widely used both by private individuals and businesses alike. Since booting directly from an ISO file is not possible, we will have to create an Amazon Machine Image (AMI) based on a virtual appliance.
Go to section
Preparing for this tutorial
Disk files represent physical devices but in the form of a file. During the preparation phase, we will need to download a Haiku image file from here. Then, we will have to use VirtualBox to create a disk image that can be later converted into an AMI image file.
Haiku can be compiled for devices using the RISC-V 64bit processor architecture. (RV64GC)
Please ensure that you have obtained a copy of Haiku’s source code as described in
Get the Haiku Source Code
if you have not already done so.
Unstable
The state of the RISC-V port is early. Only the bootloader currently runs.
Building the RISCV64 compiler toolchain is quite easy using Haiku’s configure
tool.
For a complete list of flags for the configure script, see Haiku’s Configure Options
Haiku can be compiled for devices using the SPARC 64bit processor architecture.
Please ensure that you have obtained a copy of Haiku’s source code as described in
Get the Haiku Source Code
if you have not already done so.
Unstable
The state of the SPARC port is early. Only the bootloader currently runs.
Building the SPARC compiler toolchain is quite easy using Haiku’s configure
tool.
For a complete list of flags for the configure script, see Haiku’s Configure Options
Virtual instances of operating systems are perfect for all kinds of testing purposes that need to be done in a safe and isolated environment. Installing Haiku in a virtual machine is a solution for people who do not want to install it on their physical computers, but wish to become familiar with it.
This guide will describe the process of running Haiku in a virtual machine (VM) using QEMU 4.1.0 and an .ISO image file, with a Windows 10 host.
DigitalOcean is one of the most popular KVM Cloud providers that allow the end user to upload raw disk images. As they don’t allow booting from ISO, we will need to use VirtualBox or other virtualization software for installing Haiku. This guide assumes that you already have a DigitalOcean account, you’re at least partly familiar with the interface and that you have already installed Haiku in a VM. You will need to obtain a disk image (*.vdi
for VirtualBox, *.vmdk
for VMware, etc), it should reside inside the VM directory. If you don’t have Haiku set up that way just yet, check out the Virtualizing Haiku in VirtualBox guide. Remember that the hard disk size shouldn’t exceed the disk size of your droplet!
For information about Haiku's participation in GSoC this year, please see this page.
Qualifying students can apply for a Haiku project (see the list of suggested projects below).
For details about how to apply, please check out Students: How to Apply for a Haiku Idea.
The most successful Google Summer of Code projects are often those proposed by the students themselves.
The following list represents some of our ideas and wishes for the project. However, suggesting your own idea is always encouraged!
Vultr allows one to upload a custom iso on their instances.
With this, many new possibilities are open - such as setting up a buildbot, automated testing, benchmarking and more.
This task assumes you have a Vultr account and that you are aware that it will charge you for setting up and running an instance.
Preparing a direct ISO link
Vultr doesn’t allow one to upload a custom iso from a local machine. Instead, you need a direct web download link. At the moment, Haiku does not provide these, so you will have to prepare one by yourself. Don’t worry - it’s not difficult. You can use a variety of services like Amazon S3, Dropbox, etc. Please check Vultr’s documentation for more information
This guide will show you how to use Dropbox to provide a direct link for Vultr. You will need a Dropbox account for this.
For Google Code-In 2019, Vrondir created a video on how to install Haiku in KVM [79 MiB].
Virtual instances of operating systems are perfect for all kinds of testing purposes that need to be done in a safe and isolated environment. Therefore, installing Haiku in a virtual machine is an ideal solution for people who do not want to install it on their physical computers but want to become familiar with it.
In 2017, Max Levchuk created a tutorial video for VMware ESXi [5 MiB].
Virtualizing an operating system might be a good way to give it a test run, or to use it alongside your main OS. ESXi is a platform that allows easy deployment of virtual machines on baremetal servers, and setting up a Haiku ESXi VM might be a good idea if you intend to develop Haiku or applications for it.