From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <9front-bounces@9front.inri.net> X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.6 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,HTML_MESSAGE,MAILING_LIST_MULTI, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 Received: from 9front.inri.net (9front.inri.net [168.235.81.73]) by inbox.vuxu.org (Postfix) with ESMTP id 53FE6232B5 for ; Sat, 23 Mar 2024 16:52:41 +0100 (CET) Received: from mail-wr1-f46.google.com ([209.85.221.46]) by 9front; Sat Mar 23 11:51:29 -0400 2024 Received: by mail-wr1-f46.google.com with SMTP id ffacd0b85a97d-33ddd1624beso1878677f8f.1 for <9front@9front.org>; Sat, 23 Mar 2024 08:51:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=travelping-com.20230601.gappssmtp.com; s=20230601; t=1711209086; x=1711813886; darn=9front.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=lJvDObalCwe4G1Ueg2ShJhYLju1jcwsYilNOsuID8Do=; b=n7mB1CytjbBkpYdUn96f22wnk7tha43OSq7SlrW6Bf3RJxFraxiqB82Pqcue0DiWmY CQdSx1Ilkk8wvRDTPz9fYof0uA1cKg+BboWal8lWyaZtaXHOGIxWJJXsW8wJwm9y4yt3 /wHyJ1P7txNDWEjuhv1t43NKO+D3a5JL9+EL3cgBgc/pBtg0+3oHKvgOZylI77PdUSe6 /q+9eUAlrRPkO8zYX3mKeBf31jiJ2qFREP+S49aV/uvOKH+QKKp0FzuvTx6f8BjUiRAq cL0r3xt/FEAjZy0J1Qmwgiu2nCWJLGG+JrZ3XKPaODcg0H3KB29aB2S3XflfqCf2c7Jc /LEA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1711209086; x=1711813886; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=lJvDObalCwe4G1Ueg2ShJhYLju1jcwsYilNOsuID8Do=; b=wKevjYK9+5Jiimmd2mmlfmjclVP2o0We8WHV6uK3uHow08nvY/rldDrHXhHD1jzAbu Y8uGFvjP1GLlEk2Pdz20+wCzpHwzRN+aZDP5N9dkbDkAuSLBNC1MGjPphsT51odOrJkS UNYKra6rMZCkp6W3KqgoJaZD68nbGAyIYpAVDDSUb2+FX8FDEB/6FMqzAV/X99myBXnV Q73TxabOYsnKv+F3oN334hugn5fGujrhTqhNo93nOfiFYGsGD3IUGK+zCH1S8pD7dhR9 dKG0vNiBUmHJmcVa5eUtW1RFYQ5r617lNFeSCJmXuWPysNdrp9Y6CHt+UTQ8G2BRs/1D M35A== X-Gm-Message-State: AOJu0YzYPLpiEnzGM6gbIlUAEW1OkpeUEsZfeaLzv6v9hij4TOZ1XcTF 0GrEE13yOkI2dGJQGuIqtTPsPcta4CuqiIk0bJQUO0IydZR2vllAsBlsJy41NAf7ZNgnCmHHT+m Ew/zaOH704q4vH32KFKSz/5vv2rUAAMPRQDy45GptVN1pHW1zX0J0fA== X-Google-Smtp-Source: AGHT+IHWwJzjDE3wrorOJrXqD08Jg/w83dutw6zfvKv3iJ3N5N4SCyDesEbGGwYyEJbNahC6SParMikQzeBjIGjq9dw= X-Received: by 2002:a5d:664c:0:b0:33e:6faf:7740 with SMTP id f12-20020a5d664c000000b0033e6faf7740mr1564338wrw.13.1711209085560; Sat, 23 Mar 2024 08:51:25 -0700 (PDT) MIME-Version: 1.0 References: <257affa7-de99-49eb-b41a-130566a7f60b@posixcafe.org> <2859fbcf-d2a4-4350-a0d0-fddf9c325b83@posixcafe.org> <540d0b6f-5a0d-4680-b1a9-533b8f6dd6ba@posixcafe.org> <074bf970-c82b-4603-8e75-b680161c3478@posixcafe.org> In-Reply-To: From: Bengt Kleberg Date: Sat, 23 Mar 2024 16:51:14 +0100 Message-ID: To: 9front@9front.org Content-Type: multipart/alternative; boundary="000000000000ae8395061455e986" List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: flexible realtime-based SOAP hardware cloud Subject: Re: [9front] First time 9front start with qemu Reply-To: 9front@9front.org Precedence: bulk --000000000000ae8395061455e986 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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=3Dhvf,gic-version=3D3 \ -m 4G -smp 4 \ -bios u-boot-sam460-20100605.bin \ -drive file=3D9front-10277.arm64.qcow2,if=3Dnone,id=3Ddisk \ -device virtio-blk-pci-non-transitional,drive=3Ddisk \ -serial stdio \ -nic user On Thu, 21 Mar 2024 at 12:14, Bengt Kleberg 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 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=3Dhvf,gic-version=3D3 \ > > -cpu host -m 4G -smp 4 \ > > -bios u-boot.bin \ > > -drive file=3D9front.arm64.qcow2,if=3Dnone,id=3Ddisk \ > > -device virtio-blk-pci-non-transitional,drive=3Ddisk \ > > -serial stdio > > -nic user,mode=3Dvirtio-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=C3=9Fe 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 > --=20 Bengt Kleberg --=20 Product Development --------------------------------------- enabling your networks ------------------------------------- Travelping GmbH Roentgenstra=C3=9Fe 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 --000000000000ae8395061455e986 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Greetings,

