Re: [9front] First time 9front start with qemu

[Bengt Kleberg <bengt.kleberg@travelping.com>]

[-- Attachment #1: Type: text/plain, Size: 3299 bytes --]

Greetings,

I have tried to start 9front-10277.arm64.qcow2 with this command(*), but it
only pop-up the new little window with qemu command line that I haver seen
so many times before.
It could be that I have a too old u-boot.bin. To get a newer I have
installed u-boot-tools, which gave me the command mkimage, but no
u-boot.bin. I cloned u-boot.git, but it fails to compile since it can not
fin OPENSSL (which I have and use for other things).
Since the arm64.qcow2 is without graphics, which I want, it is not worth
spending more time on 9front-10277.arm64.qcow2.

Best Wishes,
bengt

(*)
$ qemu-system-aarch64 -M virt-2.12,accel=hvf,gic-version=3 \
            -m 4G -smp 4 \
                -bios u-boot-sam460-20100605.bin  \
               -drive file=9front-10277.arm64.qcow2,if=none,id=disk \
                -device virtio-blk-pci-non-transitional,drive=disk \
                -serial stdio \
               -nic user

On Thu, 21 Mar 2024 at 12:14, Bengt Kleberg <bengt.kleberg@travelping.com>
wrote:

> Sorry, my mistake. I thought you meant modifying the arm64 kernel to
> get graphics working. There I need a starting point, and it might
> still prove to be above my competence.
>
> Starting arm64 kernel with QEMU seems to be expertly explained, so
> that even I can do it.
>
> bengt
>
> On Wed, 20 Mar 2024 at 17:13, Jacob Moody <moody@posixcafe.org> wrote:
> >
> > On 3/20/24 11:00, Bengt Kleberg wrote:
> > > It might be possible for me to figure out something about the arm64
> VM, but I would need to know a place to start for that. Which I do not.
> > >
> >
> > I gave you the example qemu command for running the arm64 image
> previously in this thread:
> >
> >
> >         qemu-system-aarch64 -M virt-2.12,accel=hvf,gic-version=3 \
> >                 -cpu host -m 4G -smp 4 \
> >                 -bios u-boot.bin \
> >                 -drive file=9front.arm64.qcow2,if=none,id=disk \
> >                 -device virtio-blk-pci-non-transitional,drive=disk \
> >                 -serial stdio
> >                 -nic user,mode=virtio-net-pci-non-transitional
> >
> > You will need a newish u-boot.bin for this as well, as stated earlier.
> > If this is too technical for you, you can use an x86_64 VM and be fine,
> but you can't have your cake and eat it too.
> >
> > - moody
> >
>
>
> --
>
> Bengt Kleberg
>
> --
>
> Product Development
>
>
> --------------------------------------- enabling your networks
> -------------------------------------
>
> Travelping GmbH
> Roentgenstraße 13
> 39108 Magdeburg
> Germany
>
> phone: +49 391 660 98560
> mail: info@travelping.com
> website: https://www.travelping.com/
>
> Company registration: Amtsgericht Stendal
> Managing Director: Holger Winkelmann
> Reg. No.: HRB 10578
> VAT ID: DE236673780
>


-- 

Bengt Kleberg

-- 

Product Development


--------------------------------------- enabling your networks
-------------------------------------

Travelping GmbH
Roentgenstraße 13
39108 Magdeburg
Germany

phone: +49 391 660 98560
mail: info@travelping.com
website: https://www.travelping.com/
Company registration: Amtsgericht Stendal
Managing Director: Holger Winkelmann
Reg. No.: HRB 10578
VAT ID: DE236673780

[-- Attachment #2: Type: text/html, Size: 6830 bytes --]