https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=285681
--- Comment #12 from Mark Millard <marklmi26-f...@yahoo.com> --- (In reply to Wei Hu from comment #11) What I was trying to boot was from the main [so: 15] 2025-Mar-27 VM image that I downloaded yesterday from: https://download.freebsd.org/ftp/snapshots/VM-IMAGES/15.0-CURRENT/aarch64/Latest/FreeBSD-15.0-CURRENT-arm64-aarch64-zfs.vhd.xz My pictures include showing: main-n276101-fd52a9e11c52 with a 2025-Mar-27 date. So recent, for sure. But the observed behavior is not new in my context. I normally run main, either official builds or a personal variant. If I use an alternate it is normally an officially built stable/* (stable/14 at this point). I converted the .vhd to .vhdx for use with Hyper-V v2. FYI: aarch64 no longer has console=comconcole as a possibility in the loader: just efi and eficom . So instructions on https://wiki.freebsd.org/HyperV about named pipe use for serial console use for v2 are out of date and cannot be followed. There is no 14.0 any more listed in: https://download.freebsd.org/ftp/releases/VM-IMAGES/ There is no 14.0 or 14.1 any more listed in: https://download.freebsd.org/ftp/snapshots/VM-IMAGES/ So I'm guessing you are recommending testing: https://download.freebsd.org/ftp/releases/VM-IMAGES/14.1-RELEASE/aarch64/Latest/FreeBSD-14.1-RELEASE-arm64-aarch64-ufs.vhd.xz that the web page is showing 2024-Jun-04 22:30 in the Date column for. But that is far from being recent. But may be you mean: FreeBSD-14.2-STABLE-arm64-aarch64-ufs.vhd.xz that has the Date column showing: 2025-Mar-27 10:59 that would be recent? Anyway, I'm unclear on just which available VM download you are suggesting that I try just to get to the point of some example operational Hyper-V session. -- You are receiving this mail because: You are the assignee for the bug.
