Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 25 Oct 2016 11:18:59 -0700
From:      Peter Grehan <grehan@freebsd.org>
To:        Randy Terbush <randy@terbush.org>
Cc:        freebsd-virtualization@freebsd.org
Subject:   Re: Installing SQL Server on Windows 2012 bhyve guests
Message-ID:  <212f161a-d2d1-d164-3910-eeb256ae68ec@freebsd.org>
In-Reply-To: <CALmWkDZvFPgmub5x_rAu_S3Ksf6xxn3pcQM3z22wr%2BbgMEpLQA@mail.gmail.com>
References:  <CALmWkDZvFPgmub5x_rAu_S3Ksf6xxn3pcQM3z22wr%2BbgMEpLQA@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Hi Randy,

> I've followed the info provided here https://wiki.freebsd.org/bhyve/Windows
> 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.

  There have been some reports of this previously. What might be 
happening is that SQL Server has stricter requirements on the underlying 
block size than NTFS itself has.

  Since you are using a file-backed image, the reported block size from 
the emulated storage controller may be 8KB or even higher, depending on 
the underlying filesystem type.

  A suggestion is to force the block size to 4KB (has to be done during 
install as well), and if the problem persists, try 512 bytes. This is 
done by using the 'sectorsize=<bsz>' parameter to the disk configuration 
e.g.

  -s 4,ahci-hd,/path/to/disk.img,sectorsize=4096

later,

Peter.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?212f161a-d2d1-d164-3910-eeb256ae68ec>