From owner-freebsd-hackers@freebsd.org  Wed Dec 27 17:37:27 2017
Return-Path: <owner-freebsd-hackers@freebsd.org>
Delivered-To: freebsd-hackers@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 EB8A4EA3310;
 Wed, 27 Dec 2017 17:37:27 +0000 (UTC)
 (envelope-from rebecca@bluestop.org)
Received: from muon.bluestop.org (muon.bluestop.org
 [IPv6:2605:7700:0:8:1:0:4a32:3323])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id CB97C6E843;
 Wed, 27 Dec 2017 17:37:27 +0000 (UTC)
 (envelope-from rebecca@bluestop.org)
Received: from muon.bluestop.org (localhost [127.0.0.1])
 by muon.bluestop.org (Postfix) with ESMTP id AE2BC7301;
 Wed, 27 Dec 2017 17:37:19 +0000 (UTC)
Received: from muon.bluestop.org ([127.0.0.1])
 by muon.bluestop.org (muon.bluestop.org [127.0.0.1]) (amavisd-new, port 10026)
 with ESMTP id d2RdyqRhL7nT; Wed, 27 Dec 2017 17:37:19 +0000 (UTC)
Received: from [10.0.10.140] (gw.bluestop.org [96.73.9.3])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (No client certificate requested)
 by muon.bluestop.org (Postfix) with ESMTPSA;
 Wed, 27 Dec 2017 17:37:18 +0000 (UTC)
Subject: Re: Running dual boot windows inside of bhyve
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>
References: <CAGBxaXnEpywFw_KavqjEpEkHeF+UKztue-3iS_c=74h5VNNqiQ@mail.gmail.com>
 <CAOtMX2icE24+qGoq-yqEAgDgibnb-N+TRTH6Nr-Ee4DNuemzbg@mail.gmail.com>
From: Rebecca Cran <rebecca@bluestop.org>
Message-ID: <7352645c-ecf1-008b-e61a-29b580d1f98c@bluestop.org>
Date: Wed, 27 Dec 2017 10:37:18 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.5.2
MIME-Version: 1.0
In-Reply-To: <CAOtMX2icE24+qGoq-yqEAgDgibnb-N+TRTH6Nr-Ee4DNuemzbg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
 <freebsd-hackers.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-hackers>, 
 <mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers/>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
 <mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Dec 2017 17:37:28 -0000

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