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.5 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,HTML_MESSAGE,MAILING_LIST_MULTI 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 8B07321350 for ; Tue, 26 Mar 2024 16:01:26 +0100 (CET) Received: from mail-wr1-f43.google.com ([209.85.221.43]) by 9front; Tue Mar 26 11:00:11 -0400 2024 Received: by mail-wr1-f43.google.com with SMTP id ffacd0b85a97d-33fd8a2a407so3811068f8f.2 for <9front@9front.org>; Tue, 26 Mar 2024 08:00:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=travelping-com.20230601.gappssmtp.com; s=20230601; t=1711465208; x=1712070008; darn=9front.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=stcXhYRRaAhwto2fcn7AV5dtCOgLmUodgXKu6jvrNro=; b=mIJEaDgdGnnp4PWdkugvc72Vl1ntN+uQ2vnAvKNcsPoCPas7wxh7pWFMbbdl06QbD7 2So+pM6vflhOQMdpTRR4hnKk4S0ylgOvk8+st+RvA6sXA/kQnWP4ZNrc84lo9Zy0fPqg 6VQAmmAFixyuqhebe+pSaqDPgRMRIb85atrnSWPUtcGFbaLizCDhYVgq0FvQ+FsyLD2Z BQwVXV/bmGoAc6/2aeic9+oNU0y5nk5B277cqWg+jlJGdDf7hYFaDLrxEhoDRGPBWsFF RyoPWfdmkLjnMfMefglo1o0wMLDSNfzOZr91Dgqq2nWTJYOcrEvH0ryn4T0ZmVjLr9rT 5BYA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1711465208; x=1712070008; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=stcXhYRRaAhwto2fcn7AV5dtCOgLmUodgXKu6jvrNro=; b=vp+sBpHTJnmtXoxKhiQ4UmJGgbpqJUpT2aURn7fuKEX1oMKF/+cPHreZnklAKnDlOv HelBE0sPk2AyW+A0aX4F2VrR+HIZXqEkE0tv/ETipxbH34hRaYCEPJ+BK6REDVCK9oBJ l/FccGKbPjcT2Ifnccqc8Wxg1j9tK0qNIzCS6351JpQygweOmBahBwnh1IxDXHIgQnw2 vrluaYwJ+zEGLGZHZLdN1/Z1O3fxO2ETmMaFA5uK2XJxkkK9Cd4dkmbv7hLn9QWuceZJ RyNBMi4Zku+JjFMUNemQFpOd9VY/XMYrt5tOuOzIJXanckY1TjHXWp21Xp27CQwfCAFW rTRw== X-Gm-Message-State: AOJu0YxLpn4vPIgXRzQCKHFExTYAJRq0hu1S9V0XLsKwbop2Ap0s5zii Z05Kju2O+nC8UDfH90/fbEOCQxhEBFmeyxU/31oACUx74TyF7v+B7vN+uQSOc8oio/ik7LnA6O7 IM+7TJpFbTLCLpIAIc1ZIrcUbaYIpjjAvkcvUJ0EKesMsjN6ugJI= X-Google-Smtp-Source: AGHT+IE8+pMvk/yQfQcnaOGjUssDf0Qt2w2YgPKDbD0hQW0DDH3oRmROR/2TmWG+leWKp136upwmk76XFYCqFoTfo9s= X-Received: by 2002:adf:e751:0:b0:33e:7029:96bf with SMTP id c17-20020adfe751000000b0033e702996bfmr1208154wrn.58.1711465208208; Tue, 26 Mar 2024 08:00:08 -0700 (PDT) MIME-Version: 1.0 References: <257affa7-de99-49eb-b41a-130566a7f60b@posixcafe.org> <2859fbcf-d2a4-4350-a0d0-fddf9c325b83@posixcafe.org> <540d0b6f-5a0d-4680-b1a9-533b8f6dd6ba@posixcafe.org> <074bf970-c82b-4603-8e75-b680161c3478@posixcafe.org> In-Reply-To: From: Bengt Kleberg Date: Tue, 26 Mar 2024 15:59:57 +0100 Message-ID: To: 9front@9front.org Content-Type: multipart/alternative; boundary="000000000000c800ca0614918be1" List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: framework-oriented factory replication-based manager Subject: Re: [9front] First time 9front start with qemu Reply-To: 9front@9front.org Precedence: bulk --000000000000c800ca0614918be1 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 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=3Dvirtio,macaddr=3D00:20:91:37:33:77 -net user \ > > -device virtio-scsi-pci,id=3Dscsi \ > > -drive if=3Dnone,id=3Dvd0,file=3D9front-10277.qcow2.img \ > > -device scsi-hd,drive=3Dvd0 > > > > 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=3Dask > monitor=3Dask > mouseport=3Dask > boot > > Or you can just do as another person mentioned in this thread and use the > ISO file. > > --=20 Bengt Kleberg --=20 Product Development --------------------------------------- enabling your networks ------------------------------------- Travelping GmbH Roentgenstra=C3=9Fe 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 --000000000000c800ca0614918be1 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
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.

Bes= t Wishes,
bengt

On Tue, 26 Mar 2024 at 02:56, Jacob Mood= y <moody@posixcafe.org> wr= ote:
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 co= mmand
>
> $ qemu-system-x86_64 -m 1024 \
> -net nic,model=3Dvirtio,macaddr=3D00:20:91:37:33:77 -net user \
> -device virtio-scsi-pci,id=3Dscsi \
> -drive if=3Dnone,id=3Dvd0,file=3D9front-10277.qcow2.img \
> -device scsi-hd,drive=3Dvd0
>
> 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:
=C2=A0>
prompt then typing to following:

vgasize=3Dask
monitor=3Dask
mouseport=3Dask
boot

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



--

Bengt=C2=A0Klebe= rg

--= =C2=A0

Pro= duct Development


=

----= -----------------------------------=C2=A0enabling your networks -----= --------------------------------

Travelping GmbH=C2=A0
Roentgenstra= =C3=9Fe 13
39108 Magdeburg
Ge= rmany

phon= e: +49 391 660 98560
mail: info@travelping.com
 website: https://www.travelping.com/
Company registration: Amtsgericht Stendal=C2= =A0
Managing Director: Holger Winkelmann
 Reg. No.: HRB 10578
VAT ID: DE236673780

=C2=A0

--000000000000c800ca0614918be1--