How to build RISC-V Fedora disk image by muself

[Jinyan]

I tried to boot fedora in qemu according to the steps given in [1].
During this process, I used the disk image named `Fedora-Developer-
Rawhide-*.raw.xz`. I am curious about what is inside and how to
compile and generate it. Where can I get the steps to generate it ?

Thank you

[1] https://fedoraproject.org/wiki/Architectures/RISC-V/Installing

[Richard W.M. Jones]

On Sun, Feb 28, 2021 at 11:43:28PM +0800, Jinyan wrote:
>  I tried to boot fedora in qemu according to the steps given in [1].
>  During this process, I used the disk image named `Fedora-Developer-
>  Rawhide-*.raw.xz`. 
They are built by Koji, and TBH I'm not precisely sure how.  I think
Koji has a way to compose disk images.  CC-ing David Abdurachmanov who
runs the Koji RISC-V instance.

>  I am curious about what is inside and how to
>  compile and generate it. Where can I get the steps to generate it ? 
If you mean how are the component RPMs built, then it's using the Koji
instance here:

http://fedora.riscv.rocks/koji/

and they are built in exactly the same way as any other Fedora
architecture, except we have our own Koji instance and RISC-V
hardware.  The sources are the regular Fedora dist-git.

>  Thank you
>  
>  [1] https://fedoraproject.org/wiki/Architectures/RISC-V/Installing 
You can use virt-install + anaconda to build your own disk image, and
that should work exactly the same as for any other architecture
(except for adjusting paths to point to the RISC-V repos rather than
the normal Fedora ones).  In fact there are instructions on the page
linked above for using virt-install.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
libguestfs lets you edit virtual machines.  Supports shell scripting,
bindings from many languages.  http://libguestfs.org

[Takayuki Nagata]

I am not sure how the image is actually built, but I have tried to
build an image with appliance-creator on a RISC-V VM, and the built
image is bootable. In my case:

    # dnf install appliance-tools
    # wget
http://fedora.riscv.rocks:3000/davidlt/fedora-riscv-kickstarts/raw/branch...
    # vi fedora-riscv64-minimal-rawhide.ks
    (enable repo and edit something to prevent errors by the following commend.)
    # appliance-creator -n ThinCrust -c
fedora-riscv64-minimal-rawhide.ks --cache ./cache/

Then I have gotten ThinCrust/ThinCrust-sda.raw.xz file.

I have referred the following URLs to get the above steps.

    http://fedora.riscv.rocks/koji/taskinfo?taskID=320958
    https://fedoraproject.org/wiki/Features/ApplianceTools
    https://pagure.io/appliance-tools

Takayuki Nagata

2021年3月1日(月) 2:57 Richard W.M. Jones <rjones(a)redhat.com&gt;:
>  On Sun, Feb 28, 2021 at 11:43:28PM +0800, Jinyan wrote:
>  > I tried to boot fedora in qemu according to the steps given in [1].
>  > During this process, I used the disk image named `Fedora-Developer-
>  > Rawhide-*.raw.xz`.
>
>  They are built by Koji, and TBH I'm not precisely sure how.  I think
>  Koji has a way to compose disk images.  CC-ing David Abdurachmanov who
>  runs the Koji RISC-V instance.
>
>  > I am curious about what is inside and how to
>  > compile and generate it. Where can I get the steps to generate it ?
>
>  If you mean how are the component RPMs built, then it's using the Koji
>  instance here:
>
>  http://fedora.riscv.rocks/koji/
>
>  and they are built in exactly the same way as any other Fedora
>  architecture, except we have our own Koji instance and RISC-V
>  hardware.  The sources are the regular Fedora dist-git.
>
>  > Thank you
>  >
>  > [1] https://fedoraproject.org/wiki/Architectures/RISC-V/Installing
>
>  You can use virt-install + anaconda to build your own disk image, and
>  that should work exactly the same as for any other architecture
>  (except for adjusting paths to point to the RISC-V repos rather than
>  the normal Fedora ones).  In fact there are instructions on the page
>  linked above for using virt-install.
>
>  Rich.
>
>  --
>  Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
>  Read my programming and virtualization blog: http://rwmj.wordpress.com
>  libguestfs lets you edit virtual machines.  Supports shell scripting,
>  bindings from many languages.  http://libguestfs.org
>  _______________________________________________
>  devel mailing list -- devel(a)lists.fedoraproject.org
>  To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives:
> https://lists.fedoraproject.org/archives/list/[e-mail]
>  Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure

[Brian C. Lane]

On Mon, Mar 01, 2021 at 07:28:49PM +0900, Takayuki Nagata wrote:
>  I am not sure how the image is actually built, but I have tried to
>  build an image with appliance-creator on a RISC-V VM, and the built
>  image is bootable. In my case: 
I'm curious to know if anaconda and livemedia-creator will run in this
environment. lmc wouldn't work if you were trying to build it from a
different arch, but if it is running on RISC-V it should work, in
theory, as long as anaconda supports it.

Brian

-- 
Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart

[Richard W.M. Jones]

