From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: Windows XP activation regression in KVM-60 Date: Tue, 26 Feb 2008 11:38:35 +0200 Message-ID: <47C3DE1B.30708@qumranet.com> References: <47C3265C.6040203@zombino.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel@lists.sourceforge.net To: Adam Majer Return-path: In-Reply-To: <47C3265C.6040203@zombino.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces@lists.sourceforge.net Errors-To: kvm-devel-bounces@lists.sourceforge.net List-Id: kvm.vger.kernel.org Adam Majer wrote: > Hi, > > Original bug was submitted at http://bugs.debian.org/467043. The summary > is that installs of Windows XP from pre-kvm-60 (pre-59?), then upgrading > to kvm-60 or 61 causes Windows to trigger activation due to "computer > changed too much". Downgrading to kvm-58 or previous resolves the issue. > > Haven't tested kvm-59 yet. > > The kernel module is not part of the problem. Using kvm-60 kernel > modules with kvm-58 user part works. > > CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 3800+ > > I'm not quite sure what these changes can be, but is it possible revert > any changes that are causing this? > It's mostly due to qemu merges which change how hardware is reported. While it's possible to avoid it, it's best done on qemu itself (not kvm's copy) to avoid divergence of the sources. -- error compiling committee.c: too many arguments to function ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/