I have tried to s= tart 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 be= fore.
It could be that I have a too old u-boot.bin. To get a newe= r 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 f= in OPENSSL (which I have and use for other things).
Since the arm= 64.qcow2 is without graphics, which I want, it is not worth spending more t= ime on=C2=A09front-10277.arm64.qcow2.

Best Wishes,=
bengt

(*)
$ qemu-system-aarch= 64 -M virt-2.12,accel=3Dhvf,gic-version=3D3 \
=C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 -m 4G -smp 4 \
=C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 -bios u-boot-sam460-20100605.bin=C2=A0 \
=C2=A0=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 -drive file= =3D9front-10277.arm64.qcow2,if=3Dnone,id=3Ddisk \
=C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 -device virtio-blk-pci-non-transi= tional,drive=3Ddisk \
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 -serial stdio \
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0=C2=A0 -nic user

On Thu, 21 Mar 2024 at 12:14, Bengt Kleb= erg <bengt.kleberg@trave= lping.com> wrote:
Sorry, my mistake. I thought you meant modifying the arm64 kerne= l 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 arm= 64 VM, but I would need to know a place to start for that. Which I do not.<= br> > >
>
> I gave you the example qemu command for running the arm64 image previo= usly in this thread:
>
>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0qemu-system-aarch64 -M virt-2.12,acce= l=3Dhvf,gic-version=3D3 \
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0-cpu host= -m 4G -smp 4 \
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0-bios u-b= oot.bin \
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0-drive fi= le=3D9front.arm64.qcow2,if=3Dnone,id=3Ddisk \
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0-device v= irtio-blk-pci-non-transitional,drive=3Ddisk \
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0-serial s= tdio
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0-nic user= ,mode=3Dvirtio-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=C3=9Fe 13
39108 Magdeburg
Germany

phone: +49 391 660 98560
mail: info@travelp= ing.com
website: https://www.travelping.com/

Company registration: Amtsgericht Stendal
Managing Director: Holger Winkelmann
Reg. No.: HRB 10578
VAT ID: DE236673780


--

Bengt=C2=A0Klebe= rg

--= =C2=A0

Pro= duct Development


=

----= -----------------------------------=C2=A0enabling your networks -----= --------------------------------

Travelping GmbH=C2=A0
Roentgenstra= =C3=9Fe 13
39108 Magdeburg
Ge= rmany

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

=C2=A0

--000000000000ae8395061455e986--