All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@qumranet.com>
To: Alexander Graf <alex@csgraf.de>
Cc: kvm-devel@lists.sourceforge.net, jieryn@gmail.com
Subject: Re: KVM not reporting dmidecode
Date: Thu, 14 Feb 2008 12:08:24 +0200	[thread overview]
Message-ID: <47B41318.4030006@qumranet.com> (raw)
In-Reply-To: <D2696028-3514-4E6B-8294-BD0EC188BACE@csgraf.de>

Alexander Graf wrote:
>
> I would really love to see this as well. Mac OS X is rather picky on 
> the DMI tables, so I'm pretty sure I'll be able to find some bugs in 
> the implementation when it's posted.
>
> I also have several bios changes to include support for newer 
> hardware, which was required to get Mac OS X working. Qemu follows the 
> policy of having these patches sent to bochs, where they are probably 
> going to be lying around for the next decade or so. Is there a chance 
> to get the changes into the KVM bochs-bios branch?
>

Yes.  Though I imagine you'll need changes to qemu as well, which I'm 
less thrilled to diverge from.  We'll work something out.

-- 
Any sufficiently difficult bug is indistinguishable from a feature.


-------------------------------------------------------------------------
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/

  reply	other threads:[~2008-02-14 10:08 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 [this message]
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
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=47B41318.4030006@qumranet.com \
    --to=avi@qumranet.com \
    --cc=alex@csgraf.de \
    --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 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.