This may be a stretch to report here, but read it as a plea for help as to
how to debug this issue further.

I've followed the info provided here
to create a Windows Server 2012 image that I successfully installed on the
bhyve hypervisor. After getting a working Win2012 image running, applying
updates, etc. I attempted to install SQL Server 2014. In the late stages of
that install, the process attempts to start the SQL server engine and fails.

Here is where the fun begins:

The first installation of WinServer 2012 was run as an unattended install.
I've since tried reinstalling it many times changing to an interactive
install, Windows 2016 install etc. and I find that the installation of SQL
Server 2014 fails every time in the same way.

I've attempted to follow some similar reports on the web for other people
installing on dedicated servers by removing all authorization restrictions,
etc. yet the server still fails to run. Log files generated by SQL Server
leave very little to go on and everything logged seems to point back to the
more common solutions regarding permissions and filesystem access.

I am at a place where I am starting to believe that this is somehow related
to the hypervisor, yet I don't have a lot of evidence to base that on. I'm
hoping that someone here might have some ideas of how to further debug
this. I've read that SQL server has some problem running on some filesystem
types, so not sure if there could be some lower level virtio missing piece
that could be causing the failure.

One other bit of data that I have that may or may not be interesting is the
following output from the file cmd on the disk0.img:

disk0.img: DOS/MBR boot sector MS-MBR Windows 7 english at offset 0x163
"Invalid partition table" at offset 0x17b "Error loading operating system"
at offset 0x19a "Missing operating system"; partition 1 : ID=0xee,
start-CHS (0x0,0,2), end-CHS (0x3ff,255,63), startsector 1, 4294967295

This output has been the same for every Windows guest I have created,
regardless of version.

Any help would be greatly appreciated.
_______________________________________________ mailing list
To unsubscribe, send any mail to 

Reply via email to