From: Avi Kivity <avi@redhat.com>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: kvm <kvm@vger.kernel.org>, Gleb Natapov <gleb@redhat.com>
Subject: Re: KVM: x86: report valid microcode update ID
Date: Sun, 31 Jul 2011 11:53:08 +0300 [thread overview]
Message-ID: <4E3517F4.8070600@redhat.com> (raw)
In-Reply-To: <20110729224421.GA25444@amt.cnet>
On 07/30/2011 01:44 AM, Marcelo Tosatti wrote:
> Windows Server 2008 SP2 checked build with smp> 1 BSOD's during
> boot due to lack of microcode update:
>
> *** Assertion failed: The system BIOS on this machine does not properly
> support the processor. The system BIOS did not load any microcode update.
> A BIOS containing the latest microcode update is needed for system reliability.
> (CurrentUpdateRevision != 0)
> *** Source File: d:\longhorn\base\hals\update\intelupd\update.c, line 440
>
> Report a non-zero microcode update signature to make it happy.
>
Applied, thanks.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2011-07-31 8:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-29 22:44 KVM: x86: report valid microcode update ID Marcelo Tosatti
2011-07-31 8:53 ` Avi Kivity [this message]
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=4E3517F4.8070600@redhat.com \
--to=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
/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