All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jes Sorensen <Jes.Sorensen@redhat.com>
To: Sebastian Herbszt <herbszt@gmx.de>
Cc: seabios@seabios.org, QEMU Developers <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: [SeaBIOS] SMBIOS strings
Date: Mon, 31 May 2010 09:33:57 +0200	[thread overview]
Message-ID: <4C036665.3030801@redhat.com> (raw)
In-Reply-To: <FCC8117D223648ADA822F9575D85D1B5@FSCPC>

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	other threads:[~2010-05-31  7:34 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-28 15:24 [Qemu-devel] SMBIOS strings Jes Sorensen
2010-05-28 15:44 ` [Qemu-devel] Re: [SeaBIOS] " Gleb Natapov
2010-05-31  7:32   ` Jes Sorensen
2010-05-31  7:50     ` Gleb Natapov
2010-05-31 20:38       ` Sebastian Herbszt
2010-06-01  5:34         ` Markus Armbruster
2010-06-01  6:05           ` Jes Sorensen
2010-06-01 23:57             ` [SeaBIOS] [Qemu-devel] " Kevin O'Connor
2010-06-01 13:02           ` Olivier Galibert
2010-06-01  5:36         ` [Qemu-devel] Re: [SeaBIOS] " Gleb Natapov
2010-05-29 12:49 ` Sebastian Herbszt
2010-05-31  7:33   ` Jes Sorensen [this message]
2010-05-29 16:15 ` Kevin O'Connor
2010-06-01 20:26 ` Sebastian Herbszt
2010-06-01 23:34   ` Kevin O'Connor
2010-06-02 20:35     ` Sebastian Herbszt
2010-06-02  6:44   ` Jes Sorensen
2010-06-02 21:01     ` Sebastian Herbszt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4C036665.3030801@redhat.com \
    --to=jes.sorensen@redhat.com \
    --cc=herbszt@gmx.de \
    --cc=qemu-devel@nongnu.org \
    --cc=seabios@seabios.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.