<Eighth_Doctor>
neil: if you're trying to DM me, it doesn't seem to be working
<neil>
Eighth_Doctor: oh, weird. thanks for letting me know lol
zsun has quit [Quit: Leaving.]
takuma has joined #fedora-riscv
jcajka has quit [Quit: Leaving]
<davidlt[m]>
rwmjones: is there a way to force virt-builder to use TMPDIR?
<davidlt[m]>
Ah, I executed command with sudo this time ..
<davidlt[m]>
My mistake
<davidlt[m]>
I need to make sure future laptop has 2TB drives to avoid running out of free space while playing with large disk images.
<davidlt[m]>
I have added SiFive Unmatched disk images (MMC and NVMe [i.e. no firmware partitions]) into virt-builder.
<davidlt[m]>
I tried adding firmware raw images, but virt-builder is not designed for non-OS based operation. It didn't like it.
mikepetullo[m] has joined #fedora-riscv
<mikepetullo[m]>
I have been using QEMU to run Fedora-Minimal-Rawhide-20200108.n.0-fw_payload-uboot-qemu-virt-smode.elf and Fedora-Minimal-Rawhide-20200108.n.0-sda.raw.xz from https://dl.fedoraproject.org/pub/alt/risc-v/repo/virt-builder-images/images/. I would like to do the same using the recently-published Fedora 37 images. The newer images seem to capture a machine differently, as there is no longer a separate .elf/kernel file. Does anyone
<mikepetullo[m]>
have a QEMU command line that will work with the Fedora 37 images?
<davidlt[m]>
mike.petullo: I don't have yet QEMU/libvirt instructions for these disk images.
<mikepetullo[m]>
How do you run the images?
<davidlt[m]>
Currently with QEMU 7.1.0 my current attempts failed (while jumping the kernel from firmware things explode).
<davidlt[m]>
I want to test pflash support in QEMU 7.2.0 for these images.
iooi has quit [Read error: Connection reset by peer]
iooi has joined #fedora-riscv
<mikepetullo[m]>
davidlt: are you running the images on real hardware?
<davidlt[m]>
mikepetullo[m]: yes
<mikepetullo[m]>
RISC-V hardware is something I don't have yet.
<davidlt[m]>
The software is capable of running on QEMU/libvirt, but right know I don't have the right instructions for that. The binaries for doing things in "old way" are not built. I am trying to match virt machines to work in a similar way SiFive boards work.
<davidlt[m]>
I didn't test, but you if virt machines is not required for you sifive_u machine might work (at is should work as hardware).
<davidlt[m]>
It allows providing additional image (SPI-NOR or SD) to load U-Boot from.
<davidlt[m]>
Yes. The images, repository, and virt-build entries just happened. Instruction is what's missing yet :)
<mikepetullo[m]>
Yes! I happened to check today, and noticed that they had appeared. Then I noticed how soon before I found them they did appear. I guess I was real lucky today. Thank you!
iooi has quit [Read error: Connection reset by peer]
iooi has joined #fedora-riscv
iooi has quit [Read error: Connection reset by peer]
iooi has joined #fedora-riscv
iooi has quit [Read error: Connection reset by peer]
iooi has joined #fedora-riscv
davidlt has quit [Ping timeout: 252 seconds]
iooi has quit [Ping timeout: 255 seconds]
iooi has joined #fedora-riscv
iooi has quit [Read error: Connection reset by peer]
iooi has joined #fedora-riscv
<ol>
<davidlt[m]> "I have added SiFive Unmatched..." <- Are you going to create images for VisionFive 5 or any other affordable RISC-V board?
iooi has quit [Read error: Connection reset by peer]