Re: [9front] First time 9front start with qemu

[Bengt Kleberg <bengt.kleberg@travelping.com>]

Sorry about the delay. My spam filter keeps hiding 9front list emails.
And then there was Easter.

Thank you all for the help. Once I switched to x86 QEMU it was easy to
get a system up using the QCOW2 image.

Due to unknown reasons acme has a problem with mouse chording, but
9term chords correctly. Strange.
I have forgotten how to use sam and would prefer to stay with acme. If
drawterm is the only option I will try to use it.

Best Wishes,
bengt

On Sun, 24 Mar 2024 at 22:07, Pablo Tesari <pablotesari@gmail.com> wrote:
>
> 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



-- 

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