qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-devel] Re: [SeaBIOS] SMBIOS strings


From: Jes Sorensen
Subject: [Qemu-devel] Re: [SeaBIOS] SMBIOS strings
Date: Mon, 31 May 2010 09:33:57 +0200
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100430 Fedora/3.0.4-2.fc12 Lightning/1.0b2pre Thunderbird/3.0.4

On 05/29/10 14:49, Sebastian Herbszt wrote:
> Jes Sorensen wrote:
>> 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.
> 
> Which OSes do care? Windows only?

The problem with this kind of stuff is that we don't know what is
sensitive and what doesn't care. Most of the Open Source OSes should be
fine, but still Windows is a pretty big customer in the virtualization
guest space.

>> 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.
> 
> Is the different ID displayed on the same VM configuration (esp. -cpu
> option) ?
> The value is gained by calling CPUID so it should not be different.
> 
> Which pre-seabios qemu-kvm bios are you comparing to?

Hmmm good point, I'll go back and dig some more on this.

Cheers,
Jes



reply via email to

[Prev in Thread] Current Thread [Next in Thread]