From owner-freebsd-virtualization@freebsd.org  Tue May  2 14:06:29 2017
Return-Path: <owner-freebsd-virtualization@freebsd.org>
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 E2EE6D5ADAF
 for <freebsd-virtualization@mailman.ysv.freebsd.org>;
 Tue,  2 May 2017 14:06:29 +0000 (UTC)
 (envelope-from digunit24@gmail.com)
Received: from mail-qk0-x22f.google.com (mail-qk0-x22f.google.com
 [IPv6:2607:f8b0:400d:c09::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 A114B996
 for <freebsd-virtualization@freebsd.org>; Tue,  2 May 2017 14:06:29 +0000 (UTC)
 (envelope-from digunit24@gmail.com)
Received: by mail-qk0-x22f.google.com with SMTP id u75so117412971qka.3
 for <freebsd-virtualization@freebsd.org>; Tue, 02 May 2017 07:06:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
 h=mime-version:from:date:message-id:subject:to;
 bh=vblq1axSHTwEojO9/Zn4JDFutum08RdYuLrh43z3Rhg=;
 b=itNda7xIVPqoGXFmLLRCgbUwCzK+EGzvPK+GCGxPRMAZyhlQ1YnXHvDqhgXBVRK9A1
 tx7SwH27DaTTV5Kno7R2WrUH5r5E9H3CoJ060oJ40byETwarnhw6F6aV1LMXtdnWiZOj
 RqZjcbyLxAkqXL+4QnSxqFVIaP6pOEJ/xxow57XwMpw0bfLNQJlIhZ0fYC/gCHZAWGYr
 5zoauhiUERdRUdFdf5zvTGVINnehoiacniiCiqsK41E7kYXMGAipnSgwWQVJuljcytlG
 9Y5kZSIdpPqHwljrzjtzyZb2uN3eIfKjT0i779NolqjCflhk/95XvzY2rW3fuPFH5Fl8
 DBgQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20161025;
 h=x-gm-message-state:mime-version:from:date:message-id:subject:to;
 bh=vblq1axSHTwEojO9/Zn4JDFutum08RdYuLrh43z3Rhg=;
 b=AfnTWV30BEkkUaEb7WXnfyaXZ/RUxDZlo6G1lKikdnXDOJ5OF34ySmoa3Lkga1VDBf
 AqXomji/y1FpxnAx4QYeOhmyJJpmZe0JtVB+uTZ5UFXQ1BZACSYBQ9r5UfPoDzQPgGBL
 l8e6t/2cVFsc4/2hrnMIsuuG5jhTOAZAk0XVo50OBUkDX+IhblxaLjx0QQAL7uS7ONZi
 iZHVOX9Tg/abVYO0o3BYiMk5eJODgWHOFVPLWybJxujo5V5zfunRkLtybFgtUSdGRSpD
 /hHbnLGGmWMlwgnXycEad2PvxoAKddyX6zfNmjQCyErmAm/2iEsZ28flbB0+UQ0bSs0k
 U/2A==
X-Gm-Message-State: AN3rC/4niJWHOA1A6NmlqwEBGH94tcI3Ni95mP0IEAppcxabWhQUTQEO
 uf2Q6h7aLOLSHFQsrZTdCAvJ79aJ2caj
X-Received: by 10.55.180.197 with SMTP id d188mr28319943qkf.70.1493733988585; 
 Tue, 02 May 2017 07:06:28 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.12.176.50 with HTTP; Tue, 2 May 2017 07:06:28 -0700 (PDT)
From: Artur Moor <digunit24@gmail.com>
Date: Tue, 2 May 2017 16:06:28 +0200
Message-ID: <CAGru6PuLog3NkC34YhM8UdpA-2iqwt2sp1BXPmbsh1e__kemzA@mail.gmail.com>
Subject: Windows Server 2016 as guest on bhyve 4k emulated drive
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."
 <freebsd-virtualization.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-virtualization>, 
 <mailto:freebsd-virtualization-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-virtualization/>
List-Post: <mailto:freebsd-virtualization@freebsd.org>
List-Help: <mailto:freebsd-virtualization-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization>, 
 <mailto:freebsd-virtualization-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 02 May 2017 14:06:30 -0000

Hello,

if the option 'sectorsize=4096/4096' for the emulated drive specified, the
installation process of "Windows Server 2016" completes the first stage
('Copying Windows files', 'Getting files ready for installation',
'Installing features' etc.) and fails after rebooting to the second stage.

The second stage ends with the following message:
Boot Failed. Windows Boot Manager
Boot Failed. EFI DVD/CDROM
Boot Failed. EFI DVD/CDROM 1
Boot Failed. EFI Hard Drive

I suppose that Windows Boot Manager has problems when booting the 4k
emulated drive.

Does anyone have any idea what can be the cause of this?

Thanks in advance for any hints!

Artur