On Mon, Mar 01, 2021 at 11:12:25AM -0800, Brian C. Lane wrote:
>  On Mon, Mar 01, 2021 at 07:28:49PM +0900, Takayuki Nagata wrote:
>  > I am not sure how the image is actually built, but I have tried to
>  > build an image with appliance-creator on a RISC-V VM, and the built
>  > image is bootable. In my case:
>  
>  I'm curious to know if anaconda and livemedia-creator will run in this
>  environment. lmc wouldn't work if you were trying to build it from a
>  different arch, but if it is running on RISC-V it should work, in
>  theory, as long as anaconda supports it. 
Our long term aim is that Fedora/RISC-V will behave exactly as any
other architecture.  No special changes/workarounds should be
necessary.  For common things we're already there.  To try it out,
suggest setting up a VM as described here:

https://fedoraproject.org/wiki/Architectures/RISC-V/Installing

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
Fedora Windows cross-compiler. Compile Windows programs, test, and
build Windows installers. Over 100 libraries supported.
http://fedoraproject.org/wiki/MinGW

[Matthew Miller]

On Mon, Mar 01, 2021 at 09:28:40PM +0000, Richard W.M. Jones wrote:
>  > > I am not sure how the image is actually built, but I have
> tried to
>  > > build an image with appliance-creator on a RISC-V VM, and the built
>  > > image is bootable. In my case:
>  > 
>  > I'm curious to know if anaconda and livemedia-creator will run in this
>  > environment. lmc wouldn't work if you were trying to build it from a
>  > different arch, but if it is running on RISC-V it should work, in
>  > theory, as long as anaconda supports it.
>  
>  Our long term aim is that Fedora/RISC-V will behave exactly as any
>  other architecture.  No special changes/workarounds should be
>  necessary.  For common things we're already there.  To try it out,
>  suggest setting up a VM as described here: 
I really, really, really suggest focusing on either
anaconda/livemedia-creator or osbuild (aka composer, aka weldr). These are
maintained by actual active teams. appliance-creator (and omg ThinCrust --
there's a blast from the past) are at best lightly kicked down the road
whenever serious problems develop.

-- 
Matthew Miller
<mattdm(a)fedoraproject.org&gt;
Fedora Project Leader

[Florian Weimer]

* Matthew Miller:

>  I really, really, really suggest focusing on either
>  anaconda/livemedia-creator or osbuild (aka composer, aka weldr). 
Isn't the original weldr gone (as in, last commit in mid-2018)?  And
it's lorax once more?

Thanks,
Florian

[Brian C. Lane]

On Tue, Mar 02, 2021 at 08:40:35AM +0100, Florian Weimer wrote:
>  * Matthew Miller:
>  
>  > I really, really, really suggest focusing on either
>  > anaconda/livemedia-creator or osbuild (aka composer, aka weldr).
>  
>  Isn't the original weldr gone (as in, last commit in mid-2018)?  And
>  it's lorax once more? 
weldr evolved into osbuild-composer and image-builder (the cockpit UI).
livemedia-creator continues to exist as part of the lorax project.

Brian
-- 
Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart

[David Abdurachmanov]

On Tue, Mar 2, 2021 at 4:03 AM Matthew Miller <mattdm(a)fedoraproject.org&gt; wrote:
>  On Mon, Mar 01, 2021 at 09:28:40PM +0000, Richard W.M. Jones wrote:
>  > > > I am not sure how the image is actually built, but I have tried to
>  > > > build an image with appliance-creator on a RISC-V VM, and the built
>  > > > image is bootable. In my case:
>  > >
>  > > I'm curious to know if anaconda and livemedia-creator will run in this
>  > > environment. lmc wouldn't work if you were trying to build it from a
>  > > different arch, but if it is running on RISC-V it should work, in
>  > > theory, as long as anaconda supports it.
>  >
>  > Our long term aim is that Fedora/RISC-V will behave exactly as any
>  > other architecture.  No special changes/workarounds should be
>  > necessary.  For common things we're already there.  To try it out,
>  > suggest setting up a VM as described here:
>
>  I really, really, really suggest focusing on either
>  anaconda/livemedia-creator or osbuild (aka composer, aka weldr). These are
>  maintained by actual active teams. appliance-creator (and omg ThinCrust --
>  there's a blast from the past) are at best lightly kicked down the road
>  whenever serious problems develop. 
We are currently running a very minimal setup for Fedora/RISCV, just
enough to build packages and produce disk images.

The goal is to get closer to the full blown Fedora infrastructure, but
that requires more human hours and hardware.

With new Linux-capable RISC-V hardware (SiFive Unmatched, Beagleboard
BeagleV, Microchip Icicle Kit, PINE64, Sipeed) hopefully that will
happen sooner than later.

It wouldn't surprise me that anaconda/livemedia-creator or osbuild
require no to minimal change to work, but someone needs to invest time
to attempt it.

>
> --
> Matthew Miller
> <mattdm(a)fedoraproject.org&gt;
> Fedora Project Leader
> _______________________________________________
> devel mailing list -- devel(a)lists.fedoraproject.org
> To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
https://lists.fedoraproject.org/archives/list/[e-mail]
> Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure