[9front] First time 9front start with qemu

[9front] First time 9front start with qemu

[Bengt Kleberg]

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

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

[Jacob Moody]

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

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

[ori]

It would be helpful describing what those variations
are and how they failed.

	https://mikeash.com/getting_answers.html

Quoth Bengt Kleberg <bengt.kleberg@travelping.com>:
> 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

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

[Bengt Kleberg]

Thank you very much for your interest.

I will not show the failures that result in an error message that I
could understand. If those are also of interest (they will perhaps
allow for a few laughts?) I can include them, too.

All other, here following commands, inevitably open a new small black
window with a qemu prompt, or if I use,  -monitor stdio, small black
empty window. Nothing else happens.

Commands:

qemu-system-aarch64 -machine virt 9front-10277.arm64.qcow2

qemu-system-aarch64 -machine virt \
-device virtio-scsi-pci,id=scsi \
-drive if=none,id=vd0,file=9front-10277.arm64.qcow2 \
-device scsi-hd,drive=vd0

qemu-system-aarch64 -machine virt \
-device virtio-scsi-pci,id=scsi \
-drive if=none,id=vd0,file=9front-10277.arm64.qcow2 \
-device scsi-hd,drive=vd0 \
-net nic,model=virtio,macaddr=00:20:91:37:33:77 -net user

qemu-system-aarch64 -machine virt \
-device virtio-scsi-pci,id=scsi \
-drive if=none,id=vd0,file=9front-10277.arm64.qcow2 \
-device scsi-hd,drive=vd0 \
-net nic,model=virtio,macaddr=00:20:91:37:33:77 -net user \
-sdl

qemu-system-aarch64 -machine virt \
-device virtio-scsi-pci,id=scsi \
-drive if=none,id=vd0,file=9front-10277.arm64.qcow2 \
-device scsi-hd,drive=vd0 \
-net nic,model=virtio,macaddr=00:20:91:37:33:77 -net user \
-monitor stdio

On Mon, 26 Feb 2024 at 20:57, <ori@eigenstate.org> wrote:
>
> It would be helpful describing what those variations
> are and how they failed.
>
>         https://mikeash.com/getting_answers.html
>
> Quoth Bengt Kleberg <bengt.kleberg@travelping.com>:
> > 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
>


-- 

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

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

[Bengt Kleberg]

[-- Attachment #1: Type: text/plain, Size: 3292 bytes --]

Greetings and sorry about the delay in answering.
Many, but not all, 9front list-mails ended up in my spam filter. I found
them today.

Thank you for the explanation. I will try this.

Using arm64 instead of amd64 is because I found Ubuntu in x86 QEMU to be
too slow, but Fedora in arm64 QEMU is fast enough, on my computer.

You statement that arm64 qemu kernel has not graphical interface makes me
wonder.
Will I get a (rc) shell directly in the new window, provided that I get
9front to start? And no graphics program will start, eg acme?

Best Wishes,
bengt

On Mon, 26 Feb 2024 at 19:56, Jacob Moody <moody@posixcafe.org> wrote:

> 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
>


-- 

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: 6672 bytes --]

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

[Jacob Moody]

On 3/20/24 05:45, Bengt Kleberg wrote:
> Greetings and sorry about the delay in answering.
> Many, but not all, 9front list-mails ended up in my spam filter. I found them today.
> 
> Thank you for the explanation. I will try this.
> 
> Using arm64 instead of amd64 is because I found Ubuntu in x86 QEMU to be too slow, but Fedora in arm64 QEMU is fast enough, on my computer.

It would help to know what your computer is. If you have an arm64 host machine this would make sense, otherwise I am skeptical of this claim.

> 
> You statement that arm64 qemu kernel has not graphical interface makes me wonder.
> Will I get a (rc) shell directly in the new window, provided that I get 9front to start? And no graphics program will start, eg acme?

You will get an rc shell but you will not be able to start graphical programs, that is correct.
It is possible to use drawterm with this vm as a way around this limitation.

Thanks,
moody

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

[Bengt Kleberg]

Thank you for the very prompt answer.

Yes, my host is an ARM computer, Mac Mini with MacOS.

To use drawterm I would need a computer/VM with 9front, which I do not have.

Best Wishes,
bengt

On Wed, 20 Mar 2024 at 15:53, Jacob Moody <moody@posixcafe.org> wrote:
>
> On 3/20/24 05:45, Bengt Kleberg wrote:
> > Greetings and sorry about the delay in answering.
> > Many, but not all, 9front list-mails ended up in my spam filter. I found them today.
> >
> > Thank you for the explanation. I will try this.
> >
> > Using arm64 instead of amd64 is because I found Ubuntu in x86 QEMU to be too slow, but Fedora in arm64 QEMU is fast enough, on my computer.
>
> It would help to know what your computer is. If you have an arm64 host machine this would make sense, otherwise I am skeptical of this claim.
>
> >
> > You statement that arm64 qemu kernel has not graphical interface makes me wonder.
> > Will I get a (rc) shell directly in the new window, provided that I get 9front to start? And no graphics program will start, eg acme?
>
> You will get an rc shell but you will not be able to start graphical programs, that is correct.
> It is possible to use drawterm with this vm as a way around this limitation.
>
> Thanks,
> 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

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

[Jacob Moody]

On 3/20/24 10:07, Bengt Kleberg wrote:
> Thank you for the very prompt answer.
> 
> Yes, my host is an ARM computer, Mac Mini with MacOS.

In your case then it may be worth the trouble of figuring out the arm64 vm.
The kernel that is used was specifically written to work under MacOS arm64
accelerated virtualization so it should work. It is just not entirely documented.

For what it's worth I doubt that running an x86 VM would be much of an issue either,
9front is not exactly a demanding piece of software compared to a gnome desktop.

> 
> To use drawterm I would need a computer/VM with 9front, which I do not have.

This is incorrect, drawterm is a program that runs under mac/linux/windows/whatever
that acts as a terminal. This is the whole point of having a specific program for it.
If you already had a 9front system you could just rcpu and run rio.

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

[Michael Misch]

Having ran x86 on my M1, I can attest to it being perfectly usable for a Drawterm host.

> On Mar 20, 2024, at 08:14, Jacob Moody <moody@posixcafe.org> wrote:
> 
> On 3/20/24 10:07, Bengt Kleberg wrote:
>> Thank you for the very prompt answer.
>> 
>> Yes, my host is an ARM computer, Mac Mini with MacOS.
> 
> In your case then it may be worth the trouble of figuring out the arm64 vm.
> The kernel that is used was specifically written to work under MacOS arm64
> accelerated virtualization so it should work. It is just not entirely documented.
> 
> For what it's worth I doubt that running an x86 VM would be much of an issue either,
> 9front is not exactly a demanding piece of software compared to a gnome desktop.
> 
>> 
>> To use drawterm I would need a computer/VM with 9front, which I do not have.
> 
> This is incorrect, drawterm is a program that runs under mac/linux/windows/whatever
> that acts as a terminal. This is the whole point of having a specific program for it.
> If you already had a 9front system you could just rcpu and run rio.
> 
> 

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

[Bengt Kleberg]

[-- Attachment #1: Type: text/plain, Size: 1649 bytes --]

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.

Sorry that I confused drawterm and rcpu.

bengt

On Wed, 20 Mar 2024 at 16:16, Jacob Moody <moody@posixcafe.org> wrote:

> On 3/20/24 10:07, Bengt Kleberg wrote:
> > Thank you for the very prompt answer.
> >
> > Yes, my host is an ARM computer, Mac Mini with MacOS.
>
> In your case then it may be worth the trouble of figuring out the arm64 vm.
> The kernel that is used was specifically written to work under MacOS arm64
> accelerated virtualization so it should work. It is just not entirely
> documented.
>
> For what it's worth I doubt that running an x86 VM would be much of an
> issue either,
> 9front is not exactly a demanding piece of software compared to a gnome
> desktop.
>
> >
> > To use drawterm I would need a computer/VM with 9front, which I do not
> have.
>
> This is incorrect, drawterm is a program that runs under
> mac/linux/windows/whatever
> that acts as a terminal. This is the whole point of having a specific
> program for it.
> If you already had a 9front system you could just rcpu and run rio.
>
>
>

-- 

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: 4623 bytes --]

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

[Jacob Moody]

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

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

[Frank D. Engel, Jr.]

Not sure why you would do that; I was able to build a native ARM binary 
of drawterm for macOS without issue.


On 3/20/24 11:17, Michael Misch wrote:
> Having ran x86 on my M1, I can attest to it being perfectly usable for a Drawterm host.
>
>> On Mar 20, 2024, at 08:14, Jacob Moody <moody@posixcafe.org> wrote:
>>
>> On 3/20/24 10:07, Bengt Kleberg wrote:
>>> Thank you for the very prompt answer.
>>>
>>> Yes, my host is an ARM computer, Mac Mini with MacOS.
>> In your case then it may be worth the trouble of figuring out the arm64 vm.
>> The kernel that is used was specifically written to work under MacOS arm64
>> accelerated virtualization so it should work. It is just not entirely documented.
>>
>> For what it's worth I doubt that running an x86 VM would be much of an issue either,
>> 9front is not exactly a demanding piece of software compared to a gnome desktop.
>>
>>> To use drawterm I would need a computer/VM with 9front, which I do not have.
>> This is incorrect, drawterm is a program that runs under mac/linux/windows/whatever
>> that acts as a terminal. This is the whole point of having a specific program for it.
>> If you already had a 9front system you could just rcpu and run rio.
>>
>>
>

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

[Bengt Kleberg]

Sorry, my mistake. I thought you meant modifying the arm64 kernel to
get graphics working. There I need a starting point, and it might
still prove to be above my competence.

Starting arm64 kernel with QEMU seems to be expertly explained, so
that even I can do it.

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

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

[Bengt Kleberg]

[-- Attachment #1: Type: text/plain, Size: 3299 bytes --]

Greetings,

I have tried to start 9front-10277.arm64.qcow2 with this command(*), but it
only pop-up the new little window with qemu command line that I haver seen
so many times before.
It could be that I have a too old u-boot.bin. To get a newer I have
installed u-boot-tools, which gave me the command mkimage, but no
u-boot.bin. I cloned u-boot.git, but it fails to compile since it can not
fin OPENSSL (which I have and use for other things).
Since the arm64.qcow2 is without graphics, which I want, it is not worth
spending more time on 9front-10277.arm64.qcow2.

Best Wishes,
bengt

(*)
$ qemu-system-aarch64 -M virt-2.12,accel=hvf,gic-version=3 \
            -m 4G -smp 4 \
                -bios u-boot-sam460-20100605.bin  \
               -drive file=9front-10277.arm64.qcow2,if=none,id=disk \
                -device virtio-blk-pci-non-transitional,drive=disk \
                -serial stdio \
               -nic user

On Thu, 21 Mar 2024 at 12:14, Bengt Kleberg <bengt.kleberg@travelping.com>
wrote:

> Sorry, my mistake. I thought you meant modifying the arm64 kernel to
> get graphics working. There I need a starting point, and it might
> still prove to be above my competence.
>
> Starting arm64 kernel with QEMU seems to be expertly explained, so
> that even I can do it.
>
> 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

[-- Attachment #2: Type: text/html, Size: 6830 bytes --]

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

[Bengt Kleberg]

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

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

[hiro]

what is your reason to oppose drawterm for graphics? it is so much
better integrated and support fancy stuff like copy&paste, window
resize, proper mouse and keyboard support.

 i highly recommend it. in a virtualised environment i see no reason
to use anything but drawterm (apart from some initial bootstrapping
stuff that people might be more used to doing in a graphical
environment).

On Sat, Mar 23, 2024 at 5:04 PM 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

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

[Pablo Tesari]

[-- 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 --]

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

[Jacob Moody]

On 3/23/24 10:51, Bengt Kleberg wrote:
> Greetings,
> 
> I have tried to start 9front-10277.arm64.qcow2 with this command(*), but it only pop-up the new little window with qemu command line that I haver seen so many times before.
> It could be that I have a too old u-boot.bin. To get a newer I have installed u-boot-tools, which gave me the command mkimage, but no u-boot.bin. I cloned u-boot.git, but it fails to compile since it can not fin OPENSSL (which I have and use for other things).
> Since the arm64.qcow2 is without graphics, which I want, it is not worth spending more time on 9front-10277.arm64.qcow2.

Yes looks like your u-boot.bin is too old. I don't use a mac so I can't suggest what to do to fix
your issue with compiling it.

As stated multiple times by myself and by some others here you may use the arm64 virtual machine in combination
with drawterm to provide a graphical interface.

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

[Jacob Moody]

On 3/23/24 11:04, Bengt Kleberg 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?

The amd64 qcow2 does not configure a graphical interface by default.
You can change this by changing values in the plan9.ini during boot.
Those would be. You can do this by pressing keys while it boots until
you get dropped at a:
 >
prompt then typing to following:

vgasize=ask
monitor=ask
mouseport=ask
boot

Or you can just do as another person mentioned in this thread and use the ISO file.

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

[Bengt Kleberg]

[-- Attachment #1: Type: text/plain, Size: 1856 bytes --]

Thank you for the drawterm suggestion. It continues to be a possible
alternative, if I fail to get 9front graphics working directly.
But I would first have to get 9front without graphics working, and then
start on drawterm.
Since the x86 alternative already has most of graphics out-of-the-box, I
consider it to be a better starting point.

Best Wishes,
bengt

On Tue, 26 Mar 2024 at 02:40, Jacob Moody <moody@posixcafe.org> wrote:

> On 3/23/24 10:51, Bengt Kleberg wrote:
> > Greetings,
> >
> > I have tried to start 9front-10277.arm64.qcow2 with this command(*), but
> it only pop-up the new little window with qemu command line that I haver
> seen so many times before.
> > It could be that I have a too old u-boot.bin. To get a newer I have
> installed u-boot-tools, which gave me the command mkimage, but no
> u-boot.bin. I cloned u-boot.git, but it fails to compile since it can not
> fin OPENSSL (which I have and use for other things).
> > Since the arm64.qcow2 is without graphics, which I want, it is not worth
> spending more time on 9front-10277.arm64.qcow2.
>
> Yes looks like your u-boot.bin is too old. I don't use a mac so I can't
> suggest what to do to fix
> your issue with compiling it.
>
> As stated multiple times by myself and by some others here you may use the
> arm64 virtual machine in combination
> with drawterm to provide a graphical interface.
>
>

-- 

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: 4814 bytes --]

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

[Bengt Kleberg]

[-- Attachment #1: Type: text/plain, Size: 1984 bytes --]

Thank you for the explanation about the boot program. It worked.

I will try to modify plan9.ini so that I do not have to enter the commands
manually.

Best Wishes,
bengt

On Tue, 26 Mar 2024 at 02:56, Jacob Moody <moody@posixcafe.org> wrote:

> On 3/23/24 11:04, Bengt Kleberg 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?
>
> The amd64 qcow2 does not configure a graphical interface by default.
> You can change this by changing values in the plan9.ini during boot.
> Those would be. You can do this by pressing keys while it boots until
> you get dropped at a:
>  >
> prompt then typing to following:
>
> vgasize=ask
> monitor=ask
> mouseport=ask
> boot
>
> Or you can just do as another person mentioned in this thread and use the
> ISO file.
>
>

-- 

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: 5226 bytes --]

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

[Bengt Kleberg]

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