public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Ryan Harper <ryanh@us.ibm.com>
To: Avi Kivity <avi@qumranet.com>
Cc: kvm-devel@lists.sourceforge.net, Ryan Harper <ryanh@us.ibm.com>,
	jieryn@gmail.com
Subject: Re: KVM not reporting dmidecode
Date: Thu, 14 Feb 2008 08:02:24 -0600	[thread overview]
Message-ID: <20080214140224.GG6995@us.ibm.com> (raw)
In-Reply-To: <47B40F6F.50501@qumranet.com>

* Avi Kivity <avi@qumranet.com> [2008-02-14 04:28]:
> Ryan Harper wrote:
> >I posted[1] a dmi patches a bit ago on qemu-devel for this.  There was a
> >better solution that involved fixing up the BIOS bits (bochs and qemu).
> >That patch is available as well on qemu-devel.  I've not see any
> >indication of when either bochs or qemu will pick up the DMI changes.
> >
> >  
> 
> I guess I'll have to pick it up.  But I prefer the BIOS version.  Can 
> you repost it?

I prefer the BIOS method as well.  If we pick up anything before QEMU
does, we should pull in that one.  It looks like it was committed[1] to
BOCH cvs on Jan 21st.  I'll pull the BIOS and test that it works with
QEMU cvs/KVM and see if we can get QEMU to pull in a new BIOS build and
the QEMU changes to support DMI.

1.  http://bochs.cvs.sourceforge.net/bochs/bochs/bios/rombios32.c?revision=1.20&view=markup

-- 
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
(512) 838-9253   T/L: 678-9253
ryanh@us.ibm.com

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

  parent reply	other threads:[~2008-02-14 14:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-13 18:13 KVM not reporting dmidecode jieryn
2008-02-13 18:52 ` Ryan Harper
2008-02-14  9:52   ` Avi Kivity
2008-02-14  9:59     ` Alexander Graf
2008-02-14 10:08       ` Avi Kivity
2008-02-14 10:12         ` Alexander Graf
2008-02-14 10:16           ` Avi Kivity
2008-02-14 12:59             ` jieryn
2008-02-14 14:02     ` Ryan Harper [this message]
2008-02-14 16:35       ` Ryan Harper

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=20080214140224.GG6995@us.ibm.com \
    --to=ryanh@us.ibm.com \
    --cc=avi@qumranet.com \
    --cc=jieryn@gmail.com \
    --cc=kvm-devel@lists.sourceforge.net \
    /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