From nobody Mon Jan 19 15:16:28 2026 X-Original-To: freebsd-arm@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 4dvvDv2Mxwz6NwKh; Mon, 19 Jan 2026 15:16:31 +0000 (UTC) (envelope-from markj@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (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 4dvvDt6WWSz3mvy; Mon, 19 Jan 2026 15:16:30 +0000 (UTC) (envelope-from markj@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1768835790; 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=XKMqSk80Ef/yQGMZgQg5KTtJULKZz3c+vGevZZUcCn0=; b=OVnJlNoweDiAbebm+3ruRo5+wUZL3+c5zjhraEuZZg9dkG0PSULp0skN8KeLr4HEzSZcFI 2McLV7yuxvtU0GF1ql50zK7W2mqmIuL5qcnpgMmtPO1X/AN5KDyI6zcsnjIQJtiIl2SXvh jEkhNgQJfBzZ6SRopxWls4SDWnTPG2yZu/pKDRNnPH/Vk3zgeoePnjXUHVDztRqOj0mB90 7CevPzOjqkvZpQueriUKFf1D8ONCNgottnAwov8BrAKwtKIsxfa+aR0JWC65ysNZP7QznR Z9D7hjaG7yijt675tg07gWm5saMk796mo35OHqywLokOgqjp3TdzAgsJKO82Tw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1768835790; 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=XKMqSk80Ef/yQGMZgQg5KTtJULKZz3c+vGevZZUcCn0=; b=DV6rXmn2jgu3MCO7SV4TF2M1sHdJtr5ABf1TO0SN/a2YeaFLEE6WpEHTqgR3bsb55rop4g FIurkaMakeFkIs4bFQ8A2/NIMd+rKifc3yWwyuPivKPU9Z686G8TGkeQkg7HMBf85IAzaF 8HC/K8BTPD4ibqyHEyPz3CgWW3axS5l4mOU1rVi0pcq0OOiSzKdrK/0y7RXnIowL2sAKSD WTeOcxGUzYFwcRMLoUPn46+MAhFOQvJ9tuik6eCgvl6MjhBNJCKzhQbRwuEdllbWlEzM3G xvcuecVHBI5SuQccxm6Y/+QaiWShoemMelizXl94cdcCzbflawTRSlv8MJiP1w== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1768835790; a=rsa-sha256; cv=none; b=lvUoNDcpVR/jmSEQ8dZWGT38r61XZgR29Wl6mKKLDSyXBCWOeQxgP6uyv5HEvtojTC9GaH v3HOoaqvLUELf6EsBD7EBq/MqwruGrMvwXb/9TdwzkuLJuoVfAXtefjZ10ZgIXHTLcFpxP 7gMYA0KLjon48mqIXkDqbbBonbC3qiX17oJ3GtF9gUm/UY21aJe5xrkhVTuSduyeqaCP1P NXFdXjPH0Oth2umJpINGj0PfexEmsWFNY5oBft+34tjtbOZdu6c+D+IbBZP/arjBCYwy3Q Dij9Ofs/m+gQC6pYmohmU4LGMvFgGKYP7oOELW1vwwBkzW3Kc3ukrDf257cOsg== 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 4dvvDt3f0CzBBl; Mon, 19 Jan 2026 15:16:30 +0000 (UTC) (envelope-from markj@freebsd.org) Date: Mon, 19 Jan 2026 10:16:28 -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: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: On Sat, Jan 17, 2026 at 06:19:47PM +0100, Roman Bogorodskiy wrote: > Mark Johnston wrote: > > > On Thu, Jan 15, 2026 at 06:42:10PM +0100, Roman Bogorodskiy wrote: > > > But bhyve does not start: > > > [...] > > > 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? > > Not sure what's the right way to share the device tree, so I used the > command I found on wiki (https://wiki.freebsd.org/FlattenedDeviceTree), > that is: sysctl -b hw.fdt.dtb | dtc -I dtb > > It's lengthy, so I uploaded it here: > > https://people.freebsd.org/~novel/misc/quartz64_devicetree.txt So, from what I can tell, gic_v3_ofw_bus_attach() should be attaching a child vgic device. Are you loading vmm.ko after the kernel has booted? Does anything change if you load it from loader.conf, or compile vmm into the kernel? > And some more details. Until today I was using u-boot, > sysutils/u-boot-quartz64-a specifically. > > Then I tried using Tianocore EDK2. Apparently, it supports three modes > for devices: > > - ACPI > - ACPI + devicetree > - Devicetree > > The devicetree mode behaves the same way as u-boot, i.e. the vgic fails > to attach. > > In the ACPI (and ACPI + devicetree) mode I can actually start a bhyve > VM. > > However, in this mode Ethernet interface is not detected. > > Earlier it was available as: > > eqos0: mem 0xfe010000-0xfe01ffff irq 28,29 on ofwbus0 > > and now it's completely missing, though I can see it in the device tree. > Does it get confused by ACPI presence? I think the eqos driver has no acpi bus support.