From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=0.2 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.4 Received: (qmail 25773 invoked from network); 7 Jan 2024 15:49:02 -0000 Received: from 9front.inri.net (168.235.81.73) by inbox.vuxu.org with ESMTPUTF8; 7 Jan 2024 15:49:02 -0000 Received: from mail.cosarara.me ([159.69.205.102]) by 9front; Sun Jan 7 10:47:41 -0500 2024 Received: from [IPV6:2a0c:5a84:e700:a900:77a0:3e36:e2a1:e60] (unknown [IPv6:2a0c:5a84:e700:a900:77a0:3e36:e2a1:e60]) by mail.cosarara.me (Postfix) with ESMTPSA id 45E14130CE for <9front@9front.org>; Sun, 7 Jan 2024 16:47:38 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cosarara.me; s=20200226; t=1704642458; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=zg8IC2f5thHNe4E7Yz0zcLDRH8Y+VcYgIfJgz4vHYG0=; b=RIzqzeCchcagpLdouzPNBjp96S+FHozof8QXp2FtEtRQ9BaK/08D+PKAqXmSIhrAy8dDld CGG6v5AjLEfaiBUg0/0XfrPLkeTXah2TnpGNNSjwCvKXY4SiYy3PZr4NAKX0JzHC7k7LxT r4VlBL6N5UA+SCNiTRn+aWB9i8cPY5I= Message-ID: Date: Sun, 7 Jan 2024 16:47:37 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Content-Language: en-US To: 9front@9front.org References: <515bcf9c-352e-4f2b-b0d9-86c26171fa8f@cosarara.me> <6479cfe7-95ee-4f75-ba98-a3ff48879b61@posixcafe.org> From: cosarara In-Reply-To: <6479cfe7-95ee-4f75-ba98-a3ff48879b61@posixcafe.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: realtime-java callback HTTP realtime element interface Subject: Re: [9front] qemu kernel for arm64, detected memory Reply-To: 9front@9front.org Precedence: bulk On 7/1/24 15:23, Jacob Moody wrote: > This is a known issue. You can set *maxmem in plan9.ini to get it to use more memory. > > Thanks, > moody Thanks moody. It took me a while to figure it out (it's not easy to edit plan9.ini when its contents make the kernel panic!), so I'm leaving this extra info here for the next person with the same question: The value for *maxmem (the * is important) for this machine should be the number of bytes = 1GiB + . So the default is 1 * GiB + 128 * MiB = 0x48000000 for 128MiB, and for 4 GiB it should be *maxmem=0x140000000. cosa