Date: Fri, 8 Nov 2024 23:49:21 -0800 From: Mark Millard <marklmi@yahoo.com> To: FreeBSD ARM List <freebsd-arm@freebsd.org>, "freebsd-virtualization@freebsd.org" <freebsd-virtualization@FreeBSD.org> Subject: Does anyone have aarch64 main FreeBSD working under aarch64 WIndows 11 Pro's Hyper-V? Message-ID: <335408A8-6D4E-4B0C-AB09-C64FF80CF3D7@yahoo.com> References: <335408A8-6D4E-4B0C-AB09-C64FF80CF3D7.ref@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
The specific Win11 Pro context that I have access to involves a Windows Dev Kit 2023. The Hyper-V boot output stops at the end of (no serial port to capture, so not literal text): EFI framebuffer information: addr, size 0xe0000000, 0x800000=20 dimensions 1024 x 768 stride 1024 masks 0x00ff0000, 0x0000ff00, 0x000000ff, 0xff000000 Trying boot loader selections for Video vs. Serial vs. both made no visible difference. Hyper-V indicates 12% usage. (8 cores so this likely is how 1 core being busy would display.) One form of experiment was via a download and expansion of: = http://ftp3.freebsd.org/pub/FreeBSD/snapshots/VM-IMAGES/15.0-CURRENT/aarch= 64/20241107/FreeBSD-15.0-CURRENT-arm64-aarch64-ufs-20241107-5036d9652a57-2= 73504.vhd.xz (Listed with "2024-Nov-07 06:22" in the web browser.) =3D=3D=3D Mark Millard marklmi at yahoo.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?335408A8-6D4E-4B0C-AB09-C64FF80CF3D7>