Date: Thu, 09 Mar 2017 09:24:45 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 211746] [Hyper-V] UEFI VM can't boot from the iso installation disk Message-ID: <bug-211746-27103-aIkiRhOEhi@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-211746-27103@https.bugs.freebsd.org/bugzilla/> References: <bug-211746-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=3D211746 --- Comment #28 from Dexuan Cui <decui@microsoft.com> --- (In reply to Dexuan Cui from comment #27) > We can notice there is a 4MB BootServicesCode range at [12MB, 16MB) ... loader.efi just writes into this range by force -- this is unsafe anyway! To fix this correctly & thoroughly, IMO we need a relocatable kernel, but that would require a lot of complicated long term work: https://reviews.freebsd.org/D9686?id=3D25414#inline-56969 For now, I suggest we should only apply the idea "reduce the size of the staging area if necessary" to VM running on Hyper-V, we should restore the old behavior on physical machines since that has been working for people for a long period of time, though it's potentially unsafe. I think in the loader we can use CPUID to tell if we're running on Hyper-V = or not. I'm making a patch for this... --=20 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-211746-27103-aIkiRhOEhi>