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

--- Comment #26 from Chris K <str...@gmail.com> ---
(In reply to Hongjiang from comment #20)

If I uninstall KB3172614 from both my Hyper-V hosts I'm able to successfully
install and then boot into FreeBSD 11.0-RC3, as well as successfully boot into
the VHDX you supplied.

The Windows 8.1 and Windows Server 2012 R2 update history page
(https://support.microsoft.com/en-au/help/24717/windows-8-1-windows-server-2012-r2-update-history)
calls out the following Hyper-V related change:

* When you try to configure connecting a SCSI storage device to a Windows
Hyper-V Host, the Host will not recognize the SCSI storage device when Logical
Unit (LUN) 0 is not present.

I suspect this change (along with the Hyper-V code changes in FreeBSD since
10.3) is triggering the virtual disk being detached from the bus.

As a reference, FreeBSD 10.3 release installs correctly with or without
KB3172614 installed. So there's definitely a regression in the Hyper-V codebase
in FreeBSD 11.0-RC3.

-- 
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"

Reply via email to