From: "Sebastian Herbszt" <herbszt@gmx.de>
To: Jes Sorensen <Jes.Sorensen@redhat.com>, seabios@seabios.org
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: [SeaBIOS] SMBIOS strings
Date: Sat, 29 May 2010 14:49:24 +0200 [thread overview]
Message-ID: <FCC8117D223648ADA822F9575D85D1B5@FSCPC> (raw)
In-Reply-To: <4BFFE03F.40606@redhat.com>
Jes Sorensen wrote:
> 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.
Which OSes do care? Windows only?
> 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
You can configure this with CONFIG_APPNAME.
> 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
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?
Sebastian
next prev parent reply other threads:[~2010-05-29 15:42 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 [this message]
2010-05-31 7:33 ` Jes Sorensen
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=FCC8117D223648ADA822F9575D85D1B5@FSCPC \
--to=herbszt@gmx.de \
--cc=Jes.Sorensen@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).