Download the latest disk image
Go to this link for the nightly builds and select the most recent (top) build. Look for the -sda.raw.xz
file and download it. It will usually be quite large, around 200-300 MB.
Uncompress it:
$ unxz Fedora-Developer-Rawhide-xxxx.n.0-sda.raw.xz
Root password
riscv
Boot under TinyEMU (RISCVEMU)
RISCVEMU recently (2018-09-23) was renamed to TinyEMU (https://bellard.org/tinyemu/).
TinyEMU allow booting Fedora disk images in TUI and GUI modes. You can experiment using JSLinux (no need to download/compile/etc) here: https://bellard.org/jslinux/
Below are instructions how to boot Fedora into X11/Fluxbox GUI mode.
Step 1. Compile TinyEMU:
wget https://bellard.org/tinyemu/tinyemu-2018-09-23.tar.gz tar xvf tinyemu-2018-09-23.tar.gz cd tinyemu-2018-09-23 make
Step 2. Setup for booting Fedora:
mkdir fedora cd fedora cp ../temu . # Download pre-built BBL with embedded kernel wget https://bellard.org/jslinux/bbl64-4.15.bin # Create configuration file for TinyEMU cat <<EOF > root-riscv64.cfg /* VM configuration file */ { version: 1, machine: "riscv64", memory_size: 1400, bios: "bbl64-4.15.bin", cmdline: "loglevel=3 console=tty0 root=/dev/vda1 rw TZ=${TZ}", drive0: { file: "Fedora-Developer-Rawhide-xxxx.n.0-sda.raw" }, eth0: { driver: "user" }, display0: { device: "simplefb", width: 1920, height: 1080, }, input_device: "virtio", } EOF # Download disk image and unpack in the same directory
Step 3. Boot it.
./temu -rw root-riscv64.cfg
We need to use -rw
if we want our changes to persist in disk image. Otherwise disk image will be loaded as read-only and all changes will not persist after reboot.
Once the system is booted login as root
with riscv
as password. Finally start X11 with Fluxbox: startx /usr/bin/startfluxbox
. To gratefully shutdown just type poweroff
into console.
The disk image also incl. awesome and i3 for testing. Dillo is available as a basic web browser (no javascript support) and pcmanfm as file manager.
Boot under qemu
You will need a very recent version of qemu. If in doubt, compile from upstream qemu sources.
Get bbl from here or compile it from source.
qemu-system-riscv64 \ -nographic \ -machine virt \ -smp 4 \ -m 2G \ -kernel bbl \ -object rng-random,filename=/dev/urandom,id=rng0 \ -device virtio-rng-device,rng=rng0 \ -append "console=ttyS0 ro root=/dev/vda1" \ -device virtio-blk-device,drive=hd0 \ -drive file=Fedora-Developer-Rawhide-xxxx.n.0-sda.raw,format=raw,id=hd0 \ -device virtio-net-device,netdev=usernet \ -netdev user,id=usernet,hostfwd=tcp::10000-:22
Boot with libvirt
Detailed instructions how to install libvirt: https://docs.fedoraproject.org/en-US/quick-docs/getting-started-with-virtualization/
Quick instructions for libvirt installation (tested on Fedora 29):
dnf group install --with-optional virtualization systemctl start libvirtd systemctl enable libvirtd
Needs libvirt ≥ 4.7.0 which is the first version with upstream RISC-V support. This is available in Fedora 29. You should be able to boot the disk image using a command similar to this:
# virt-install \ --name fedora-riscv \ --arch riscv64 \ --machine virt \ --vcpus 4 \ --memory 2048 \ --import \ --disk path=/var/lib/libvirt/images/Fedora-Developer-Rawhide-xxxx.n.0-sda.raw,bus=virtio \ --boot kernel=/var/lib/libvirt/images/bbl,kernel_args="console=ttyS0 ro root=/dev/vda1" \ --network network=default,model=virtio \ --rng device=/dev/urandom,model=virtio \ --graphics none
Note that will automatically boot you into the console. If you don't want that add --noautoconsole
option. You can later use virsh
tool to manage your VM and get to console.
Add --channel name=org.qemu.guest_agent.0
option if you want virsh shutdown <name>
to work. This requires qemu-guest-agent
to be installed in disk image (available in Developer, GNOME and Minimal disk images starting Oct 15, 2018, but not in Nano disk images).
If you want to change hostname before 1st boot install libguestfs-tools-c
and then:
virt-customize -a Fedora-Developer-Rawhide-xxxx.n.0-sda.raw --hostname fedora-riscv-mymagicbox
A quick reference of virsh
commands:
virsh list --all
- list all VMs and their statesvirsh console <name>
- connect to serial consolevirsh shutdown <name>
- power down VM (see above for more details)virsh start <name>
- power up VMvirsh undefine <name>
- remove VMvirsh net-list
- list network (useful for the next command)virsh net-dhcp-leases <network_name>
- list DHCP leases,<network_name>
most likely will bedefault
. This is useful when you want to get IPv4 and SSH to the VM.virsh domifaddr <name>
- alternative for the above two commands, only shows IPv4 for one VMvirsh reset <name>
- hard reset VMvirsh destroy <name>
hard power down of VM
If you want to use ssh user@virtualMachine
you can setup libvirt NSS module. See: https://wiki.libvirt.org/page/NSS_module
Install on the HiFive Unleashed SD card
These are instructions for the HiFive Unleashed board.
The disk image (above) is partitioned, but usually we need an unpartitioned ("naked") filesystem. There are several ways to get this, but the easiest is:
$ guestfish -a Fedora-Developer-Rawhide-xxxx.n.0-sda.raw \ run : download /dev/sda1 Fedora-Developer-Rawhide-xxxx.n.0-sda1.raw
This creates a naked ext4 filesystem called *-sda1.raw
. The naked ext4 filesystem can be copied over the second partition of the SD card.
You can also build a custom bbl+kernel+initramfs to boot directly into the SD card using these sources.
Install on the HiFive Unleashed using NBD server
Look at https://github.com/rwmjones/fedora-riscv-kernel in the sifive_u540
branch. This is quite complex to set up so it's best to ask on the #fedora-riscv
IRC channel.
Install Fedora GNOME Desktop on SiFive HiFive Unleashed + Microsemi HiFive Unleashed Expansion board
Detailed instructions are provided by Atish Patra from Western Digital Corporation (WDC). See their GitHub page for details and pictures: https://github.com/westerndigitalcorporation/RISC-V-Linux
So far two GPUs are confirmed to be working: Radeon HD 6450 and Radeon HD 5450.