Date: Tue, 2 Apr 2019 10:56:13 -0400 From: Nick Wolff <darkfiberiru@gmail.com> To: Victor Sudakov <vas@mpeks.tomsk.su> Cc: freebsd-virtualization@freebsd.org Subject: Re: Windows 2019 server Message-ID: <CACxAneBRy4=5mSz=9eAqs53wSG9=fv41f_UUVYpSDFb_rkCB-A@mail.gmail.com> In-Reply-To: <20190303032918.GA60561@admin.sibptus.ru> References: <20190216123859.GA24315@doctor.nl2k.ab.ca> <40ddfdd6-a1c4-ac00-f088-2880a7d372ce@smeets.xyz> <20190302094829.GA48523@admin.sibptus.ru> <CACLnyCL5V5j3ykq=VZdwfM8LsKOCfw7rQZH1UnbERq4NTwVGTA@mail.gmail.com> <20190303032918.GA60561@admin.sibptus.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
There is paravirtulized support in FreeBSD 11.2 and 12 but you need to sideload the virtio drivers into windows. Sadly microsoft doesn't ship with them even with how "cloud" focused they are. Ahci-hd will allow you to get around this. I know we had some restrictions in the past on needing specific virt-io drivers for windows I'm not sure if that is fixed now. I think nvme paravirtual might also just work with windows but haven't confirmed that lately. On Sun, Mar 3, 2019 at 8:19 AM Victor Sudakov <vas@mpeks.tomsk.su> wrote: > Jason Tubnor wrote: > > > > > Which kind of storage did you present to the Windows 2019 guest, > > > paravirtualized or ahcd-hd ? > > > > ahci-hd is what you want with bhyve and uefi > > Still no paravirtualized disks support for Windows guests, even in > FreeBSD 12? How sad. > > -- > Victor Sudakov, VAS4-RIPE, VAS47-RIPN > 2:5005/49@fidonet http://vas.tomsk.ru/ >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CACxAneBRy4=5mSz=9eAqs53wSG9=fv41f_UUVYpSDFb_rkCB-A>