From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adam Majer Subject: Re: Windows XP activation regression in KVM-60 Date: Tue, 26 Feb 2008 11:46:12 -0600 Message-ID: <47C45064.4010808@zombino.com> References: <47C3265C.6040203@zombino.com> <47C3DACB.7070901@quicknet.nl> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: kvm-devel@lists.sourceforge.net Return-path: In-Reply-To: <47C3DACB.7070901@quicknet.nl> 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 Pelle wrote: > 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 -- 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/