From nobody Mon Jan 19 18:03:15 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 4dvyxZ2bkZz6P8M3 for ; Mon, 19 Jan 2026 18:03:30 +0000 (UTC) (envelope-from bogorodskiy@gmail.com) Received: from mail-ed1-x534.google.com (mail-ed1-x534.google.com [IPv6:2a00:1450:4864:20::534]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4dvyxZ01qQz3PKc for ; Mon, 19 Jan 2026 18:03:30 +0000 (UTC) (envelope-from bogorodskiy@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ed1-x534.google.com with SMTP id 4fb4d7f45d1cf-64b9dfc146fso8135666a12.0 for ; Mon, 19 Jan 2026 10:03:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1768845804; x=1769450604; darn=freebsd.org; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:sender:from:to:cc:subject:date:message-id :reply-to; bh=JakZmmETIrgxv8j6i6vDbYG4HohY4U7mEdAZCKEvqpE=; b=ZxGpuxtMgoNNNgzdnimlTVjuxvmG7At6YPCs+8o8P6lUcJSTrXjV7qkWeqYSpZYxYS e2wVypnq6Ma7vBl+iEI+bV1Zur0MdH02jbHVyjPt71jnwLchsiqFNSwMJ+YNAn06xClQ lf0ISGvw5wyI+YzsJbSKGjCN2dkPic9Qzot1jZoR8ZDys1XDhadx1BOtwclb6HtosW2S xEb/1TI9lgv3KqpWrN30z2mK94J9U+sMUlL96y4tnNl2yqQGGFUAAL9MVhtita/gUdWU 6mKsQq4oWVev3xlYwVjWOx0RQScJNTduF0bqBdVB3zFZytZ7VOz1+ZP15u2an2AC8knc pmWQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1768845804; x=1769450604; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:sender:x-gm-gg:x-gm-message-state:from:to :cc:subject:date:message-id:reply-to; bh=JakZmmETIrgxv8j6i6vDbYG4HohY4U7mEdAZCKEvqpE=; b=uiLZIPrZ291e2Gq08Ssj8FssCW9E5ibXKJZyFH0O53Blhw3VE9qGxBt0lwLPMSgNKl sksrTE0ft2Hq88+ONHk24KJOvKobwjqyObJG+P2AHKbWlNNo6cXn/SD2yRLprSHUU7VQ WuxJVEcfZmoutD6l1XM6VRYu1VvYv2OcT9nX/ouoHFVg3kTUwFWGm1Y8aNfMUyejU1ab PNksbgebVYHsxm+PhJj8EyoYPLLWrvRr6TbPQx+O1AhKgJJQ7Z5IBRhyC7ktt+PeRsUL D7lJO4HGRw3D0Eket74drVxzuXFhSP/bAVhlod/6U3Rt6htrEyg+/KYcSPosopuS8cv/ qEig== X-Forwarded-Encrypted: i=1; AJvYcCW2nyYfIocrpJvkgo+PaasbRx65DSoAnOJQwKE1HGwmgH1HejV3eD2ULQVF4N1/+Aoc8U6Rk6IONigIsg==@freebsd.org X-Gm-Message-State: AOJu0Yw8TK0nuOlcurlvVsshPjn44svi4Vp/yFOhi0YJmCDoZVQuZSfY xHbwirUY5xPHCRvGgiG/gvcsssy3O6i6Qae0ZlOcWzxxpemYxwrn2gwTJuIUd87f X-Gm-Gg: AZuq6aJKE78KH+18fLH6375CabstKA+0j9/hVnMqOGLdkcatsSEiWjzc5lqNXjnCDIH 40rcQRG7wI30C422D4kAZqt2J1y1b5QphpEixcif3l/uC0KqoIFeMTCYsDfRDNAgXB1xrZNfwTN DPCjbXxSmOuZpabXiaFnJZIeRe2rKhU3nlRms8FxaDb+4BPiLSt17OFCy+UiXKJWyc1cbL4t4EW cvKqV+PYDnbzmNBV2HPlM1uKUleYU+8EJZt+ov6vudbbGL7urtxv08ldan/JbOmTjtPxCAiH9oa HoX2hWPfB2WAaDgxXMdEMwh2Aa9yAMhDgnAVHD1IDX15MJgKe/h9DDExttiEEvah5trYWLmjgLk IS/lRsbFmJXIy2W7bq+WAY3tvnmiCwY/ShsSAg4LtwG9UhYF3+MKFhgcX6JIbhWfApdMtjnfy6m laKVu13E1Wk1m6i3NnCwf8RJEZ9uvK/u6ryT4d5V6mMEUpp8+L5QJadrhVVwvjRgXdLK+MFSpdF iPr/g== X-Received: by 2002:a05:6402:13c8:b0:64d:a80b:3268 with SMTP id 4fb4d7f45d1cf-65452fd412dmr10772158a12.10.1768845803307; Mon, 19 Jan 2026 10:03:23 -0800 (PST) Received: from tulp (2001-1c02-1a15-3000-c218-03ff-feb5-6cc4.cable.dynamic.v6.ziggo.nl. [2001:1c02:1a15:3000:c218:3ff:feb5:6cc4]) by smtp.gmail.com with ESMTPSA id 4fb4d7f45d1cf-657e61901e9sm2503733a12.4.2026.01.19.10.03.21 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 19 Jan 2026 10:03:21 -0800 (PST) Date: Mon, 19 Jan 2026 19:03:15 +0100 From: Roman Bogorodskiy To: Mark Johnston 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: X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Rspamd-Queue-Id: 4dvyxZ01qQz3PKc Mark Johnston wrote: > 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? I was loading vmm.ko manually, i.e. by running `kldload vmm`. Nothing changes when I load it via vmm_load="YES" in /boot/loader.conf: vmm: No vgic found module_register_init: MOD_LOAD (vmm, 0xffff0000014391f0, 0) error 19 I'll test adding that to the kernel once I have an established procedure of building a kernel for this board. > > 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. Interestingly, the eqos driver has stopped working completely, even in the devicetree mode, even with vmm_load commented out in /boot/loader.conf. eqos0: mem 0xfe010000-0xfe01ffff irq 27,28 on ofwbus0 eqos0: reset timeout! device_attach: eqos0 attach returned 60 Not sure if it's directly related to the vmm issue though.