From owner-freebsd-virtualization@freebsd.org  Mon Feb 20 05:37:52 2017
Return-Path: <owner-freebsd-virtualization@freebsd.org>
Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1AB5DCE6308
 for <freebsd-virtualization@mailman.ysv.freebsd.org>;
 Mon, 20 Feb 2017 05:37:52 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 0A3307A5
 for <freebsd-virtualization@FreeBSD.org>; Mon, 20 Feb 2017 05:37:52 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v1K5bpbA014556
 for <freebsd-virtualization@FreeBSD.org>; Mon, 20 Feb 2017 05:37:51 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
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
Date: Mon, 20 Feb 2017 05:37:52 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: CURRENT
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: decui@microsoft.com
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-virtualization@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-211746-27103-2TAxq0TwKX@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/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-virtualization@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: "Discussion of various virtualization techniques FreeBSD supports."
 <freebsd-virtualization.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-virtualization>, 
 <mailto:freebsd-virtualization-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-virtualization/>
List-Post: <mailto:freebsd-virtualization@freebsd.org>
List-Help: <mailto:freebsd-virtualization-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization>, 
 <mailto:freebsd-virtualization-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Feb 2017 05:37:52 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211746

--- Comment #19 from Dexuan Cui <decui@microsoft.com> ---
(In reply to Dexuan Cui from comment #18)

It looks this is indeed a complex issue and a lots of work is required to h=
ave
a thorough fix.

For now, I'm planning to make a patch to verify the assumption that the
physical memory in the range
[2MB, 2MB+EFI_STAGING_SIZE) is indeed Conventional Memory that doesn't cont=
ain
firmware/loader data/code:

if 'staging_end' is not in the same Conventional Memory block as 'staging',=
 we
print a warning and decrease 'staging_end' to the end of the memory block.

This won't introduce new issues or risks, but can indeed help in the cases =
like
this bug. :-)

--=20
You are receiving this mail because:
You are the assignee for the bug.=