From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:39856) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zm8Hj-0004pX-B9 for qemu-devel@nongnu.org; Tue, 13 Oct 2015 18:43:08 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Zm8Hg-0000h3-4k for qemu-devel@nongnu.org; Tue, 13 Oct 2015 18:43:07 -0400 Received: from mx1.redhat.com ([209.132.183.28]:34958) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zm8Hf-0000go-VG for qemu-devel@nongnu.org; Tue, 13 Oct 2015 18:43:04 -0400 Date: Tue, 13 Oct 2015 19:43:00 -0300 From: Eduardo Habkost Message-ID: <20151013224300.GT1260@thinpad.lan.raisama.net> References: <1443389342-2186-1-git-send-email-somlo@cmu.edu> <1443389342-2186-4-git-send-email-somlo@cmu.edu> <20151001090203.6cf5af1a@nial.brq.redhat.com> <560CEE63.9030909@redhat.com> <20151001133350.5b2c65cc@nial.brq.redhat.com> <20151010040016.GA11819@GLSMBP.INI.CMU.EDU> <20151013191003.GQ1260@thinpad.lan.raisama.net> <20151014001736-mutt-send-email-mst@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20151014001736-mutt-send-email-mst@redhat.com> Subject: Re: [Qemu-devel] [PATCH v4 3/5] acpi: pc: add fw_cfg device node to ssdt List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Michael S. Tsirkin" Cc: peter.maydell@linaro.org, drjones@redhat.com, matt.fleming@intel.com, pbonzini@redhat.com, ard.biesheuvel@linaro.org, "Gabriel L. Somlo" , qemu-devel@nongnu.org, leif.lindholm@linaro.org, kevin@koconnor.net, kraxel@redhat.com, zhaoshenglong@huawei.com, Igor Mammedov , markmb@redhat.com, Laszlo Ersek , rth@twiddle.net On Wed, Oct 14, 2015 at 12:18:10AM +0300, Michael S. Tsirkin wrote: > On Tue, Oct 13, 2015 at 04:10:03PM -0300, Eduardo Habkost wrote: > > One of the things that may break if guest-visible bits of the machine > > change is Windows license activation, but the rules Windows use to > > trigger reactivation aren't very clear. > > They are easy to find on the internet. I couldn't find them[1]. If you have a pointer to a clear description of the rules for all Windows versions, I would love to see it. [1] All I have found were things like: "Do I need to activate Windows after making a hardware change? Maybe. [...]" http://windows.microsoft.com/en-us/windows/activating-windows-faq#1TC=windows-7 "Microsoft is characteristically shy about discussing the details of activation. [...]" http://www.zdnet.com/article/microsoft-quietly-rewrites-its-activation-rules-for-windows-10/ "What triggers the need to reactivate Windows? As intended, each hardware component gets a relative weight, and from that WGA determines whether your copy of Windows 7 needs reactivation. The weight and the number of changes is apparently a guarded secret. If you upgrade too much at once, WAT decides that your PC is new, and things can get messy. The actual algorithm that Microsoft uses is not disclosed, [...]" http://searchitchannel.techtarget.com/feature/How-Windows-7-hardware-upgrades-affect-licensing -- Eduardo