From nobody Fri Jan 16 20:30:30 2026 X-Original-To: freebsd-virtualization@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 4dtBLc4Dy1z6NqQY; Fri, 16 Jan 2026 20:30:32 +0000 (UTC) (envelope-from markj@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (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-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R12" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4dtBLc3b58z3ZBr; Fri, 16 Jan 2026 20:30:32 +0000 (UTC) (envelope-from markj@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1768595432; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=QrWfLwdcLNeCKTWyohTC7e4uqoXv688t6USFgFX5eWw=; b=yIibmCimxgJH8U71oysC8/PzgciE1/KVeuvIRYotqlhf7/XBJfExBDPHABHk58hio4Vi1U kj/4VBv1ryf6ch+uuufHDEAE44I9nqQ/UFi3wTf8P1e7BPw7mxk9TRDV31OietYX8QQmYB Y7Or1ORkUenzEf9/2lQ1lL6j0pfo3OJETbwWpAjGc0dAWEgFYLCpH9h+raGmzEfAVE8K6f GO3XwgFvBTJWgCDhj3vr0DUcbsoSWaHhQWU30Zt13gxB5rK6kDfxZrjT5/BBVgh1yavFMe Sil9ACyC30LeXMOGgHc45OJ+aNq5r447Z6p29n5M/7wmZUQhklyIT5jUyIpwTQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1768595432; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=QrWfLwdcLNeCKTWyohTC7e4uqoXv688t6USFgFX5eWw=; b=Rv2ONwBjK5USG7z60nEP4Anjbo6vdLdPJZ3nXhHnmbyxCrumEM9hkY6aqbOU706pxuPobw hdr41JoJm7GxsltOLZTzyXHkp5sl9CpS3FNmDUG+zMqSG+degeuvedFKt8ml70ZFb2xG3V 7sRdACPk9QerMmdpFicNA+afPxUdgBWs84gGCva8ZG66An+ynWsiNCXuvMR7Tx1WbGJKmM ewrwiALOT6yGbbgELDLY8OWMoeDfd/+t1290PlOYr98EE3BlA7vi6shBHvZ0e9qt+AEwiG z3ocU7JZ40n2iL27l9ZMGka1h0ZpFWpfsvOY02jeDRFg9RSbJa6sfinQlayMxQ== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1768595432; a=rsa-sha256; cv=none; b=PLX4mmbJN3EvMmG9C3HhSEybTbXbwMvZKdr7VoC0h0n1hLsu3+h1sk/W4kbi6cf44nuFAV 4y/KwhgoI6iETrgacvwoWoMNSQrC9mwztDmoh8NXYUWPB429N83m1jL7PZLYabc2D3m7gy TFoOubcwbX/5rIIJkOC9Be3wlKTitHDVNAH5jhzIfup6Sn/a8vKJSqe1wH4o8EKVWCdVCB A76uxtCUxguM8SGvkELSkKS2SkgQYPz8fXhoKR9sKUReBP1zplw0mu14PwqpZemuDcN6Ay iO0N0fkmD7WbioeWwjLlICiKG2i2iVsVimVnjf+s+aNRWxMYpZYjWXPb+aM3Bw== ARC-Authentication-Results: i=1; mx1.freebsd.org; none Received: from nuc (192-0-220-237.cpe.teksavvy.com [192.0.220.237]) (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) (Authenticated sender: markj) by smtp.freebsd.org (Postfix) with ESMTPSA id 4dtBLc16kyz18YJ; Fri, 16 Jan 2026 20:30:32 +0000 (UTC) (envelope-from markj@freebsd.org) Date: Fri, 16 Jan 2026 15:30:30 -0500 From: Mark Johnston To: Roman Bogorodskiy Cc: freebsd-virtualization@freebsd.org, freebsd-arm@freebsd.org Subject: Re: Quartz64: vmm: No vgic found Message-ID: References: List-Id: Discussion List-Archive: https://lists.freebsd.org/archives/freebsd-virtualization List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-virtualization@freebsd.org Sender: owner-freebsd-virtualization@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: On Thu, Jan 15, 2026 at 06:42:10PM +0100, Roman Bogorodskiy wrote: > Hi, > > Loading of the vmm(4) module shows errors like: > > Jan 15 17:32:10 generic kernel: vmm: No vgic found > Jan 15 17:32:10 generic kernel: module_register_init: MOD_LOAD (vmm, 0xffff0000e12931f0, 0) error 19 > > The module is listed in kldstat: > > $ kldstat |grep vmm > 7 1 0xffff0000e1268000 4f000 vmm.ko > $ This is due to a bug. vmm.ko should unload itself after the error you observed above: https://reviews.freebsd.org/D54750 > But bhyve does not start: > > # bhyve -o bootrom=/usr/local/share/u-boot/u-boot-bhyve-arm64/u-boot.bin -s 1,virtio-blk,./FreeBSD-15.0-RELEASE-arm64-aarch64-ufs.raw -o console=stdio vm0 > bhyve: vm_openf: No such file or directory > # > > Host system is: > > Pine64 Quartz64 Model A > FreeBSD 15.0-RELEASE arm64 > > gic0: mem 0xfd400000-0xfd40ffff,0xfd460000-0xfd4dffff irq 12 on ofwbus0 > gic0: using for IPIs > > CPU 0: ARM Cortex-A55 r2p0 affinity: 0 0 > Cache Type = <64 byte CWG,64 byte ERG,64 byte D-cacheline,VIPT I-cache,64 byte I-cacheline> > Instruction Set Attributes 0 = > Instruction Set Attributes 1 = > Instruction Set Attributes 2 = <> > Processor Features 0 = > Processor Features 1 = > Processor Features 2 = <> > Memory Model Features 0 = > Memory Model Features 1 = > Memory Model Features 2 = <32bit CCIDX,48bit VA,IESB,UAO,CnP> > Memory Model Features 3 = <> > Memory Model Features 4 = <> > Debug Features 0 = > Debug Features 1 = <> > Auxiliary Features 0 = <> > Auxiliary Features 1 = <> > AArch32 Instruction Set Attributes 5 = > AArch32 Media and VFP Features 0 = > AArch32 Media and VFP Features 1 = > CPU 1: ARM Cortex-A55 r2p0 affinity: 1 0 > CPU 2: ARM Cortex-A55 r2p0 affinity: 2 0 > CPU 3: ARM Cortex-A55 r2p0 affinity: 3 0 > > Does the board need something in addition to GICv3 that is missing that > is needed to make vmm(4) work, or is that a configuration or vmm(4) > issue? The vgic driver is refusing to attach, apparently because we don't detect virtualization support when probing the controller. When booting from a FDT we look for an "interrupts" property to determine this, but it's not clear to me whether that's totally right. Can you share the device tree you're using with this board?