From nobody Sat May 21 04:30:56 2022 X-Original-To: freebsd-riscv@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 69E911AE3055 for ; Sat, 21 May 2022 04:31:03 +0000 (UTC) (envelope-from lars.sonchocky-helldorf@hamburg.de) Received: from cosmopolitan.snafu.de (cosmopolitan.snafu.de [IPv6:2001:1560:3:255::151]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4L4rJ62KVYz3hdS; Sat, 21 May 2022 04:31:02 +0000 (UTC) (envelope-from lars.sonchocky-helldorf@hamburg.de) X-Trace: 507c6c6172732e736f6e63686f636b792d68656c6c646f72664068616d62757267 2e64657c39332e3233302e3136322e3231397c316e73476c552d3030303141382d 56537c31363533313037343536 Received: from cosmopolitan.snafu.de ([10.151.10.15] helo=localhost) by cosmopolitan.snafu.de with esmtpsa (Exim 4.94.2) id 1nsGlU-0001A8-VS; Sat, 21 May 2022 06:30:59 +0200 Content-Type: text/plain; charset=us-ascii List-Id: FreeBSD on the RISC-V instruction set architecture List-Archive: https://lists.freebsd.org/archives/freebsd-riscv List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-riscv@freebsd.org X-BeenThere: freebsd-riscv@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\)) Subject: [Solved] was: Re: Problem running FreeBSD/RISC-V in QEMU From: "lars.sonchocky-helldorf@hamburg.de" In-Reply-To: <40a8ac1a-ad1c-9e03-a66b-4b78b23f0d4a@FreeBSD.org> Date: Sat, 21 May 2022 06:30:56 +0200 Cc: "freebsd-riscv@freebsd.org" Content-Transfer-Encoding: quoted-printable Message-Id: References: <2FA6ED5C-4269-4033-BAF0-466FDC7EEA1C@hamburg.de> <40a8ac1a-ad1c-9e03-a66b-4b78b23f0d4a@FreeBSD.org> To: Mitchell Horne X-Mailer: Apple Mail (2.3654.120.0.1.13) X-VISP-ShouldScan: 1 X-VISP-Virus-Check: clean X-VISP-Spam-Score: -0.2 (/) X-VISP-Spam-Report: This message has been scanned on "cosmopolitan.snafu.de" to identify if it is considered spam or not. Contact the support hotline for details. Content analysis details: (-0.2 points) pts rule name description ---- ---------------------- -------------------------------------------------- 0.5 JMQ_SPF_NEUTRAL ASKDNS: SPF set to ?all [hamburg.de TXT:v=spf1 include:_spf1.snafu.de] [include:spf.crsend.com ?all] -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP 0.1 POISEN_SPAM_PILL_3 BODY: random spam to be learned in bayes 0.1 POISEN_SPAM_PILL_1 RAW: random spam to be learned in bayes 0.0 KAM_DMARC_STATUS Test Rule for DKIM or SPF Failure with Strict Alignment -0.0 T_SCC_BODY_TEXT_LINE No description available. 0.1 POISEN_SPAM_PILL Meta: its spam X-VISP-Spam-Max-Score: +++++ X-SA-Exim-Connect-IP: 93.230.162.219 X-SA-Exim-Mail-From: lars.sonchocky-helldorf@hamburg.de X-SA-Exim-Scanned: No (on cosmopolitan.snafu.de); SAEximRunCond expanded to false X-Rspamd-Queue-Id: 4L4rJ62KVYz3hdS X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of lars.sonchocky-helldorf@hamburg.de designates 2001:1560:3:255::151 as permitted sender) smtp.mailfrom=lars.sonchocky-helldorf@hamburg.de X-Spamd-Result: default: False [-1.90 / 15.00]; TO_DN_EQ_ADDR_SOME(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; FROM_DN_EQ_ADDR(1.00)[]; TO_DN_SOME(0.00)[]; MV_CASE(0.50)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; R_SPF_ALLOW(-0.20)[+ip6:2001:1560:3:255::/64]; ARC_NA(0.00)[]; DMARC_NA(0.00)[hamburg.de]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-0.999]; NEURAL_HAM_SHORT(-1.00)[-1.000]; RCPT_COUNT_TWO(0.00)[2]; MLMMJ_DEST(0.00)[freebsd-riscv]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:34171, ipnet:2001:1560::/32, country:DE]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[2001:1560:3:255::151:from] X-ThisMailContainsUnwantedMimeParts: N this old snapshot works! Fine! root@freebsd:~ # uname -a FreeBSD freebsd 14.0-CURRENT FreeBSD 14.0-CURRENT #0 = main-n255198-1907e1c07c3: Thu May 5 06:03:11 UTC 2022 = root@releng1.nyi.freebsd.org:/usr/obj/usr/src/riscv.riscv64/sys/GENERIC = riscv root@freebsd:~ #=20 run on macOS 11.6.5: MBP15:~ lars$ uname -a Darwin MBP15.local 20.6.0 Darwin Kernel Version 20.6.0: Tue Feb 22 = 21:10:41 PST 2022; root:xnu-7195.141.26~1/RELEASE_X86_64 x86_64 MBP15:~ lars$=20 using this command: qemu-system-riscv64 \ -machine virt \ -smp 2 \ -m 2G \ -nographic \ -bios /Volumes/Data/Projects/RISC-V/FreeBSD/fw_jump.elf \ -kernel /Volumes/Data/Projects/RISC-V/FreeBSD/u-boot.bin \ -drive = file=3D/Volumes/Data/Projects/RISC-V/FreeBSD/FreeBSD-14.0-CURRENT-riscv-ri= scv64-20220505-1907e1c07c3-255198.raw,format=3Draw,id=3Dhd0 \ -device virtio-blk-device,drive=3Dhd0 \ -device virtio-net-device,netdev=3Dnet0 \ -netdev user,id=3Dnet0,ipv6=3Doff,hostfwd=3Dtcp::8022-:22 Thanks a lot! Lars > Am 20.05.2022 um 22:44 schrieb Mitchell Horne : >=20 > On 2022-05-20 8:36 a.m., lars.sonchocky-helldorf@hamburg.de wrote: >> Hi everybody, >> I am trying to run FreeBSD/RISC-V in QEMU. >> For that purpose I have installed FreeBSD/amd64 inside Virtual Box on = a macOS machine: >> FreeBSD FreeBSD14 14.0-CURRENT FreeBSD 14.0-CURRENT #0 = main-n255696-716fd348e01: Thu May 19 08:29:12 UTC 2022 = root@releng1.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC = amd64 >> and then followed those instructions: >> https://wiki.freebsd.org/riscv#Quick_Start >> The boot process is initialized but then however I get repeatedly: >> failed to allocate staging area: 9 >> here is the part where it fails, truncated, since the above message = is repeated endlessly: >> Loading kernel... >> /boot/kernel/kernel text=3D0x5a5e88 text=3D0x172c34 data=3D0xf8350 = data=3D0x1eac+0x273b9c 0x8+0x1efc360+0x8+0xf28d3 >> Loading configured modules... >> can't find '/etc/hostid' >> can't find '/boot/entropy' >> Using DTB provided by EFI at 0x87efb000. >> Kernel entry at 0xf660002e... >> Kernel args: (null) >> failed to allocate staging area: 9 >> failed to allocate staging area: 9 >> What is going wrong here? >=20 > Seems to be a bug made visible by the recent upgrade of LLVM/clang. It = was reported here: >=20 > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D264021 >=20 > If you grab the snapshot from 2 weeks ago, it might not exhibit this = problem. Otherwise, it looks like a fix is in progress. >=20 > = https://download.freebsd.org/snapshots/VM-IMAGES/14.0-CURRENT/riscv64/2022= 0505/ >=20 > Cheers, > Mitchell >=20 >> Thanks in advance and if you need more information please let me = know! >> Kind regards, >> Lars