public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@qumranet.com>
To: Adam Majer <adamm@zombino.com>
Cc: kvm-devel@lists.sourceforge.net
Subject: Re: Windows XP activation regression in KVM-60
Date: Tue, 26 Feb 2008 11:38:35 +0200	[thread overview]
Message-ID: <47C3DE1B.30708@qumranet.com> (raw)
In-Reply-To: <47C3265C.6040203@zombino.com>

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/

      parent reply	other threads:[~2008-02-26  9:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-25 20:34 Windows XP activation regression in KVM-60 Adam Majer
2008-02-26  9:24 ` Pelle
2008-02-26 17:46   ` Adam Majer
2008-02-26  9:38 ` Avi Kivity [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=47C3DE1B.30708@qumranet.com \
    --to=avi@qumranet.com \
    --cc=adamm@zombino.com \
    --cc=kvm-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox