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 0FF5721460 for ; Mon, 26 Feb 2024 19:55:59 +0100 (CET) Received: from mail.posixcafe.org ([45.76.19.58]) by 9front; Mon Feb 26 13:54:38 -0500 2024 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=posixcafe.org; s=20200506; t=1708973672; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=zSFiR3g4TaXrK4X/EKHcaT74iB/ApmmBkRXrIQ1leGM=; b=g75QcdCTKBWCI1v7KpcnQoc4FiUWr7A51/MRgxLSJ+O61D3+UiAOKnTLpp4CwJVT+jHjBL jhSORKXKc9huZ7IXNicD6SY67QavjkJ6mMb2LXNiI6SPC3sVr25Z0ODzGtFa94CbdPWSZ3 P+LRPK+ZophJvoc80p6c+SAiS/JghpI= Received: from [192.168.168.200] ( [207.45.82.38]) by mail.posixcafe.org (OpenSMTPD) with ESMTPSA id 4a028878 (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO) for <9front@9front.org>; Mon, 26 Feb 2024 12:54:31 -0600 (CST) Message-ID: <257affa7-de99-49eb-b41a-130566a7f60b@posixcafe.org> Date: Mon, 26 Feb 2024 12:54:36 -0600 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Content-Language: en-US To: 9front@9front.org References: From: Jacob Moody In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: secure TOR over SQL table DOM layer Subject: Re: [9front] First time 9front start with qemu Reply-To: 9front@9front.org Precedence: bulk On 2/26/24 12:20, Bengt Kleberg wrote: > Greetings, > > If somebody that has used the new qcow2 images with qemu, could share > how it was done I would appreciate an explanation/copy of that. > > I recently read an article about 9front/plan9 and the author mentioned > it was possible to start 9front (with qemu) in just a few minutes. I > have now spent a few days and think it is time to seek help. > Given the right qcow2 file for my computer, 9front-10277.arm64.qcow2.gz from > https://9front.org/iso, I have tried to use the right qemu command, > qemu-system-aarch64, in various ways inspired by the description of > how it was done in the time of ISO files: > http://fqa.9front.org/fqa3.html#3.3.1 (Qemu) > > Mostly I have been trying variations on 3.3.1.2 Post-Installation > Booting (since I have no ISO), with some additions demanded by error > messages (-machine virt). > But I only get a new little window with qemu command line. Or I can > get the qemu command line in my original window, and nothing in the > new window (-monitor stdio). > > Best Wishes, > bengt arm64 is a bit more involved then amd64 and the documentation is not quite updated to reflect the differences yet. The original commit message has the basic template: qemu-system-aarch64 -M virt-2.12,accel=hvf,gic-version=3 \ -cpu cortex-a72 -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 This requires you to also grab your own relatively recent u-boot.bin from upstream. The cpu could also be replaced with 'host' on an arm64 host device. What particular reason do you have to use arm64? If you are new to the system I would really suggest to stick to amd64 to get your bearings first. The current arm64 qemu kernel has no graphical interface so you have to use it in conjunction with drawterm. Thanks, moody