See: Progress on running Haiku on VisionFive 2 - Development / OS - Haiku Community (haiku-os.org)
The other test images (see @X512, @kallisti5, @davidkaroly): RISCV64 - Unsupported Builds | Haiku Files (haiku-os.org)
Most likely certain nightly images may not work, so validate with the main people beforehand… 
Without a detailed log of the errors, there will be only wild guesses
~/haiku/generated.riscv64> jam -j2 -q @minimum-mmc
Starting build of type minimum …
Building Haiku Minimum Target
build-feature packages unavailable on riscv64: glu mesa fontconfig gutenprint webkit jasper qrencode_kdl tiff openexr libdvdread libdvdnav libraw libavif live555
AddHaikuImagePackages: package icu66 not available!
/boot/home/haiku/src/add-ons/kernel/bus_managers/isa/arch/riscv64/Jamfile: No such file or directory
/boot/home/haiku/src/add-ons/kernel/debugger/disasm/riscv64/Jamfile: No such file or directory
/boot/home/haiku/src/bin/debug/ltrace/arch/riscv64/Jamfile: No such file or directory
Asked for riscv target boot platform
Unknown path to handle adding to image
…patience…
…patience…
…patience…
…patience…
…patience…
…patience…
…patience…
…found 61016 target(s)…
…updating 8358 target(s)…
InitScript1 haiku.image-init-vars
C++ objects/haiku_host/x86_64/release/build/libbe/support/ZstdCompressionAlgorithm.o
InitScript1 objects/haiku/riscv64/packaging/packages_build/minimum/hpkg_-haiku_loader.hpkg/scripts/haiku.package-init-vars
…/src/kits/support/ZstdCompressionAlgorithm.cpp:17:12: fatal error: zstd.h: No such file or directory
17 | #include <zstd.h>
| ^~~~~~~~
compilation terminated.
gcc -c “…/src/kits/support/ZstdCompressionAlgorithm.cpp” -O2 -Wall -Wno-trigraphs -Wno-ctor-dtor-privacy -Woverloaded-virtual -Wpointer-arith -Wcast-align -Wsign-compare -Wno-multichar -include …/headers/build/HaikuBuildCompatibility.h -DZSTD_ENABLED -fPIC -include …/headers/build/BeOSBuildCompatibility.h -DARCH_x86_64 -D_NO_INLINE_ASM -D__NO_INLINE__ -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -DHAIKU_HOST_USE_XATTR -DHAIKU_HOST_PLATFORM_HAIKU -DHAIKU_HOST_PLATFORM_64_BIT -DHAIKU_PACKAGING_ARCH="riscv64" -iquote …/build/user_config_headers -iquote …/build/config_headers -iquote …/src/build/libbe/support -iquote objects/common/build/libbe/support -iquote objects/haiku_host/x86_64/common/build/libbe/support -iquote objects/haiku/riscv64/common/build/libbe/support -iquote …/src/kits/support -I …/headers/build/private/app -I …/headers/build/private/interface -I …/headers/build/private/shared -I …/headers/build/private/support -I …/headers/build/host/haiku_host -I …/headers/build -I …/headers/build/os -I …/headers/build/os/add-ons/registrar -I …/headers/build/os/app -I …/headers/build/os/bluetooth -I …/headers/build/os/drivers -I …/headers/build/os/kernel -I …/headers/build/os/interface -I …/headers/build/os/locale -I …/headers/build/os/storage -I …/headers/build/os/support -I …/headers/build/private -o “objects/haiku_host/x86_64/release/build/libbe/support/ZstdCompressionAlgorithm.o”
…failed C++ objects/haiku_host/x86_64/release/build/libbe/support/ZstdCompressionAlgorithm.o …
AddVariableToScript1 objects/haiku/riscv64/packaging/packages_build/minimum/hpkg_-haiku_loader.hpkg/scripts/haiku.package-init-vars
BUILD FAILURE:
…failed updating 1 target(s)…
…skipped 68 target(s)…
…updated 3 target(s)…
~/haiku/generated.riscv64>
I deleted both /haiku and /buildtools, then redownloaded everything and built the buildtools as-is. Ran jam -j2 @minimum-mmc (no -q) and got a lot further before it failed. Then ran jam -j2 -q @minimum-mmc and got only this far. Is this the first fault point or did I possibly mess things up by running jam without -q?
Run pkgman install zstd_devel in Terminal.
Thank you, X512! That did the trick! Had to remove -q in the jam command line, for it to complete successfully, but I am also happy to report that Haiku (RiscV) hrev57475 boots to the desktop in QEMU!
Now, next on my list is to figure out how to remove or add apps to the image. I’ve spent a while digging through the /haiku folder and the Jam files and such, but not seeing any direct connection. Nothing that says, “put these applications/applets/preferences in this platform image”. Or is there something I overlooked?
Aside from the default apps that come with the image you won’t be able to install anything there (I presume) because there is no buildmaster running builds for third party packages there.
You could setup haikuporter and build there yourself I think (think I saw @X512 doing something like that before).
This will show you the apps and packages usually included during the jam build process - but more info may be in the Haiku docs for riscv64. I think the packages are built during the jam process and/or prebuilt from X512’s repo.
Where is X512’s repo? I think I saw it mentioned in one thread, but don’t recall which one… or where. 
Review your build log for the downloaded riscv64 packages during the jam build - although, I don’t know if this repo was/is official…
It have RVVM and VisionFive 2 SD card boot support.
Whoa… wait a second… you say your latest revisions have VisionFive 2 SD card boot support? As in, you can now boot Haiku off of an SD card on the VisionFive 2?!? This is the one thing I’ve been wanting/waiting for, to pull the trigger on buying a VisionFive 2!
Ok, can you detail the steps I need to go through, once I get a VisionFive 2, in order to get Haiku running on the VisionFive 2? I mean, I’ve read you gotta do this and that to get the latest firmware and all whatnot. So, I want to make sure I do everything EXACTLY in the right order.
Thank you. Indeed, I was able to make the changes I wanted, looking through …/minimum.
I am also pleased to report, I’ve gotten QEMU running in Haiku now! I was using the Windows version before. However, after a few hours, I finally figured out how to get QEMU (I pronounce it “Chem-You” but maybe it could be pronounced “Keem-You”, but probably not “Queem-You”… unless you’re planning on pummeling someone, but you have an Elmer Fudd speech impediment… “You waskely wabbit… I’m gonna queem you!” 
) running.
But it functions a bit different than the Windows version. Here is my command line for it:
qemu-system-riscv64 -kernel /boot/home/Desktop/u-boot.bin -M virt -m 2048 -device ati-vga -device virtio-blk-device,drive=x0,bus=virtio-mmio-bus.0 -drive file=/boot/home/Desktop/haiku-mmc.image,if=none,format=raw,id=x0 -device usb-ehci,id=ehci -device usb-tablet -device usb-kbd -device ramfb -serial stdio
As you’ll notice, I had to tell it the path to both the u-boot.bin file as well as the haiku-mmc.image file. I think this is because I was completely unable to copy the files to where I think they would normally go in the system directory (Windows 11 protests, only slightly, asking that I give it Admin privilage to copy files). I kept being told I couldn’t put files there, as it was a read-only directory, and I could not find a way to override that. So… whatever works! 
Is there a complete guide somewhere about firmware updates (for the VisionFive 2) and what order to do things, or is it the “sitting up all night and searching the internet game” as usual ?[quote=“Luposian, post:33, topic:14369, full:true”]
Whoa… wait a second… you say your latest revisions have VisionFive 2 SD card boot support? As in, you can now boot Haiku off of an SD card on the VisionFive 2?!? This is the one thing I’ve been wanting/waiting for, to pull the trigger on buying a VisionFive 2!
Ok, can you detail the steps I need to go through, once I get a VisionFive 2, in order to get Haiku running on the VisionFive 2? I mean, I’ve read you gotta do this and that to get the latest firmware and all whatnot. So, I want to make sure I do everything EXACTLY in the right order.
[/quote]
Anyone know if GLTeapot can be made to work with Haiku (RiscV)? I’m curious as to what kind of performance (FPS) I’d get inside QEMU. Also, what is needed to get multi-core functionality in QEMU?
GLTeapot need LLVM to be compiled, that takes A LOT OF TIME on current real riscv64 hardware or virtual machine. It is not done yet.
Would a tinygl backed version work? : )
Yes. Although, I’d rather see Vullkan-related work though…
Expected ‘software’ performance (one core, CPU-only) <= 250 FPS.
You mean LLVM is not yet available (“It is not done yet.”) for Haiku (RISCV), correct? Because, if it simply took HOURS for it to compile (“A LOT OF TIME”), I wouldn’t care.