Date: Sat, 29 Mar 2025 21:12:14 +0000 From: bugzilla-noreply@freebsd.org To: virtualization@FreeBSD.org Subject: [Bug 285681] [Hyper-V] i386 panic during storvsc_xferbuf_prepare() Message-ID: <bug-285681-27103-sGgyeuAwrs@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-285681-27103@https.bugs.freebsd.org/bugzilla/> References: <bug-285681-27103@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=285681 Mark Millard <marklmi26-fbsd@yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |marklmi26-fbsd@yahoo.com --- Comment #9 from Mark Millard <marklmi26-fbsd@yahoo.com> --- (In reply to Mark Johnston from comment #7) I've never been able to get FreeBSD to complete much of the boot sequence under Hyper-V on the Windows DevKit 2023 (aarch64) that has Windows 11 Pro. The console output stops after the masks line of the EFI framebuffer information or somewhat later. The farthest I've seen is Event Timer line from the kernel output. It has stopped between those points otherwise. No failure notices when ti stops: just no more output. It does not get far enough for Hyper-V to be able to do a shutdown. Hyper-V indicates the VM was still not ready, even with a long wait first. arm64 Windows 11 only supports v2 VMs. I converted a downloaded FreeBSD .vhd to .vhdx in Hyper-V to have something official to try. (V2 only supports .vhdx .) (My personal builds have historically behaved similarly to the above.) I've never figured out how to get a serial console and named pipe configuration to work. So I'm dependent on the monitor being operational. Anyway, my retry at this got no farther and I was unable to get anywhere near figuring out how to test. I've no clue how specific the Hyper-V problems may be to the Windows DevKit 2023 type of context. So I'm not sure if anyone else would be able to test. I do not know if any of it is tied to Warner's UEFI console related adjustments that he made. -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-285681-27103-sGgyeuAwrs>