https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211746
--- Comment #22 from Dexuan Cui <de...@microsoft.com> --- (In reply to commit-hook from comment #21) Some people reported the fix was breaking their hosts. Chris H is the first person to dump the EFI memory map to me: on the host there is a 1MB LoaderData memory range, which splits the big Conventional Memory range into a small one (15MB) and a big one: the small one is too small to hold the staging area. Marcel did remind me of this: https://reviews.freebsd.org/D9686?id=25414#inline-56907 But unluckily I didn't realize the importance, since I didn't really have access to an EFI-boot physical FreeBSD host and FreeBSD VM running on Hyper-V didn't expose the issue. I'll attach the screen shot of Chris's mem map FYI. And I'm going to make a patch shortly. -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
