From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=56782 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1OJKbX-0000kd-T1
	for qemu-devel@nongnu.org; Tue, 01 Jun 2010 02:05:37 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69)
	(envelope-from <Jes.Sorensen@redhat.com>) id 1OJKbW-0006w2-Km
	for qemu-devel@nongnu.org; Tue, 01 Jun 2010 02:05:35 -0400
Received: from mx1.redhat.com ([209.132.183.28]:41040)
	by eggs.gnu.org with esmtp (Exim 4.69)
	(envelope-from <Jes.Sorensen@redhat.com>) id 1OJKbW-0006vm-EB
	for qemu-devel@nongnu.org; Tue, 01 Jun 2010 02:05:34 -0400
Message-ID: <4C04A326.3050205@redhat.com>
Date: Tue, 01 Jun 2010 08:05:26 +0200
From: Jes Sorensen <Jes.Sorensen@redhat.com>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] Re: [SeaBIOS] SMBIOS strings
References: <4BFFE03F.40606@redhat.com>
	<20100528154402.GB3604@redhat.com>	<4C0365F8.2070703@redhat.com>
	<20100531075030.GB22291@redhat.com>	<019522D4DB3546ECB35EA6CC5D5FD069@FSCPC>
	<m3wrujz57a.fsf@blackfin.pond.sub.org>
In-Reply-To: <m3wrujz57a.fsf@blackfin.pond.sub.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Markus Armbruster <armbru@redhat.com>
Cc: seabios@seabios.org, QEMU Developers <qemu-devel@nongnu.org>, Gleb Natapov <gleb@redhat.com>, Sebastian Herbszt <herbszt@gmx.de>

On 06/01/10 07:34, Markus Armbruster wrote:
> "Sebastian Herbszt" <herbszt@gmx.de> writes:
> 
>> Gleb Natapov wrote:
>>> I don't care much as long as we will not have "CPU :". It looks like something
>>> that can change after BIOS upgrade, so it is hard to believe Windows
>>> will stop working because of this change.
>>
>> Maybe it could trigger the Windows activation process?
> 
> Isn't that testable?

The problem there is that the number of possible combinations to test is
endless. I think older versions of windows are far more prone to such
problems than newer ones.

Cheers,
Jes