Date: Wed, 27 Dec 2017 10:37:18 -0700 From: Rebecca Cran <rebecca@bluestop.org> To: Alan Somers <asomers@freebsd.org>, Aryeh Friedman <aryeh.friedman@gmail.com> Cc: "freebsd-virtualization@freebsd.org" <virtualization@freebsd.org>, FreeBSD Mailing List <freebsd-hackers@freebsd.org>, FreeBSD Mailing List <freebsd-questions@freebsd.org> Subject: Re: Running dual boot windows inside of bhyve Message-ID: <7352645c-ecf1-008b-e61a-29b580d1f98c@bluestop.org> In-Reply-To: <CAOtMX2icE24%2BqGoq-yqEAgDgibnb-N%2BTRTH6Nr-Ee4DNuemzbg@mail.gmail.com> References: <CAGBxaXnEpywFw_KavqjEpEkHeF%2BUKztue-3iS_c=74h5VNNqiQ@mail.gmail.com> <CAOtMX2icE24%2BqGoq-yqEAgDgibnb-N%2BTRTH6Nr-Ee4DNuemzbg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12/27/2017 10:15 AM, Alan Somers wrote: > > I fear that you may be out of luck. Windows deliberately frustrates this > use case by profiling its hardware at installation time and at every boot > thereafter. If the hardware changes too much, then Windows demands a new > license fee. Moving from physical hardware to a VM would probably trip > every one of its alarms. Fortunately modern versions at least allow you to move the installation to a different machine without requiring a reinstall. You might be told you need to relicense it, and it will take some time to reconfigure itself to the new hardware it finds itself running on, but it'll work at least. -- Rebecca
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7352645c-ecf1-008b-e61a-29b580d1f98c>