From: Pablo Tesari <pablotesari@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] First time 9front start with qemu
Date: Sun, 24 Mar 2024 18:06:24 -0300 [thread overview]
Message-ID: <CALS0JdFSrJQc4ZPvVbZxiJu5RyQAc_rHKQ2q-cwgU1wwGiz-UA@mail.gmail.com> (raw)
In-Reply-To: <CAK9C8575UpiEQsMzyf+vrOrhRt-_4PCmXPN93bs+T4vVwudE2A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2684 bytes --]
Have you tried installing it yourself from the iso ?
qemu-system-x86_64 -enable-kvm \
-boot d -cdrom <path_to_iso> \
-drive file=<path_to_disk_img>
I think that should be enough to install it and then you can use your
command to boot it from disk.
Saludos
Pablo
On Sat, 23 Mar 2024 at 13:05, Bengt Kleberg <bengt.kleberg@travelping.com>
wrote:
> 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=virtio,macaddr=00:20:91:37:33:77 -net user \
> -device virtio-scsi-pci,id=scsi \
> -drive if=none,id=vd0,file=9front-10277.qcow2.img \
> -device scsi-hd,drive=vd0
>
> 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 <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
>
[-- Attachment #2: Type: text/html, Size: 3727 bytes --]
next prev parent reply other threads:[~2024-03-24 21:07 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
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 [this message]
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=CALS0JdFSrJQc4ZPvVbZxiJu5RyQAc_rHKQ2q-cwgU1wwGiz-UA@mail.gmail.com \
--to=pablotesari@gmail.com \
--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).