9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Jacob Moody <moody@posixcafe.org>
To: 9front@9front.org
Subject: Re: [9front] First time 9front start with qemu
Date: Mon, 26 Feb 2024 12:54:36 -0600	[thread overview]
Message-ID: <257affa7-de99-49eb-b41a-130566a7f60b@posixcafe.org> (raw)
In-Reply-To: <CAK9C857h27DhxZCDX7GUbH4TP9WqG+XaX=P5JnrxH5OkqOuH7w@mail.gmail.com>

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

  reply	other threads:[~2024-02-26 18:55 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-26 18:20 Bengt Kleberg
2024-02-26 18:54 ` Jacob Moody [this message]
2024-03-20 10:45   ` Bengt Kleberg
2024-03-20 14:51     ` Jacob Moody
2024-03-20 15:07       ` Bengt Kleberg
2024-03-20 15:14         ` Jacob Moody
2024-03-20 15:17           ` Michael Misch
2024-03-21  1:41             ` Frank D. Engel, Jr.
2024-03-20 16:00           ` Bengt Kleberg
2024-03-20 16:11             ` Jacob Moody
2024-03-21 11:14               ` Bengt Kleberg
2024-03-23 15:51                 ` Bengt Kleberg
2024-03-26  1:38                   ` Jacob Moody
2024-03-26 14:56                     ` Bengt Kleberg
2024-03-23 16:04               ` Bengt Kleberg
2024-03-23 20:00                 ` hiro
2024-03-24 21:06                 ` Pablo Tesari
2024-04-05  7:05                   ` Bengt Kleberg
2024-03-26  1:54                 ` Jacob Moody
2024-03-26 14:59                   ` Bengt Kleberg
2024-02-26 19:55 ` ori
2024-02-26 21:29   ` Bengt Kleberg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=257affa7-de99-49eb-b41a-130566a7f60b@posixcafe.org \
    --to=moody@posixcafe.org \
    --cc=9front@9front.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).