From nobody Tue Dec 16 16:44:18 2025 X-Original-To: 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 4dW2p50VbPz6LHrx; Tue, 16 Dec 2025 16:44:29 +0000 (UTC) (envelope-from contact@evilham.com) Received: from yggdrasil.evilham.com (yggdrasil.evilham.com [46.19.33.155]) (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 4dW2p401t7z3Mqp; Tue, 16 Dec 2025 16:44:27 +0000 (UTC) (envelope-from contact@evilham.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=evilham.com header.s=mail header.b=EoP+946h; dmarc=pass (policy=quarantine) header.from=evilham.com; spf=pass (mx1.freebsd.org: domain of contact@evilham.com designates 46.19.33.155 as permitted sender) smtp.mailfrom=contact@evilham.com From: Evilham DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=evilham.com; s=mail; t=1765903460; bh=fDshVLIz3UZScYh+07N/bW2RvaRHtNvz3CdDFojhDf0=; h=From:To:Cc:Subject:References:In-reply-to:Date; b=EoP+946h6oAa4fqlqVvuAQDUyMU5lTUaq7fQ+bjtsFbL4txtnJQuZI5Z/DJ0h1wxB 3Zu21JVsPzVrbWRwwvdesZJzwFzSPLXaON0BQqfz1+x67NZgsy1uF4xxKDBiCKNc3h DzcMgBB/NQasUz5/Yir23VtK9z9AbULdOAy5ncO4= To: Robert Ricci Cc: freebsd-virtualization@freebsd.org, virtualization@freebsd.org Subject: Re: Possible vmm/bhyve regression on FreeBSD 15 References: In-reply-to: Date: Tue, 16 Dec 2025 17:44:18 +0100 Message-ID: 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; format=flowed X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.90 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.995]; DMARC_POLICY_ALLOW(-0.50)[evilham.com,quarantine]; R_SPF_ALLOW(-0.20)[+mx]; R_DKIM_ALLOW(-0.20)[evilham.com:s=mail]; ONCE_RECEIVED(0.10)[]; MIME_GOOD(-0.10)[text/plain]; MISSING_XM_UA(0.00)[]; MIME_TRACE(0.00)[0:+]; TO_DN_SOME(0.00)[]; FROM_HAS_DN(0.00)[]; ASN(0.00)[asn:196752, ipnet:46.19.32.0/21, country:NL]; ARC_NA(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; MID_RHS_MATCH_FROMTLD(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-virtualization@freebsd.org,virtualization@freebsd.org]; RCVD_COUNT_ZERO(0.00)[0]; DKIM_TRACE(0.00)[evilham.com:+] X-Rspamd-Queue-Id: 4dW2p401t7z3Mqp Hey, On dg., des. 14 2025, Robert Ricci wrote: > I've run into what appears to be a regression in vmm/bhyve in > FreeBSD 15, and could use some help tracking it down. > > I upgraded my AMD Zen 4 machine (via source) from stable/14 > (sometime post-14.3) to stable/15 (currently running -stable > from today). I had some VMs (Linux guests of various flavors) > that were running fine before the update. After the update, they > won't start. > > The behavior is: the bootloader seems to work fine (eg. I can > run grub-bhyve, it runs to completion and exits). However once I > start bhyve itself, it just burns up a CPU (note: just one, no > matter how many vCPUs) - I get nothing on serial console, > nothing on the fbuf if I enable it. I think I'm seeing this as well, did you manage to solve it? For me it doesn't matter whether I use uefi or grub bootlaoders. Here is my (suboptimal) temporary workaround: - start a tmux - run vm start -f VM-name on each tmux tab (somehow this works) I also tried with vm-bhyve-devel-1.7.0_1 and have the same symptoms you mentioned. Cheers, -- Evilham