Date: Thu, 22 Sep 2016 15:07:37 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 212721] FreeBSD 11.0-RC3 fails on Hyper-V 2012r2 Message-ID: <bug-212721-27103-XBbDE2XVvM@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-212721-27103@https.bugs.freebsd.org/bugzilla/> References: <bug-212721-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=3D212721 --- Comment #26 from Chris K <stryqx@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 i= nto 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 Logi= cal 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 code= base in FreeBSD 11.0-RC3. --=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-212721-27103-XBbDE2XVvM>