From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=51441 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OI1Qd-0002j6-Of for qemu-devel@nongnu.org; Fri, 28 May 2010 11:24:56 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OI1Qc-0003Du-Cy for qemu-devel@nongnu.org; Fri, 28 May 2010 11:24:55 -0400 Received: from mx1.redhat.com ([209.132.183.28]:65368) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OI1Qc-0003DS-6n for qemu-devel@nongnu.org; Fri, 28 May 2010 11:24:54 -0400 Message-ID: <4BFFE03F.40606@redhat.com> Date: Fri, 28 May 2010 17:24:47 +0200 From: Jes Sorensen MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] SMBIOS strings List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: seabios@seabios.org Cc: QEMU Developers Hi, We were looking at the dmidecode output from qemu-kvm pre-seabios and current qemu-kvm and noticed some of the strings have changed. The main problem with this is that certain OSes are quite sensitive to system changes and avoiding to change things unnecessarily would probably be a good thing. I wanted to check with the lists if there are any strong feelings about this, and whether some of these changes were made for specific reasons? For example: Handle 0x0000, DMI type 0, 24 bytes BIOS Information - Vendor: QEMU - Version: QEMU + Vendor: Bochs + Version: Bochs Release Date: 01/01/2007 Address: 0xE8000 Runtime Size: 96 kB and this: Handle 0x0401, DMI type 4, 32 bytes Processor Information - Socket Designation: CPU 1 + Socket Designation: CPU01 Type: Central Processor Family: Other - Manufacturer: QEMU - ID: 63 06 00 00 FD FB 8B 07 + Manufacturer: Bochs + ID: 23 06 00 00 FD FB 8B 07 Version: Not Specified Voltage: Unknown External Clock: Unknown I guess the Socket Designation in particular might have been done for a reason? Otherwise, if there are no objections, I'll look at adding some patches to make it more backwards compatible. Cheers, Jes