From: Ryan Harper <ryanh@us.ibm.com>
To: jieryn@gmail.com
Cc: kvm-devel@lists.sourceforge.net
Subject: Re: KVM not reporting dmidecode
Date: Wed, 13 Feb 2008 12:52:01 -0600 [thread overview]
Message-ID: <20080213185201.GF6995@us.ibm.com> (raw)
In-Reply-To: <eab08af20802131013x2279bbe3ia2492ffb8cc76ff9@mail.gmail.com>
* jieryn@gmail.com <jieryn@gmail.com> [2008-02-13 12:18]:
> Greetings,
>
> I'm using vanilla sources 2.6.24.2 and KVM-60. I'm trying to install a
> corporate rollout WinXP image which utilizes WinPE in an attempt to be
> clever. Unfortunately, this seems to fail because dmidecode and vpddecode
> produce no usable results. Is there any chance that kvm/qemu will see
> support for this?? I'm getting fairly desperate.
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.
Until then you'll have to patch it in yourself. This is the latest
revision AFAIK:
http://marc.info/?l=qemu-devel&m=120083547021821&w=2
1. http://marc.info/?l=qemu-devel&m=119740418021275&w=2
--
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/
next prev parent reply other threads:[~2008-02-13 18:52 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 [this message]
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
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=20080213185201.GF6995@us.ibm.com \
--to=ryanh@us.ibm.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