From: Avi Kivity <avi@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
Alex Williamson <alex.williamson@hp.com>,
kvm <kvm@vger.kernel.org>
Subject: [Qemu-devel] Re: [PATCH 0/2] qemu: SMBIOS passing support
Date: Mon, 30 Mar 2009 17:59:52 +0300 [thread overview]
Message-ID: <49D0DE68.60309@redhat.com> (raw)
In-Reply-To: <20090330143845.GA26602@redhat.com>
Daniel P. Berrange wrote:
> 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.
>
-smbios serial=blah,model=bleach ?
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-03-30 15:00 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
2009-03-30 14:59 ` Avi Kivity [this message]
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=49D0DE68.60309@redhat.com \
--to=avi@redhat.com \
--cc=alex.williamson@hp.com \
--cc=berrange@redhat.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).