From owner-freebsd-virtualization@freebsd.org Tue Oct 25 15:21:44 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 B413FC21EDC for ; Tue, 25 Oct 2016 15:21:44 +0000 (UTC) (envelope-from randy@terbush.org) Received: from mail-qt0-x22f.google.com (mail-qt0-x22f.google.com [IPv6:2607:f8b0:400d:c0d::22f]) (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 747151286 for ; Tue, 25 Oct 2016 15:21:44 +0000 (UTC) (envelope-from randy@terbush.org) Received: by mail-qt0-x22f.google.com with SMTP id 12so8442282qtm.3 for ; Tue, 25 Oct 2016 08:21:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=terbush.org; s=google; h=mime-version:from:date:message-id:subject:to; bh=2gbyvtTB68AYgDhYTOGJgDZ4M5Qt3vDHImOpd/2RuHc=; b=T57LW4MA6xlmtQJucF1HSTIOs5GWyI7BaFMxCooAl72zsS7FrMgZN5Akd20GS4La3g UJooHomVkIm+Fo7QXU6Y5hZ9KkJwqHimGhdVNdvTk4uVZ9D/0pM0AJkvZhn/DrJHY/Ks fjWFjYDa6Vyep68YWkhWIefo6pRsex0q+fSBo= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=2gbyvtTB68AYgDhYTOGJgDZ4M5Qt3vDHImOpd/2RuHc=; b=Cw89W82+0z2hh0aV2VqIY+4YTuJZVUlfldl5LrFbx+S9VQ2sRs85rfSOZhQEF/fKxc /RUV/vRdZgfavEJv975/8IZU0NMWDrfHHmAx3+Kz0YFamqllVgBZQbek404jNzr+0eR/ nd+hNi+iwI0lI0ZidoKF4zsrXOGUp2CQXjHeH+Gp3kwcPAtrPMYMSTkH9rxH1kwM5T3s vMKERV0eH4TPyp2gL8UzC9RWN24GKDIjRQlf6k7t4G7o87hJV4vn6v8hEGQN+NRTxsOP 8nuslaJNEBQqlWEOsTgt10SXmRYdv4+woivM9/Pc3OaGaK5/HF5D3b0LW7R4RZLwwvnv vftg== X-Gm-Message-State: ABUngvchSu9Tm8ffnHZD0zO72F2FZO9fYB9+3K2wrFVWJafgh7gVv7SKqtjTyU0fK8y/Fr1vIsQiCohHC/YJAA== X-Received: by 10.200.41.33 with SMTP id y30mr20652730qty.66.1477408903376; Tue, 25 Oct 2016 08:21:43 -0700 (PDT) MIME-Version: 1.0 Received: by 10.200.51.174 with HTTP; Tue, 25 Oct 2016 08:21:12 -0700 (PDT) From: Randy Terbush Date: Tue, 25 Oct 2016 09:21:12 -0600 Message-ID: Subject: Installing SQL Server on Windows 2012 bhyve guests To: 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: Tue, 25 Oct 2016 15:21:44 -0000 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 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. 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 sectors This output has been the same for every Windows guest I have created, regardless of version. Any help would be greatly appreciated. -- Randy