Date: Sat, 9 Nov 2024 11:47:42 +0100 From: Robert Clausecker <fuz@fuz.su> To: Mark Millard <marklmi@yahoo.com> Cc: arm@freebsd.org Subject: Re: Does anyone have aarch64 main FreeBSD working under aarch64 WIndows 11 Pro's Hyper-V? Message-ID: <Zy89zvy1VHrBw8jx@fuz.su> In-Reply-To: <335408A8-6D4E-4B0C-AB09-C64FF80CF3D7@yahoo.com> References: <335408A8-6D4E-4B0C-AB09-C64FF80CF3D7.ref@yahoo.com> <335408A8-6D4E-4B0C-AB09-C64FF80CF3D7@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Mark,
I also run a Windows Dev Kit, but natively. Try
hw.pac.enable="0"
in /boot/loader.conf.
Yours,
Robert Clausecker
Am Fri, Nov 08, 2024 at 11:49:21PM -0800 schrieb Mark Millard:
> 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
> 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/aarch64/20241107/FreeBSD-15.0-CURRENT-arm64-aarch64-ufs-20241107-5036d9652a57-273504.vhd.xz
>
> (Listed with "2024-Nov-07 06:22" in the web browser.)
>
> ===
> Mark Millard
> marklmi at yahoo.com
>
>
>
--
() ascii ribbon campaign - for an encoding-agnostic world
/\ - against html email - against proprietary attachments
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Zy89zvy1VHrBw8jx>