Windows XP activation regression in KVM-60
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?
- Adam
-------------------------------------------------------------------------
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/
I THINK this is due to the fact that kvm-60+ uses a realtek nic as default and not the old ne2000.
You could try specifying -nic,model=ne2k_pci
I expected this bug to happen on my virtual windows too but it never happened.
Quoted 20 lines · Adam Majer
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?
- Adam
Quoted 10 lines
-------------------------------------------------------------------------
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/
_______________________________________________
kvm-devel mailing list [email protected]
https://lists.sourceforge.net/lists/listinfo/kvm-devel
-------------------------------------------------------------------------
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/
Quoted 3 lines · Pelle
I THINK this is due to the fact that kvm-60+ uses a realtek nic as default and not the old ne2000.
You could try specifying -nic,model=ne2k_pci
Yes, this is *part* of the solution. A clean install that was activated on some old KVM, had some software installed on more recent one only required the nic to be specified to avoid re-activation.
On a more used image though, it did not help. Reactivation was requested.
Avi Kivity may be right that most of the problem rests with qemu changes...
- Adam
Signature · 10 lines
Mail Etiquette ============== * Quote properly or not at all. Top posters, this applies to you! * When replying to posts on mailing lists, only address the mailing list unless poster explicitly requested you include them in CC ------------------------------------------------------------------------- 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/
Quoted 9 lines · Adam Majer
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.
Quoted 8 lines
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.
Signature · 7 lines
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/