From: "Daniel P. Berrange" <berrange@redhat.com>
To: Alex Williamson <alex.williamson@hp.com>
Cc: qemu-devel <qemu-devel@nongnu.org>, kvm <kvm@vger.kernel.org>
Subject: [Qemu-devel] Re: [PATCH 0/2] qemu: SMBIOS passing support
Date: Mon, 30 Mar 2009 15:38:45 +0100 [thread overview]
Message-ID: <20090330143845.GA26602@redhat.com> (raw)
In-Reply-To: <1238421576.15558.146.camel@lappy>
On Mon, Mar 30, 2009 at 07:59:36AM -0600, Alex Williamson wrote:
>
> Is there any interest in this series? Aside from copying host SMBIOS
> entries, it also seems useful for providing information to the guest
> about their virtual machine pool (perhaps via a type 3 entry), or
> whatever other bits of data someone might find useful (type 11, OEM
> string for instance). Thanks,
>
> Alex
>
> On Mon, 2009-03-23 at 13:05 -0600, Alex Williamson wrote:
> > This series adds a new -smbios option for x86 that allows individual
> > SMBIOS entries to be passed into the guest VM. This follows the same
> > basic path as the support for loading ACPI tables. While SMBIOS is
> > independent of ACPI, I chose to add the smbios_entry_add() function to
> > acpi.c because they're both somewhat PC BIOS related (and ia64 can
> > support SMBIOS and might be able to make use of it there).
> >
> > This feature allows the guest to see certain properties of the host if
> > configured correctly. For instance, the system model and serial number
> > in the type 1 entry. Obviously its only built at boot, so doesn't get
> > updated for migration scenarios. User provided entries will supersede
> > generated entries, so care should be taken when passing entries which
> > describe physical properties, such as memory size and address ranges.
> > Thanks,
I can't help thinking that if we wish to provide metadata to guest OS
like system model, serial number, etc, then we'd be better off using
explicit named flags (or QEMU config file settings once that exists)
-system-serial 2141241521 -system-model "Some Virtual Machine"
and have QEMU generate the neccessary SMBIOS data, or other equivalent
data tables to suit the non-PC based machine types for which SMBIOS
is not relevant.
Regards,
Daniel
--
|: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :|
|: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|
next prev parent reply other threads:[~2009-03-30 14:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-23 19:05 [Qemu-devel] [PATCH 0/2] qemu: SMBIOS passing support Alex Williamson
2009-03-23 19:11 ` [Qemu-devel] [PATCH 1/2] qemu: Allow SMBIOS entries to be loaded and provided to the VM BIOS Alex Williamson
2009-04-06 19:50 ` [Qemu-devel] " Anthony Liguori
2009-04-06 22:34 ` Alex Williamson
2009-04-06 22:42 ` Anthony Liguori
2009-04-07 19:34 ` [Qemu-devel] Re: [kvm] " Alex Williamson
2009-04-07 19:49 ` Anthony Liguori
2009-03-23 19:11 ` [Qemu-devel] [PATCH 2/2] qemu:bios: Read external SMBIOS entries from the VM Alex Williamson
2009-04-06 19:52 ` [Qemu-devel] " Anthony Liguori
2009-03-30 13:59 ` [Qemu-devel] Re: [PATCH 0/2] qemu: SMBIOS passing support Alex Williamson
2009-03-30 14:05 ` Gleb Natapov
2009-03-30 14:38 ` Daniel P. Berrange [this message]
2009-03-30 14:59 ` Avi Kivity
2009-03-30 15:40 ` Alex Williamson
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=20090330143845.GA26602@redhat.com \
--to=berrange@redhat.com \
--cc=alex.williamson@hp.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.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).