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,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 07C5321499 for ; Sat, 23 Mar 2024 17:05:12 +0100 (CET) Received: from mail-wr1-f53.google.com ([209.85.221.53]) by 9front; Sat Mar 23 12:04:15 -0400 2024 Received: by mail-wr1-f53.google.com with SMTP id ffacd0b85a97d-33e162b1b71so2429540f8f.1 for <9front@9front.org>; Sat, 23 Mar 2024 09:04:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=travelping-com.20230601.gappssmtp.com; s=20230601; t=1711209851; x=1711814651; darn=9front.org; h=content-transfer-encoding:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=4nbXfvvH7UH/S9OWnG+NlG5BmuYu8ItLu3ymiUawCZI=; b=em5Oj93/ii/UPUzU5eqUPJXbZXJ4DCt8+ksp2HS29v2Y/hIbrMSeQj5yjnOzZN9BXz hEVjQ9+qQ+385TE94VTNhQFS3Ba/Nm5q06ClccePxrllsPZ4gtlwPHDVurTYDeXQYfp4 BSOlhv4sySAQ3UlPDzIxMa7Lyg2R0g9btdDqLPEPFR7pkPPNRaUfqG9tt4B/phMsj+c/ NpjLEqZX8HJlnTAj/8j05KYpmCjoBU83Eds/fWdIv7aYDV0t4CYJ/aSsuxynlbLr9iT5 JzkWxaykHldu8UN4o78NUKmY4CcdspEyTBPzVeLe6l1elNgdfH/i0ROGuG//zbqOEan7 MkyA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1711209851; x=1711814651; h=content-transfer-encoding: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=4nbXfvvH7UH/S9OWnG+NlG5BmuYu8ItLu3ymiUawCZI=; b=bXJyG9Fld4PnTv1pX9LK90TdAnxtdREx2KuRmPgto6YZCz+UeWECLZ46elTQVpReiZ gjoMg0LOq2gs98ht8W1IfKMHtMPSWpMPJhp7FMQHAmUn2cT8Va6xmYSRGjqZTwjkyGFX /hYzDvfRRUW3Iigk0mzKKFxCuTfem79CxTRYnV38zimtyZ3qrJoYjhlxFsWhV3XrWgzn ESBz+jSFw/Cgu5cxfx7pipBokaW51s4OSFvUSvJy/KmhdOhshEGubaszfRwsMOG03RNr /YvwtKy+Wxpb42RB+qDobeog6xBKJm5RVtxY2IPVFfpgaxqEhj5SNZnPTQEFLwoxDHSz 85GQ== X-Gm-Message-State: AOJu0YxfDzdToi4U8oNuS/hlAdwnDjiNqzmsPniKPx7i/pyWhq5S0JSr qpV9LwOVcjN7JyIVxHVNQl5beh1x+l7VNrxr0qYB1/SHtZL1rvxszxp70gjLPQNMxoA8O2Cnn3W li+4Uus+y+3Gi8hhQudki3cMYX9A8M9/OrF7QwL/gXESaJBFnlXTboA== X-Google-Smtp-Source: AGHT+IGzsG6CrlYZTPFfapuWfuMCPRfnC/p5NEhOEgFDbAiV3DeahsM+Fti5csL+Lhbt3qvK1L6NrlgZqaB3/RraBgE= X-Received: by 2002:adf:c686:0:b0:33e:d865:422 with SMTP id j6-20020adfc686000000b0033ed8650422mr1669223wrg.29.1711209851124; Sat, 23 Mar 2024 09:04:11 -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: <074bf970-c82b-4603-8e75-b680161c3478@posixcafe.org> From: Bengt Kleberg Date: Sat, 23 Mar 2024 17:04:00 +0100 Message-ID: To: 9front@9front.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: responsive high-performance WEB2.0 hardware-aware framework-scale NoSQL locator Subject: Re: [9front] First time 9front start with qemu Reply-To: 9front@9front.org Precedence: bulk Greetings, I try to get 9front running in a x86_64 VM. From https://9front.org/iso I have 9front-10277.amd64.qcow2. From http://fqa.9front.org/fqa3.html#3.3.1 I created the command $ qemu-system-x86_64 -m 1024 \ -net nic,model=3Dvirtio,macaddr=3D00:20:91:37:33:77 -net user \ -device virtio-scsi-pci,id=3Dscsi \ -drive if=3Dnone,id=3Dvd0,file=3D9front-10277.qcow2.img \ -device scsi-hd,drive=3Dvd0 This will pop-up a small window with 9front where i can select bootargs and user. Which is good. But I get an error: bind: #i: no frame buffer And then rio can not open display. I get a (rc) shell, but would like graphics. How do I add a frame buffer to either 9front-10277.qcow2.img or to the QEMU command? Best Wishes, 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 previousl= y 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, b= ut 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