Date: Fri, 5 May 2017 10:28:21 -0700 From: Peter Grehan <grehan@freebsd.org> To: Artur Moor <digunit24@gmail.com> Cc: freebsd-virtualization@freebsd.org Subject: Re: Windows Server 2016 as guest on bhyve 4k emulated drive Message-ID: <bffe8df2-0fa2-a0c7-b241-646338037f47@freebsd.org> In-Reply-To: <CAGru6Pv4=wqmhy7=O4KMHTxDUGVFtWwfTo1xmZ9nZcKK9F28dw@mail.gmail.com> References: <CAGru6PuLog3NkC34YhM8UdpA-2iqwt2sp1BXPmbsh1e__kemzA@mail.gmail.com> <49770719-c87f-c673-4f2b-c17674797159@freebsd.org> <CAGru6Pv4=wqmhy7=O4KMHTxDUGVFtWwfTo1xmZ9nZcKK9F28dw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Artur, > I can not explain how Windows comes to 8192 bytes. As explained in Jeremya F's email, that's the zvol default record size. > <https://msdn.microsoft.com/en-us/windows/compatibility/advanced-format-disk-compatibility-update?f=255&MSPPError=-2147217396>; > about 512E drives. According to the article, the 512E drives should not > be used, because this configuration affects both the lifetime and the > performance of the drives. Bhyve presents a virtual drive so this doesn't apply. > (https://msdn.microsoft.com/en-us/windows/compatibility/advanced-format-disk-compatibility-update?f=255&MSPPError=-2147217396) > > For this reason, I started using 4K emulated drive, both logical and > physical (sectorsize=4096/4096), but Windows can not be installed on a > 4K emulated drive. I'd recommend sticking with "sectorsize=512/4096" for now. The 4096/4096 appears to be a bhyve bug that needs to be fixed, especially since the NVMe emulation GSoC project has been approved*, and that mandates 4K block size. later, Peter. * https://summerofcode.withgoogle.com/projects/#5252121027936256
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bffe8df2-0fa2-a0c7-b241-646338037f47>