From owner-freebsd-virtualization@freebsd.org Wed Oct 26 13:08:55 2016 Return-Path: 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 C5E85C22DA1 for ; Wed, 26 Oct 2016 13:08:55 +0000 (UTC) (envelope-from randy@terbush.org) Received: from mail-qt0-x233.google.com (mail-qt0-x233.google.com [IPv6:2607:f8b0:400d:c0d::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 88D46A8D for ; Wed, 26 Oct 2016 13:08:55 +0000 (UTC) (envelope-from randy@terbush.org) Received: by mail-qt0-x233.google.com with SMTP id 23so3378905qtp.5 for ; Wed, 26 Oct 2016 06:08:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=terbush.org; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=Fosgx573CknDYttvPvkTwoyYdR1vaOt9FeXdypCby0Y=; b=NdKBRLoUMRr2/TCuW9LUhiyzHLmxreY1QoEKARDweRLq8KYR2gl3JXDpf7Fy/Y9AK4 OqG6EbGqnFiuPIjqA8lIPhYCWFWFsbmAphV9Zw677DBPjL7vdqYt6webVr+YaN5f5YU8 oN9X+Nh7HNWW+JwIQauG1Z0Dv+jS5risVNMuk= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=Fosgx573CknDYttvPvkTwoyYdR1vaOt9FeXdypCby0Y=; b=YxNMVoRdCs3Jw41TXkw9R/pmcdj/EGkVMcQjse3T+ywJIGLGPZ0BO/t+DeH70AgJ/0 tCZ1Hm+0j2mgX7/eiYyQT63rBNwqoVRLbKdnFNL/THlltF+GCpiTalLbf+uJJQ8hOwc0 JGQSS3lx0QYSe91pWzv5F0ubWI03Sed+17kGjjMO8eMoQ3Z4dxKhjCCHLcUTWjvZdBbm m/A3vXjEnDaasnn7g7HN4afT85Vz9T2WGC/qM+cygZQRGwsFC2C25wVfzz0ieAL5Cfnf b2901d71DpxsycJ2PrL36Z+Tsn38aKTjLK19pnDQ9B2WqR82KZMt/3zR9mwV4JXh79KG Ks9g== X-Gm-Message-State: ABUngvdHEjMWr/p531yDyS/sDRhkaXM5c6i87mKMr6NBT7KTYJBtnI+kUK0CQupmnkTm8dLw4Os6200JtAx9XQ== X-Received: by 10.200.50.22 with SMTP id x22mr1448607qta.129.1477487334486; Wed, 26 Oct 2016 06:08:54 -0700 (PDT) MIME-Version: 1.0 Received: by 10.200.51.174 with HTTP; Wed, 26 Oct 2016 06:08:24 -0700 (PDT) In-Reply-To: <4febd210b57742b780eefc0132709be2@SERVER.ad.usd-group.com> References: <212f161a-d2d1-d164-3910-eeb256ae68ec@freebsd.org> <4febd210b57742b780eefc0132709be2@SERVER.ad.usd-group.com> From: Randy Terbush Date: Wed, 26 Oct 2016 07:08:24 -0600 Message-ID: Subject: Re: Installing SQL Server on Windows 2012 bhyve guests To: Matt Churchyard Cc: Peter Grehan , "freebsd-virtualization@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Oct 2016 13:08:55 -0000 Thanks guys, I'll report back once I nail this down. I've tried both 4096 and 512 and cannot seem to get an image to boot past the failed EFI message. Not sure if something has changed lately in stable to create that result, but will investigate and report back. Thanks again for the guidance here. -- Randy On Wed, Oct 26, 2016 at 3:30 AM, Matt Churchyard wrote: > -----Original Message----- > From: owner-freebsd-virtualization@freebsd.org [mailto:owner-freebsd- > virtualization@freebsd.org] On Behalf Of Peter Grehan > Sent: 25 October 2016 19:19 > To: Randy Terbush > Cc: freebsd-virtualization@freebsd.org > Subject: Re: Installing SQL Server on Windows 2012 bhyve guests > > >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=' parameter to the disk configuration e.g. > > > -s 4,ahci-hd,/path/to/disk.img,sectorsize=4096 > > Just to add, if you're using vm-bhyve you should be able to add this with > the diskX_opts template/config option > > disk0_opts="sectorsize=4096" > > I may adjust the sample templates to include a sectorsize option for > Windows guests, although I'm not 100% clear on what exact OS versions or > applications require specific settings. I do know that SQL Server has been > reported to suddenly fall over unless a valid block size is used (although > I believe it did install and run), but again I'm not sure exactly what the > "correct" settings are. > > Also note that you shouldn't need any grub_* template options if you're > using UEFI. Those options only apply to grub-bhyve. > > Matt > > >later, > > >Peter. > >