Date: Fri, 19 Mar 2021 13:00:59 -0700 From: David Christensen <dpchrist@holgerdanske.com> To: freebsd-questions@freebsd.org Subject: Re: OS to replace FreeBSD Message-ID: <76c40e90-cf10-fe69-d60a-89428c4be5e8@holgerdanske.com> In-Reply-To: <20210319140448.00007521@seibercom.net> References: <20210319101040.00005c35@seibercom.net> <CA%2BD9QhsjLtVui6exPDyG2CO5H8X-=YckFjCehHusG7eH_kk2sg@mail.gmail.com> <6054BE1B.50706@gmail.com> <20210319130249.000042a1@seibercom.net> <5a8cf0be-646a-a433-2428-9700a47c1bf0@att.net> <20210319140448.00007521@seibercom.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 3/19/21 11:04 AM, Jerry wrote: > I had considered using a different flavor of BSD. I still might. > However, I also happen to have a spare HD that I could plug into the > system, install Windows 10 Pro and Hyper V and then see if FreeBSD 12.x > or newer works correctly. That would only take a short amount of time. > I just need to do it at night so I can take the system offline. > > It probably won't work, but if FreeBSD is isolated from the hardware, > it might be all that is needed in the short run. FreeBSD on Hyper V on Windows 10 should work: https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/supported-freebsd-virtual-machines-on-hyper-v If not, alternatives include VirtualBox, VMware, and Qemu. David
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?76c40e90-cf10-fe69-d60a-89428c4be5e8>